iPhone XR LTE seen in status bar but no internet!

mujtaba.mir

macrumors 6502a
Original poster
Oct 16, 2014
523
361
Trying to figure out if this is a hardware or software issue. Once every 2-3 days I face this issue where the status bar show full 4 bars of LTE but there is no connectivity. Safari doesn’t load pages, apps don’t work. The only way to fix this quickly is to switch on AirPlane mode and switch it off, and LTE starts working. I am on 12.2 beta 5 (updated from 12.1.4 just now).

A few reddit users have seen the same issue too and airplane toggle seems to be the fix for now. A few users here on macrumors have faced it too and resetting network settings helped them. Also, want to point out that I did a DFU restore last night and faced the issue today again.

I visited the Apple Store today and they gladly will replace the unit but I want to establish whether it is a software issue or hardware issue. My model is A1984 and if I replace the phone here in UAE, I get a unit which doesn’t have Facetime.

If anyone has faced this, please post here and let us know which model, iOS version and also if you are using eSIM or a physical SIM. Thanks.
 

Knowlege Bomb

macrumors 604
Feb 14, 2008
6,582
2,326
Madison, WI
I have a strong feeling this is an A12 issue. I have a XS that I'm in the process of selling because of constant connectivity and freezing/stuttering issues. I've already had it replaced by Apple and don't feel like going through the same song and dance just to get a third one with the same issues.

I found a 128GB jet black iPhone 7 on craigslist and scooped it up. It's been a good experience so far, although battery life leaves a little to be desired. I'll potentially revisit the idea of newer hardware this fall but IMO 2018 hardware is a bust.
 

NoBoMac

Moderator
Staff member
Jul 1, 2014
2,545
931
I have a strong feeling this is an A12 issue.
If HW, possibly A11 Bionic as well. My 8 will do this occasionally as well, but not at the frequency of OP (maybe once a month, every two months).

Leaning toward SW as did not see these issues until iOS 12.
 

techiegirl

macrumors 65816
Sep 7, 2007
1,154
174
I had this problem today with my XS Max. I Took the SIM card out, put it in another phone and data was fine. I am using dual SIM, so I took the SIM card out of the phone and deleted my physical sim profile. I put the SIM card back and reset the profile back. Everything is working fine now.
 

mujtaba.mir

macrumors 6502a
Original poster
Oct 16, 2014
523
361
I have a strong feeling this is an A12 issue. I have a XS that I'm in the process of selling because of constant connectivity and freezing/stuttering issues. I've already had it replaced by Apple and don't feel like going through the same song and dance just to get a third one with the same issues.

I found a 128GB jet black iPhone 7 on craigslist and scooped it up. It's been a good experience so far, although battery life leaves a little to be desired. I'll potentially revisit the idea of newer hardware this fall but IMO 2018 hardware is a bust.
My XR has been replaced by Apple a few times before as well for multiple reasons, not involving connectivity. Unfortunately I am stuck with one of these now since I need dual sims. I just hope this issue is a software issue. I have removed the eSIM profile and added it back now. I will update if the issue comes back again. 12.2 Beta 5 has been very smooth.
[doublepost=1552374615][/doublepost]
I had this problem today with my XS Max. I Took the SIM card out, put it in another phone and data was fine. I am using dual SIM, so I took the SIM card out of the phone and deleted my physical sim profile. I put the SIM card back and reset the profile back. Everything is working fine now.
I haven't got the opportunity yet to face this issue with the physical card. I am travelling tomorrow onwards so will look out for the issues on the visitor line for data.
 

axantas

macrumors 6502
Jun 29, 2015
308
215
Home
I had this issue a couple of weeks with an iPhone X at a German provider. Switching off LTE and using 3G resolved it.
It turned out to be a provider issue...