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.
Apple Watch Users Report Weather Complication Issues in watchOS 10
- Thread starter MacRumors
- Start date
- Sort by reaction score
These instructions have worked for my friends and I on several different watch models, figured I’d share them here since I don’t see anyone mentioning to do this:
1. On your iPhone, go to Settings > Privacy > Location Services and check that Location Services is enabled. If the setting is already turned on, try turning it off, pausing for a few moments and then re-enabling it.
2. Check that Apple Watch Faces is set to While Using. Try to toggle it to Never and then back again.
3. Make sure that Weather is set to Always. Toggling this setting also may help.
4. Check if the Background App Refresh is on for Weather.
1. On your iPhone, go to Settings > Privacy > Location Services and check that Location Services is enabled. If the setting is already turned on, try turning it off, pausing for a few moments and then re-enabling it.
2. Check that Apple Watch Faces is set to While Using. Try to toggle it to Never and then back again.
3. Make sure that Weather is set to Always. Toggling this setting also may help.
4. Check if the Background App Refresh is on for Weather.
All these voodoo 'fixes' are not fixes, they just kick the complication into updating, they'll stop again after some minutes or hours. Only Apple can properly resolve this, it's a bug.
Mine shows nothing, and thinks I am 1000 miles away when I touch the complication. Location services are on but nothing.
I've had this a few times too on my AW Ultra even though the weather app itself was showing my correct location. I had no idea how it was choosing me to be in Columbia when the weather app correctly says I'm in PA.
Ha I noticed this issue as well but thought it was because I had Weather uninstalled when I first upgraded. I just deleted it and installed it again, and opened it on the phone before the watch.
I notice the watch would work when a location was selected, but would not automatically use your current location. I guess this is one of those voodoo dance bugs because it's working for me now and I didn't try any of the suggested fixes, just uninstalled and reinstalled Weather again.
I notice the watch would work when a location was selected, but would not automatically use your current location. I guess this is one of those voodoo dance bugs because it's working for me now and I didn't try any of the suggested fixes, just uninstalled and reinstalled Weather again.
This is not a new issue. I had it on multiple betas on my W7, and it still remains on my U2. You'd think they would have caught this one by now, weather/complications working is a big one.
agree except they are too focused on being a subscription house. Apple software isn't what it used to be, never will.
I‘ve experienced this off and on for some time. It’s been especially bad the past few days, and I have not updated to watchOS 10.
That might fix some user’s issues, but as someone who has a series 8 and series 4, I made sure all settings were correct months ago and still intermittently experience this problem even though I have held off updating to watchOS 10.
I think the reports associating it to watchOS 10 are because the people most likely to notice and complain about the issue are also the most likely to update. I’m guessing this is caused by a combination of underlying issues involving battery management and syncing the iPhone and the Apple Watch.
The Apple Weather app overall is pretty abysmal. It's gotten better with iOS releases, but it's buggy at best.
As a developer who recently worked on a widget complication for watchOS 10 - I can relate. You have to choose between scheduled interval updates (min 15-20 minutes) or to hope your process gets woken up in the background to do manual updates. Both suck - because often the data only updates every 5-10 minutes, so your 15 minute update could take 30 minutes to reflect actual data, and still be 5 min behind real time.
They need a much more flexible system for widget updates. Honestly, a user permission for "frequent updates" would be great. Widgets that need it can request it, and the others can live in the current system. The entire point of the AW is glanceable information, but if that info is out of date or missing, then what is the point?
They need a much more flexible system for widget updates. Honestly, a user permission for "frequent updates" would be great. Widgets that need it can request it, and the others can live in the current system. The entire point of the AW is glanceable information, but if that info is out of date or missing, then what is the point?
