Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacRumors

macrumors bot
Original poster
Apr 12, 2001
67,488
37,763


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

  1. On your iPhone, open the Settings app, then tap Privacy & Security -> Location Services.
  2. Scroll down and tap Weather.
  3. Under Allow Location Access, tap Never, then tap your original setting.
  4. Check whether the issue is resolved.
If weather data still doesn't load, Apple suggests trying these steps:
  1. On your iPhone, open the Settings app, then tap General -> Transfer or Reset iPhone.
  2. Tap Reset -> Reset Location & Privacy.
  3. If prompted, enter your passcode and reset.
  4. 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.

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
 
Last edited:
  • Like
Reactions: Pinkyyy 💜🍎
My 3yo SE is still not working with weather and 10.0.2 isn't coming up, I'm on 10.0.1 and it says its up-to-date. Also the battery has taken a nose dive since the new OS, and a few times its not waking up with the alarm.
 
POTENTIAL fixes? We don’t really know what’s going on, so throw some 💩at the board and see if it sticks.
Wow, just wow.
It’s possible for the same issue to have multiple possible causes, so the same workaround may not work for all users.

Also, bugs that only occur for a subset of users can be an absolute nightmare to confirm and resolve.

This is nothing more than a visual bug and would have been at the bottom of the dev team’s priorities during beta.
 
None of the above methods worked: Apple Watch 7 (10.0.1 because the 10.0.2 is not available for me yet 🤷🏻‍♂️) and iPhone 15 with latest iOS

Update: it worked for a few minutes and then it went back as before
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.