Apple Watch Users Report Weather Complication Issues in watchOS 10

[MacRumors]

Some Apple Watch users on watchOS 10 have reported experiencing issues with Weather complications failing to display data on the watch face, despite the Weather app itself presenting no such issues.

Apple Watch users have taken to the MacRumors forums, Apple's Support Community, and other platforms to share their experiences. 9to5Mac has highlighted the problem, and some MacRumors staff have seen its occurrence on their own watches.

Affected complications appear blank where weather data should be showing, and yet tapping the complication reveals the expected information in the Weather app. The issue appears to be happening on various models whether they are on watchOS 10.0 or have been updated to the latest watchOS 10.0.1 update.

Until Apple issues an update to correct the problem, one temporary workaround that users have had the most success with is to open the Watch app on iPhone and toggle the 24-Hour Time switch in the Clock app settings, wait a few seconds, then toggle it back to its original position. The paired Watch should update, and the affected complications should display weather data again (until they don't again – your mileage may vary).

Has your Apple Watch been affected by the Weather complications issue? Let us know in the comments.

Article Link: Apple Watch Users Report Weather Complication Issues in watchOS 10

 

[Matthias46]

The 24 Hour time doesn't fix this thing and also resetting the Location settings...I hope Apple can resolve it quickly!

 

[jMan80]

I am actually experiencing this issue in the weather app itself. I often need to reopen the app to make it load the weather data for the current location (in Germany mostly) since WatchOS 10

 

[LedRush]

The weather complication has never reliably worked for me.

 

[adammusic]

Been posting about this since watch 10 beta launced. Someone on reddit finally found a fix for me.
You have to do this
Settings > display & brightness > always on > complications data > turn all on.


For some reason watch os 10 turn display complications data off for me.

Working normal now.

 

[bengoey49]

I have the same problem on my iWatch 6 in the UK.
Togglingthe 24 hr on and off does not work.
It was ok before updating to the latest IOS

 

[bengoey49]

Been posting about this since watch 10 beta launced. Someone on reddit finally found a fix for me.
You have to do this
Settings > display & brightness > always on > complications data > turn all on.


For some reason watch os 10 turn display complications data off for me.

Working normal now.

Always on is unfortunately on the Pro model only.

 

[Japan Ricardo]

Been posting about this since watch 10 beta launced. Someone on reddit finally found a fix for me.
You have to do this
Settings > display & brightness > always on > complications data > turn all on.


For some reason watch os 10 turn display complications data off for me.

Working normal now.

Yeah, but that reveals data on other complications which you might not want people to see (e.g. calendar).

 

[Japan Ricardo]

Always on is unfortunately on the Pro model only.

There is no Pro model. Do you mean the SE and older models like the Series 4?

 

[contacos]

It doesn’t seem to take your location data. I had to manually select Tel Aviv and then it works

 

[Japan Ricardo]

The workaround described in the article is ridiculous. I found that long-pressing the watch face, changing the complication to a different one, then changing it back to the one you want works.

Crazy that this is happening on a version TEN of software! It's the kind of thing that happened in the early versions.

 

[Apple Knowledge Navigator]

Sounds like a complicated issue.

 

[Japan Ricardo]

I have the same problem on my iWatch 6 in the UK.
Togglingthe 24 hr on and off does not work.
It was ok before updating to the latest IOS

You mean 'Series 6'?

The workaround mentioned in the article - which is ridiculous anyway (see my other post) - won't be available to you.

 

[greg624]

I thought I was crazy

 

[eilavid]

On your iPhone, add any new city to your weather app and then remove it. This will trigger a resync and fix it.

 

[abatabia]

Can vouch for this. In general I actually really dislike watch is 10. Makes the watch, a device I am already quickly tiring of, that much more annoying to use.

 

[coolfactor]

I bet getting this fixed is going to be a complication.

 

[5ammyT]

Yep - also having real trouble with the calendar complication… These issues have been happening ever since the beta versions and unfortunately still not solved.... 😩😩

 

[Japan Ricardo]

Why can't we downgrade Watch OS, like we can with iOS?

 

[coolfactor]

The workaround described in the article is ridiculous. I found that long-pressing the watch face, changing the complication to a different one, then changing it back to the one you want works.

Crazy that this is happening on a version TEN of software! It's the kind of thing that happened in the early versions.

That's what many users don't understand. They think once a feature is working, it will keep working forever. Meanwhile, they want Feature X, Y and Z added.

Software is not that compartmentalized. It's very interwoven. Adding a new feature can break an old feature.

It's amazing how well Apple devices work given how complex they are.

 

[Japan Ricardo]

Yep - also having real trouble with the calendar complication… These issues have been happening ever since the beta versions and unfortunately still not solved.... 😩😩

My calendar complication opened last Tuesday's calendar when I touched it just now.

 

[Japan Ricardo]

That's what many users don't understand. They think once a feature is working, it will keep working forever. Meanwhile, they want Feature X, Y and Z added.

Software is not that compartmentalized. It's very interwoven. Adding a new feature can break an old feature.

It's amazing how well Apple devices work given how complex they are.

Apologies for thinking that a feature will continue to work....

I get where you're coming from as a software writer, but it doesn't inspire much confidence in me as a customer if you think it's amazing that things work because they're complex.

Surely this sort of thing is supposed to be ironed out in the months and months of beta testing, not public releases?

 

[Craiguyver]

Been posting about this since watch 10 beta launced. Someone on reddit finally found a fix for me.
You have to do this
Settings > display & brightness > always on > complications data > turn all on.


For some reason watch os 10 turn display complications data off for me.

Working normal now.

Mine was already set to on. However I toggled off all three settings under "Wrist Down" for "Show Complications Data", "Show Apps", and "Show Notifications". When I toggled them off and then turned them back on, the problem is fixed, at least for the moment. Thanks!

 

[i_bit_the_apple]

That's what many users don't understand. They think once a feature is working, it will keep working forever. Meanwhile, they want Feature X, Y and Z added.

Software is not that compartmentalized. It's very interwoven. Adding a new feature can break an old feature.

It's amazing how well Apple devices work given how complex they are.

That means that their software is bad. If the software is complex it's because you have bad architects, bad team leaders and bad tech leads.

And it's not like this is some hidden feature that no one uses. Surely someone at Apple also uses a watch and noticed the things ain't working.

They should concentrate on being a software house, and not a woke PC nest.

 

[base08]

I have this issue frequently on the Stocks complication...