Hello @matty1001 ,

Could you please provide a screenshot of the widget? I tried both formats (12-hour and 24-hour), and both seem to be working correctly on my end.

Also, which iOS version are you using? There might be some issues related to the iOS 27 beta.

Oh, sorry — which widget is affected, and what platform are you using (iOS, Android)?

Hello,

I’m sorry about the confusion and thank you for reporting this.

There are actually two possible reasons for the mismatch:

1. Lock Screen widget vs. Home Screen widget
   This difference can be caused by mixing a Premium and non-Premium instance. Please make sure both widgets are premium instance.
   We’re planning to merge this into a single instance in the future to prevent this kind of inconsistency.

2. Widget vs. App icon differences
   The difference between the Home Screen widget and the app itself is caused by how the weather icon is computed on the frontend. The app and widgets currently use slightly different implementations (for technical reasons).

More specifically:
The Premium 1-hour forecast cannot directly display rain/snow intensity using drop/snow icons in the widget, because the icons would be too small. Instead, precipitation is accumulated into 3-hour segments. An icon is then shown only if the accumulated precipitation exceeds certain thresholds.

The mismatch you’re seeing is most likely related to these thresholds and rounding of accumulated precipitation values.

I will review the current implementation and try to align it more closely with the app’s behavior.

Thanks again for pointing this out.

@Alessandro-Di-Mase I think, 18.7.2 is still RC version of the system and that cause this problem. See https://community.windy.com/topic/42388/updated-ios-now-getting-webgl-errors/7?_=1761906024873

Hello @Nick-3g ,
What do you mean by disappear? There is some black spot, or they are showing some preview data ?
Can you send me a screenshot of that situation?

Hello @SAM-JAGE ,
can you please provide us an screenshot of the widget? And also your coordinates (don't have to be exact one) or city name, I will try to simulate your conditions ( it's often connected with location )

Hello @rschmidt1957,
Could you please let us know which version of the Windy app you are using, as well as the version of your operating system?

Thank you.

Hello @pegasbay,

I’m currently implementing some analytics measurements to identify bottlenecks and improve backend performance. This process will take some time, but I’ll keep you updated.

@Kamil-Burczyk, this issue seems to be related to indexing on iOS. Please try restarting your iPhone, and if that doesn’t help, reinstalling Windy might do the trick. This problem sometimes occurs after a system update when iOS doesn’t properly index widgets.

Please let me know if this helps

Hello,

This issue was most likely caused by a bug in our last version. A fixed version is already available in the App Store—please download it and let me know if it resolves the problem.

Also, you’re absolutely right—changing the units in the settings triggers an event to sync those units with the widgets and refresh them.

Hello @Ortlepp-Enrico,
can you please provide us a screenshot of the widget? What Windy version are you using right now?

Hello,

Good news—Apple has just approved our fixed version with widget improvements! Please download it and let me know if it resolves the issues.

The Radar and Satellite widgets were affected by a backend problem. I’m still investigating exactly what happened, but based on our metrics, everything should be working fine now. That said, I’d greatly appreciate hearing about your experience to confirm.

To prevent this kind of issue in the future, I will be adding more metrics and optimizations to ensure everything runs smoothly.

Hello,

Good news—Apple has just approved our fixed version (44.010338). Please download it when you have a chance and let me know if it resolves the issue.

It should be enough to simply open the app, as the sync process with the widget will begin automatically. After a few seconds, the widgets should start working properly. If you want to be completely sure, you can log out and log back in, but this step shouldn’t be necessary—it’ll just speed things up a bit.

Please let me know if the update helped.

Hello @beast23,

Thank you for letting me know. It’s possible that this issue is related to an internal bug in the latest version. I’ve already submitted a fixed version to Apple for review, and as soon as it’s approved, I’ll release it right away.

I truly hope the next version resolves your problem. I’m really sorry for the inconvenience and appreciate your patience.

Hi,

I wanted to update you on a couple of things. I’ve come across an issue in the app related to its implementation. I take full responsibility for this, and I’m already working on a fix, which will be included in the next update. I’m submitting this version for review today.

As for the radar widget issue, it seems to be related to the backend. Once the problem is addressed, the widgets should start working correctly again.

I truly appreciate your understanding and patience, and I’m very sorry for any trouble this has caused. I’ll keep you informed as we make progress.

Hello @pegasbay ,
thank you for report. I am going to investigate what exactly happend.
Please try to "restart" widget ( resize it, or change settings ), that shoud help, while I will fix it.

Hello @g-funk ,
do you have iOS or Android app?
Can you provide a screenshot for us? I assume, that you are logged in, but you don't have access to premium features, am I right?

@tony-broom ,
Thank you for a report. I am goint to fix it now.

Hello @agchs ,
you are right, this is my mistake with "lockScreenWidget". I am going to release hotfix ASAP.
Than you for report.

Hey @ice-rabbit ,
According to what you write, the only thing I can think of is that WatchOS somehow initialized the Complication instead of the Widget. From the user's point of view there is no way to tell if it is a complication or a widget, the only indicator is the WatchOS version. For WatchOS7 and 8, Complications ( Apple complication kit ) are used and for WatchOS10, WidgetKit is used. When updating, the migration from Complication Kit to WidgetKit takes place, but it has been my experience that sometimes, for reasons I don't understand, WatchOS will use Complication, but Complications reload is disabled in WatchOS10.
I would try removing that middle Complication, restarting Apple Watch, and then adding it again. If that doesn't help, we can troubleshoot it further, using the custom version with debug logs so I can see exactly what the problem is, but I'm hoping that reboot will work ( it's the only way to force the system to reindex widgets and complications )

After closer examination, I found that the Pois layer of the Airport is the problem. Does anyone use it?
If so, try switching or turning Pois off completely. We are working on a solution.