Not on the watch, but on the phone.
On the phone's Clock location settings, it even cites the watch in the subtext.
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 Suggests Potential Fixes for Weather Complication Bug on Apple Watch
- Thread starter MacRumors
- Start date
- Sort by reaction score
On the phone's Clock location settings, it even cites the watch in the subtext.
Where exactly is this 10.0.2 update? Not seeing it on my Ultra. Tried all the usual things to get it to load. (toggling on/off, beta on/off, etc.)
Nothing, running 10.0.01
Nothing, running 10.0.01
Nope - didn’t work. I also tried turning Location Services off, waiting a minute, and turning it back on. No joy.![]()
Apple on Tuesday offered two potential fixes for the recently reported Apple Watch issue where watch face Weather complications fail to load data.
![weather-complications.jpg]()
Apple Watch owners have been complaining of malfunctioning Weather complications since the launch of watchOS 10, with both the initial launch and watchOS 10.0.1 affected. Those impacted are seeing a blank reading where the weather data should be, but tapping into the Weather app shows the expected information.
In a new support document titled "If the Apple Watch Weather complication isn't working," Apple suggests users affected by the issue try the following:
Reset iPhone Settings
If weather data still doesn't load, Apple suggests trying these steps:
- On your iPhone, open the Settings app, then tap Privacy & Security -> Location Services.
- Scroll down and tap Weather.
- Under Allow Location Access, tap Never, then tap your original setting.
- Check whether the issue is resolved.
Apple on Tuesday also released a new watchOS 10.0.2 update, which was initially thought to resolve the Weather complication issue, but it seems that a number of users did not see any permanent resolution after updating.
- On your iPhone, open the Settings app, then tap General -> Transfer or Reset iPhone.
- Tap Reset -> Reset Location & Privacy.
- If prompted, enter your passcode and reset.
- Check whether the issue is resolved.
Did either of Apple's suggested fixes work for you? Let us know in the comments.
Article Link: Apple Suggests Potential Fixes for Weather Complication Bug on Apple Watch
I just turned location services off and backed out of the screen, waited a minute and then reenabled location services.
Something I noticed, in the watch app on iPhone it has been showing current location for default city, that stayed the same. On the watch in weather settings, it was always checking my first location in weather, there wasn’t an option for current location. After turning location settings off and then back on, current location is now checked and an optiin the weather settings on the watch. Complications are working and will have to see if it sticks.
Not sure if this is the case or not, but I did not have this issue at all through out the beta run, it started after having to restore my watch and phone because I received a replacement 13PM. I wonder if it is only happening to people that have had to restore or setup new on iOS 17 and those that upgrade are not affected.
On the watch app I tried this: Settings > display & brightness > always on > complications data > turn all on (toggled it off and on)
Before 10.0.2 released it worked for a brief moment. After updating, weather complications has been working without complication.
Before 10.0.2 released it worked for a brief moment. After updating, weather complications has been working without complication.
I just wanted to add that my Apple Watch 6 was intermittent when it came to showing the weather. I did option number 2 and things seem to be working compared to option 1. It was weird and not sure if anyone else had this problem, but the weather for my current location was not being shown. Only the two cities that I have saved. Everything seems to be working fine now.
Confirming this suggestion worked for me. Thank you!! =)
(This bug was not present in any of the dev betas I tested over the last few months. I only started experiencing the issue last week.)
It was pretty much around from Beta 1 through RC. It's amazing how much it was reported and they can't get something as simple as showing the outside temperature on the watch face.
UPDATE: Unfortunately I spoke too soon. The Weather complication stopped pulling in data again after raising my arm several times in the past hour and checking it, however, when I tap on the complication now it loads data unlike before when nothing happened. Unfortunately it disappears soon after.
I may erase my watch and see if that fixes it but I'll wait 24 hours before reporting results.
LATEST UPDATE: No need to wait 24 hours. I just erased my watch and if anything the issue is worse now with none of my three weather complications showing data consistently....your move, Apple.
Last edited:
I had thought that it was just me with this issue.
I am using a new Ultra 2, a new iPhone 15 PM and both are on new operating systems. I initially noticed the error on the new Modular Ultra watch face, so i was thinking that it was just me.
It now seems to be loading the weather data from the first fix.
I am using a new Ultra 2, a new iPhone 15 PM and both are on new operating systems. I initially noticed the error on the new Modular Ultra watch face, so i was thinking that it was just me.
It now seems to be loading the weather data from the first fix.
Tried both methods. First worked for about an hour the second didn’t work at all. Hope they issue a fix for this.![]()
Apple on Tuesday offered two potential fixes for the recently reported Apple Watch issue where watch face Weather complications fail to load data.
![weather-complications.jpg]()
Apple Watch owners have been complaining of malfunctioning Weather complications since the launch of watchOS 10, with both the initial launch and watchOS 10.0.1 affected. Those impacted are seeing a blank reading where the weather data should be, but tapping into the Weather app shows the expected information.
In a new support document titled "If the Apple Watch Weather complication isn't working," Apple suggests users affected by the issue try the following:
Reset iPhone Settings
If weather data still doesn't load, Apple suggests trying these steps:
- On your iPhone, open the Settings app, then tap Privacy & Security -> Location Services.
- Scroll down and tap Weather.
- Under Allow Location Access, tap Never, then tap your original setting.
- Check whether the issue is resolved.
Apple on Tuesday also released a new watchOS 10.0.2 update, which was initially thought to resolve the Weather complication issue, but it seems that a number of users did not see any permanent resolution after updating.
- On your iPhone, open the Settings app, then tap General -> Transfer or Reset iPhone.
- Tap Reset -> Reset Location & Privacy.
- If prompted, enter your passcode and reset.
- Check whether the issue is resolved.
Did either of Apple's suggested fixes work for you? Let us know in the comments.
Article Link: Apple Suggests Potential Fixes for Weather Complication Bug on Apple Watch
Reset is not a fix. Apple Watch had weather issues on ios 9 as well. looks like they’ve gone unfixed.
on ios 9, weather app sporadically just resets to the default cities, then just fixes on its own.
this is what i partly mean by beta features: release half baked features, then never fix them.
on ios 9, weather app sporadically just resets to the default cities, then just fixes on its own.
this is what i partly mean by beta features: release half baked features, then never fix them.
Just because it wasn't fixed yet doesn't mean it was ignored. Things that can lead to something taking a 'long' time to fix:
- Problem is non-trivial and might require touching multiple layers/services to fix. This not only takes more time, but introduces more risk to fix, which means more time to do correctly.
- Related to above: problem would require cross-team collaboration to fix. This means the timeline of the fix is subject to the priorities and schedules of all involved teams.
- Inability or inconsistency with problem reproduction. This can
- Effort to payoff ratio. How much work is involved to implement a fix vs how much payoff do you get for doing this fix. This necessarily has to be weighed against other issues that need to be fixed and compared to their effort/payoff ratios. Sometimes, some issues that take longer to even start addressing because there are other issues that are placed ahead of them.
- Related to above: how many people is this actually affecting? Sometimes bugs seem really bad, and there might be a vocal set of people that are impacted ... but the numbers may show that the actual number of people being impacted is small. Even if a bug impacts only one person, it will be fixed, but this is weighed against other issues that may be impacting more people and may take a back seat for some time.
- Team cycles/workload. There are a finite number of people working on these issues, and likely a very large list of things to be working through. Sadly, they can only maintain a certain cadence and that doesn't always allow our own pet peeve to be addressed when we'd like them to be.
I noticed besides the complications not showing data that the cities were not syncing. I added a random city and then removed it and it immediately synced up with my phone and also fixed the complications. This was before the last update and I have since updated and restarted the watch a couple times and not seen the issue again.
Agree
Agree
Do not agree at all. One of the main selling points for an Apple Watch is the immediate view of things using the complications. When one of the complications doesn't work, that should be a somewhat high priority.