I life in germany and we have special characters here, like äöü. They are not supported in the city names. Maybe it's the font or something else?
A simple way would be to add an option…
Thanks for helping me...
I don't think the issue in pulling data, as that code is small and well guarded. Weather and exchange rates requested every hour at the same time, one after another. Sometimes even…
Good. Looks like the issue was with access to storage on the device. It turns out there is a bug on the firmware that Garmin still unable to fix. (https://forums.garmin.com/developer/connect-iq/i/bug-reports…
This is a nice watchface. I have it installed in a Fenix 5X with 15.20 firmware. The watchface has crashed twice on me so far. The first time, when I changed field 4 to show Steps/Floors. The second time it crashed, it was just in watchface mode. And now as I'm typing this message, I see the watchface has crashed a 3rd time. All this in the past 2 hours which I have the watchface installed.
That's weird. Just checked, only two crashes were on F5X for the last week and all crashes caused by storage access issues. An only possible explanation is too many installed applications and not enough space to store settings.
I have updated the app, rebuild it on the last SDK and clean up in a couple of places but not sure that this helps.
Some info from me to help the diagnosis;
I have tracking off, so it's not goals reached.
I have only 3 watchfaces installed and 1.6 mb software storage free so it's not storage either. 4gb on the watch too but that's irrelevant.
It could be the data pull from either weather or currency, and I suspect weather as currency I believe only pulls once a day and I've had multiple crashes throughout one day.
As reported by others and myself, I don't think your crash log is accurate.
Thanks for helping me...
I don't think the issue in pulling data, as that code is small and well guarded. Weather and exchange rates requested every hour at the same time, one after another. Sometimes even more frequent, in fact, it could be once in 5 min - you just need to switch from the watch-face to any other widget and then switch back, to initiate pull data requests.
So, if it was a web request issue, you'd notest that WF crashes every time when you trying to switch back to WF or receiving a notification from the phone.
Another thing is that crashes happened mostly on 5X, so I suspect that 5X does not support some features that WF is using or some times the system returns unexpected results.
The crash log is provided by garmin and it turns out it useless.