Posts made by SimonUrbanek

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.

@alottem One more thing: when this happens, do you see the onboarding screen with the unit's settings?

Hello @alottem, thank you for reporting this. We are currently working to fix it, and our main theory concerns disk space on the iPhone. Can you please tell me which iOS version and Windy version you have? What login option do you use (email, login via Apple, Google, Facebook)? How often does it happen?

This information will really help us to resolve the issue.

Hello @Joe-Kondratko ,
I am sorry for a late answer,
please witch version of iOS do you have? And in application are you logged correctly?

I have reviewed the app you mentioned, but its widget only offers favorite spots, not favorites and search any locations combined (looks to me, that is not a search, but filter).
Unfortunately, the Apple API does not permit this, which is disappointing because having favorites listed first would be beneficial.
I recommend exploring iOS focus mode. You can create separate focus modes for private and public use, organizing different apps and widgets on your home screen to enhance privacy (https://support.apple.com/en-gb/guide/iphone/iphd6288a67f/ios).
Regrettably, I am unable to provide further assistance at the moment.

@slimothy said in Widget Location from Favorites List:

@Ondřej-Šutera Strange, maybe it was a glitch, but mine used to show a Favorite location label rather than a street address.

I agree with you, let's give the best solution to offer all possibilities by adding Favorites to the list. So people can type in a street address, or a Favorite name. That way they have ALL possibilities to choose their location.

It is technically unfeasible because iOS generates settings based on widget intent declarations, and we lack access to the search field due to system limitations.

Hello @gdtrfb ,

I hope this message finds you well. As was previously mentioned by @Ondřej-Šutera , I have been occupied with the recent developments surrounding Apple's restrictions, which have rightfully taken precedence in my priorities. However, I wish to assure you that I have not overlooked the matter of implementing locations in widgets.

In contemplating this issue, I have given considerable thought to the approach we should take. One option is to adopt a similar approach as with the old complications, where the default location was chosen due to technical constraints. Nevertheless, I am inclined to explore alternative avenues for widgets. While it would be simpler to follow the default location approach, I believe it may not be the most accurate course of action. Therefore, I have chosen the more intricate path, one that will enable widgets to support all user-defined locations on their respective watches.

I must emphasize that this decision will necessitate more extensive modifications within the application. It will undoubtedly pose challenges and consume more time, but I firmly believe it to be the most correct and comprehensive approach.

Thank you for your understanding and patience as we work towards enhancing the functionality of our widgets.

Hello @carpediemi24 ,
Thank you for reporting the bug. Widgets since watchOS 10 have completely new refresh logic and it is possible that there was a problem with the primary location. I've tried it now on my AW and it also shows me a different current location. I'll try to fix it for the next version.

Hello @seeyou186,
According to your screenshots it seriously looks like a bug. I'll take a closer look. Please let me know what version of the app it is, because in the last update the watch widgets have changed completely ( under the hood )

Hi @Tony-Norris ,
Thank you for the report, this problem also occurred on my iPad ( iPhone is fine ), so I will be able to fix it. I'll keep you posted on the fix, or ask you for more information.

Thanks for the report, there really was a problem in the small lock screen widget and it was fixed. I haven't found a problem with the premium widget yet, but I'll look into it again and let you know.

Hello @Brancis ,
In the last version I modified the switching of 1H and 3H predictions so that it is switched only in 2 cases, namely

1. The user logs out of the iPhone app
2. The user's premium expires.

Previously there was one more option that if I have a non-valid token, it switches, but I have cancelled that. This way it can happen that he has 1H prediction ticked and it shows him 3H, but the build should be quite minimal and it should fix itself. It can happen when you don't turn on either the watch or the iPhone App for a long time, and you have a background task on the watch that refreshes that token blocked by the system.

Please email me, in what situation, does the forecast switch and I will take a look at it again

Hello @Brancis ,
In the last update, I modified the logic regarding 1H settings, the app should no longer switch back to 3H forecast.
If this is still happening, please let me know in what situation it occurs and I will look at it again.
At the moment it changes the 1H forecast to 3H in the following situations:

• The user has logged out of Windy
• User has run out of premium

I have prevented a situation where the validation token has expired, which could just be causing the behavior described ( settings will remain unchanged, but the forecast will be non-premium ). This situation should occur minimally ( when the apple watch or iPhone app hasn't been running for more than 3 days ) and the user has no complication on the watchface and the system won't allow a background update. As soon as it is restarted premium will be restored.