bmaroti9 / Overmorrow

minimalist colorful weather app
GNU General Public License v3.0
174 stars 7 forks source link

Error searching for locality #14

Closed er2de2 closed 4 months ago

er2de2 commented 4 months ago

When I search for my locality I get this error

Screenshot_20240519-124557.png

bmaroti9 commented 4 months ago

Hmm, it seems like it dies when fetching for the data. Some quick questions: does this only happen for Dobra? If you change languages does it work? Interestingly if i search for the same place it works.

er2de2 commented 4 months ago

Yes, only when I search for my locality Dobra. In my case it does not work in every language Strange, because until this morning it was ok. When you search Dobra select the fourth locality

bmaroti9 commented 4 months ago

Could you check if the search provider in the settings page is set to wearherpi? The open-meteo search provider could be the cause as it sometimes gives places with certain parameters missing, indicating the null check.

On Sun, May 19, 2024, 2:28 PM er2de2 @.***> wrote:

In my case it does not work in every language Strange, because until this morning it was ok. When you search Dobra select the fourth locality

— Reply to this email directly, view it on GitHub https://github.com/bmaroti9/Overmorrow/issues/14#issuecomment-2119219635, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYETV3XSVU5AL634CTDBPLTZDCLITAVCNFSM6AAAAABH6IO2DKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGIYTSNRTGU . You are receiving this because you commented.Message ID: @.***>

er2de2 commented 4 months ago

On wearherapi it detects the location with no problem. Yesterday strange things were happening :). Searching for my locality on https://open-meteo.com/en/docs/geocoding-api#name=Dobra returns good results,my locality is on the fourth position. Searching in the app returned only localities from Romania. I reinstalled the app and now everything is ok

bmaroti9 commented 4 months ago

I don't really know what could have happened. I tried all kind of different settings but it always found the place for me. I guess it's good it's fixed, though it still could come up later... I would like to implement a way to report the stacktrace when this sort of thing happens, sometime in the future, to help solve these types of problems. But I guess since it got fixed... I will go ahead and close it. :)