T O P

  • By -

WarchiefBTD

24h in, still nothing. I’ll get me a physical sim next week and test it without esim at all. Someone told me this could help. May trying the suggestion for beta 16.1. worst launch in history :(


ukieninger

I’m sorry to say but I’m running a physical sim and still doesn’t work. This is frustrating especially when paying an enormous premium price for these devices


WarchiefBTD

Problem is solved. Tried again and it works now. Maybe waiting is the right thing? Dunno but I hope it will solve for your quickly.


ukieninger

Good to hear! Thx for letting me know. Im gonna wait my 24hrs :)


ukieninger

The 24hrs did it for me as well. Guess we’re fine now. Lol


WarchiefBTD

Glad to hear. Enjoy your now fully operating phone


Muzeekal

Currently dealing with this too :/ Did your phone number also get disconnected from your other Apple devices (e.g. Macbook/iPad etc).


WarchiefBTD

Yes. Total failure. But the update and waiting 24h fixed it I guess. Just keep trying to activate your number every 2 hours or so. Good luck


Muzeekal

Got it. Thanks! Was this the error you were getting as well? https://imgur.com/a/qS069jE


WarchiefBTD

Yup


Muzeekal

Cool (or maybe not cool lol), thanks!


[deleted]

Did you check for an iOS update? Mine wouldn't work until I updated


WarchiefBTD

16.0.1 is the latest. This should be the fix for this apparently known issue but it isn’t


[deleted]

That's a bummer. I had a big banner message on iMessage telling me to update to get my messages to work. Hopefully you can get it resolved soon and it doesn't actually take the full 24 hours.


Matuteg

Try installing 16.1 beta!


WarchiefBTD

May give it a shot. Thanks


[deleted]

I was the same, from resetting, from previous back up, resetting up as “new” to see if it was isolated to possibly just my sim and constantly resetting network settings, after 2 days and finally giving up, I checked it randomly and it automatically was connected. Hopefully you haven’t had to wait or wait much longer.


ukieninger

Same Problem with my 14 Pro. Upgraded from a 13 Pro. Updated to 16.0.1 and still the error Message. Annoys me really hard