Remaining Weather App Issues After 32.32.10.20 Update

[4degree]

Starting with the good, everything but the weather app is working just fine after this update.  Thank you, Fitibit, for that.

Weather app issues:

1.  Within the app itself, you're supposed to be able to set up 3 locations. For me, that would be city A, city B, and Current Location.  If I include Current Location in my group of 3, the weather app auto removes city B a short time later.  This happens every time I set it up.  I consider this very poor quality on Fitbit's behalf considering that may excellent Android weather apps support multiple locations, including combinations of defined cities and wherever your current location happens to be.  

2.  Current location behavior on my watch - if I'm lucky, at most I will see weather for the current location 2x/day.  The rest of the day I only have weather for hard coded city A.  In other words, the "current location" location comes and goes randomly.

Please prioritize fixing both of these.  App behaviors with random issues are not reflective of a quality product and quality software to support it.  Thank you.

[Jingtseng]

weather apps from any source can be finicky - I can't speak to the first issue (although, is City B often the same as your Current Location?), but issues with Current Location often have to do with the availability of weather reporting locations, and possibly GPS.  Most apps will pull your current location as the closest weather reporting station to your location, but that could be quite far (conceivably, there could be a limit on how far away it will report as current location, and if nothing is in range....?).  If you are between two stations, it could flip randomly as you move about.  

So the issues could be a matter of GPS (which relies on your phone, in which case, maybe just use a phone weather app, which would be more convenient generally) or weather reporting stations...

[4degree]

These are good thoughts, and I appreciate the feedback.  To your point about city B being the same as my current location and that being the reason the app drops city B, not sure if that applies; let's see if Fitbit development will respond and advise if there is logic in the app to delete a city if it's the same as the current location.  This week I actually am in and out of city B during the day, but at one point I had 3 locations available to display, city B, city A, and city B again because that's where I was. I think it would be a very poor design to delete a city because you happen to be there at the moment, because you could leave city B at any time.

Throughout the day I am between several locations, but all are densely populated suburban areas, and another weather app on my phone updates to my current location within an hour.  So I would expect Fitbit to update and display my current location with the same consistency.