Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Watchos7 "cannot verify the iOS update because you are not connected to the internet"
- Thread starter Pharsirme
- Start date
- Sort by reaction score
The message says it all. You need an internet connection. Try things that might bring that back.
Turn wifi off, then back on.
Try a different wifi network.
Turn off any VPN software.
Restart your phone.
Restart your router.
Wait a few hours.
Try visiting websites to check for connectivity.
Try other devices on the same network.
Turn wifi off, then back on.
Try a different wifi network.
Turn off any VPN software.
Restart your phone.
Restart your router.
Wait a few hours.
Try visiting websites to check for connectivity.
Try other devices on the same network.
Thanks for the reply.
Tried all that but as soon as the update reaches preparing, the unable to update comes up. Tried it over 10times.
Welcome to the club. Doesn’t appear to be any fix. Some people randomly reported that theirs started working recently but I have spent a couple of hours and still no luck. Tried it from the phone. Tried it from the watch. Tried it from the watch with the phone off. Nothing works.
I Guess we should just leave it for few hours , since all possible solutions failed. Like @chabig said, it’s a glitch from the phone, I just hope it’s not permanent.
If an Apple Store is nearby, they can send it into the repair depot, which will perform the update at no charge. But it does take a few days.
I tried every possible approach, with the exception of erasing my phone, and all attempted updates, over multiple times and different dates, would fail about halfway through the "Preparing" step wtih the resulting dialog, which was patently false. That step only takes place after the payload has been uploaded to the watch. I even unsynced my phone's music library to free up GBs of working space for a little ~100MB update, just to make sure.
And I doubt Apple's verification servers were down for a day, then again a week later at a different time of day, unless their uptime is rotten, in which case it would be quite noticeable.
During those attempts, it also had trouble restoring from backup using the automatic process, but using the manual process with the PIN code did work. The 14/7 duo has its issues.
I tried every possible approach, with the exception of erasing my phone, and all attempted updates, over multiple times and different dates, would fail about halfway through the "Preparing" step wtih the resulting dialog, which was patently false. That step only takes place after the payload has been uploaded to the watch. I even unsynced my phone's music library to free up GBs of working space for a little ~100MB update, just to make sure.
And I doubt Apple's verification servers were down for a day, then again a week later at a different time of day, unless their uptime is rotten, in which case it would be quite noticeable.
During those attempts, it also had trouble restoring from backup using the automatic process, but using the manual process with the PIN code did work. The 14/7 duo has its issues.
Hello thanks for the reply, unlucky for me , Apple store is very far from me , so are saying I won’t be able to use the watch s5 again or it’s just faulty ?
Thank You soo much, I will try that now, I am just setting it up newly, I hope it works.
I tried everything and no success.
did that work for you? I tried that many times before and it didn’t make a difference.
Been battling this for months on my Series 4. Stuck on 7.0. Have tried nearly everything
Like most folks in this thread, I have tried everything: unpairing; rebooting (phone + watch); factory resetting the watch; leaving it on the charger while it downloaded; tried downloading it directly from the watch, etc. and none of it worked. So I decide to chat with Apple last night about the issue, and after being transferred to a supervisor he immediately escalated my issue to engineering. They scheduled a callback for the next day (today) to talk about the problem in detail with an expert. And here is what she told me:
Apple is aware of the problem since Oct 28, but she won't be able to resolve the problem at the moment. I was then told she'll call me back on Thursday after sending in my reports to the engineering team. So, I'm guessing we'll have a new update soon? If not, we should demand a replacement, since it could be hardware related.
Apple is aware of the problem since Oct 28, but she won't be able to resolve the problem at the moment. I was then told she'll call me back on Thursday after sending in my reports to the engineering team. So, I'm guessing we'll have a new update soon? If not, we should demand a replacement, since it could be hardware related.