-
Notifications
You must be signed in to change notification settings - Fork 71
Failure during data fetching #49
Comments
I guess it's cause of the API change by open weather map. They want you to pay for the daily forecasts. |
Thanks. It works awesome. |
Hi! How can I use the fork?? I don't understand.... Thanks |
Well the easiest way will be to clone or download the repo (my fork) and build it for your own. It's done like the README says. |
The installer would be great also because I did not understand how to do ... |
@axelv73 So I just uploaded some different versions as releases. So just pick the one you need, unzip it and start the app. It's not a installer more like ready to go :) |
@musicpro ok thanks!!! It works fine! |
Good to hear that it is working :) |
@musicpro I'm using your version. Do you have an idea why it shows "Invalid date"? |
Yeah, I noticed this too. Reason was the google api. So I fixed it and pushed it. If you need to download an executable file you can find new builds under the release tap. |
an installer would be great, because i also don't understant how to buil my own one |
@l1t1s Hej, just check the release tab on GitHub. You can download the program there. Actually there is no installer needed to use the app. |
great. thousand thanks |
@musicpro Awesome work and fix ! Quick question, is there a way to exit from the detailed day's forecast ? Like, I clicked on a day to see the temperature graph, but I have no way to exit that graph (and display the 4 days forecast again). It stays there, even if I go in the options or close/reopen the Temp window. |
@LaP0573 Sorry for the late reply and thanks for using my fix! |
@musicpro Thanks a million for patching this beloved app. For me the 'invalid date' error has come back again. I'm running your latest patched release of May 2019 (v.0.7.3). Any chance you might be able to fix this again? I would have opened this as an issue in your fork, but I think issues are disabled over there. |
@happydemic Hej, glad to hear that you like it :) So the reason for this is again the change of an API. I notice that there were a lot of request to the TimeZone API. So google decided to start charging for this and I ended up in a kinda huge bill I can't pay. Luckily I was still in the promo time and did not have to pay this one but every upcoming. This is why i had to deactivate it. Also I have to rethink the geolocation think again I guess. Caused by maybe paying for the API usage in future. IF you have suggestions feel free :) BTW I activated the issue tab on my fork, hope this will work. |
I have a key from openweather and tested it with curl to make sure it works. I enter the key into temps.app and every time I run it, it responds with
Is there a log file or a way to get more information on why / how it's failing?
The text was updated successfully, but these errors were encountered: