Weather app crash with Complications

[Grobaouche]

Hello guys,

I have an Apple Watch Ultra, I have a few weather complications, like temperatures or weather conditions. When I touch either of the weather complications it launch and then crash the weather app, and goes back to the main cadran.

Instead, if I launch the weather app first, go back to the cadran, and then touch one of the weather complications, it works.

Seems to be like that since the 9.1 update, anyone having the same annoyance ?

Thanks guys !

 

[ibookemo]

Good tip. I have the issue too on a regular Apple Watch with the latest OS.

 

[Eriamjh1138@DAN]

Ugh. I just started having this problem on my watch 4 running 9.1.

 

[cwosigns]

I’m hoping it’s server-side. I am having that problem on both my ultra and my series 7.

 

[Eriamjh1138@DAN]

Quitting the app on the phone didn’t fix it. Rebooting didn’t fix it. I’ll try rebooting the phone next (running 16.1). If that doesn’t work, there’s unpairing/re-pairing, then I’m out of ideas.

 

[Otflyer]

Same problem here. Noticed it first time this afternoon. Must be a server glitch.

 

[CheesePuff]

Same problem here. Noticed it first time this afternoon. Must be a server glitch.

Same here, just started happening today (Series 7 on 9.1)

 

[arqtiq]

I noticed, it only happens with the current location. If you set it to any other city, it works fine.

Could it be related to the upcoming switch from daylight savings time to standard time?

 

[Frankfurt]

Same.., just happened today … probably a short term server issue

 

[fdw777]

Started having the Weather crash problem today. Why oh why????

 

[wilberforce]

I opened the Weather app on the watch, changed it from "Viewing Temperature" to "Viewing Precipitation," and it stopped crashing. Maybe coincidence? I changed it back to viewing temperature and it was still OK

 

[cwosigns]

I opened the Weather app on the watch, changed it from "Viewing Temperature" to "Viewing Precipitation," and it stopped crashing. Maybe coincidence? I changed it back to viewing temperature and it was still OK

View attachment 2108779

That only puts the weather app in RAM. If I do that and then force close the weather app and tap on a weather complication, it still crashes.

 

[wilberforce]

That only puts the weather app in RAM. If I do that and then force close the weather app and tap on a weather complication, it still crashes.

OK, so if Weather is in RAM it works fine. Interestingly, if I force close Weather, then tap on a weather complication (whereupon Weather crashes), I can go to the dock where Weather is at the top of the list as the most recent app, tap on it, then it works OK. Something is wrong with the way the complication is invoking the Weather app.

 

[wilberforce]

Look at the temperature for 1 a.m., just before DST change:

 

[Otflyer]

I changed my weather app from current location to my city and the weather complication works.

 

[Frankfurt]

Issue resolved itself for me. Probably server issue.

 

[Asianboy604]

Hello guys,

I have an Apple Watch Ultra, I have a few weather complications, like temperatures or weather conditions. When I touch either of the weather complications it launch and then crash the weather app, and goes back to the main cadran.

Instead, if I launch the weather app first, go back to the cadran, and then touch one of the weather complications, it works.

Seems to be like that since the 9.1 update, anyone having the same annoyance ?

Thanks guys !

Yes started having the same issue today. Apple is looking into fixing it and contacting the developers hoping also the next update might. I thought it was only mine doing that but seems like lots of people are having the same issue with this update and the ultra.

 

[wilberforce]

Issue seems to have resolved itself for me - perhaps because now DST change has passed

 

[cwosigns]

Issue seems to have resolved itself for me - perhaps because now DST change has passed

Same

 

[Otflyer]

Yep! It’s now fixed.

 

[Eriamjh1138@DAN]

That is the weirdest time change error I’ve seen.

I launched it from the main app view and that fixed it, just like OP said. Then the complication worked after that (this was Saturday).