Posts made by SimonUrbanek

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.

Hi everybody,
I am trying to induce this problem, but the units in the widgets are displayed correctly. I think the error may occur in the synchronization between the application and the widgets. Could you please try the following: In the application in the settings, switch the units to for example celsius, then refresh the widget and then again to faranhait and refresh the widget again? When you change the units in the settings, the settings in the widgets will be synchronized. It is possible that the data for the widgets has been lost and this is how it will be uploaded again. Anyway, I will check the synchronization mechanism again.

Hi everybody,
I'm trying the app on Pixel 8 pro but it works fine so far. What does the freeze look like? Does the application get stuck on the splash screen, or does it start (you see the map) and then you can't interact with it? I think it might be a storage problem. In the last version, we added storage migration for better security, and I think this is what causes it.
Could you please try clearing the app data, then the app, restart the device and then install the latest version?

The biggest obstacle is from Apple and the fact that they do not allow weather applications for Apple Car play. So even if we developed an application, Apple would not allow us to add it to the store. It's sad, so we hope that with the arrival of Car play 2, such applications will be allowed.

@Richard-Martin-5 What watchOS version do you have?

Hello @alottem @Conor-Doyle ,
Thank you for reporting.
I have been working on this problem for the past weeks and the latest version should fix this problem.
The problem is that the system greases the local storage, which the application uses to store data. For this reason, we created a backup of this data in the native iOS storage, which should be immune to this behavior. This backup must first be created (the first launch of the new version) and then it is applied when the local storage is lost.
If this behavior is repeated on the latest version, please let me know and I will continue with the solution.

Thank you all for the information.
From my observation, this is a system optimization of version 17.2. I'm addressing this as a priority now and preparing a Windy version that will store data in native Apple frameworks, which should resolve this issue. Unfortunately, this is not a simple modification.

I would be grateful for any further information.