Last post by Geooh GO -
No, I cannot replicate. I can't even remember the last time getting the limit in normal use. But I also may not be doing the same steps or frequency of calls.
Last post by Geooh GO -
As I indicated, every API returns values as to how long the app must wait until another API call can be made. If some limit is reached, Geooh must wait the specified amount of time. I have no control over that.
If installing a geocache from outside the app when Geooh is not running, the app starts up and makes normal API calls needed for the app's features. If the installed geocache is an event, another API call is made to retrieve attendance information.
I have rarely ever encountered the API limit during testing... and usually some big test to force a limit check. I am not sure how you reached a limit, but it could be the event type which immediately gets additional data via another quick API call. That's why I was asking if the limit only occurred on events.
You are comparing apples to oranges in your test. You can't trigger API calls as fast as an app. And the lite status is not important... it's not the amount of data returned, it's the frequency of API calls. In fact, the API oddly allows more full caches per day than lite. Until I can replicate the same limits as you encountered, I am shooting in the dark trying to find the proper cause so the best thing now is to try what I implemented in the latest release.
I plan to display a dialog to verify the user wants to show the cache screen after download. That will hopefully add a delay long enough to appease the API.
This would be a shame. 99% of the times i click on a link for a cache it is because I want to see the cache. So if I then need to click an extra time for every cache that would really be an annoyance.
I have done a little test. I looked at the live map and got some caches on the map. These are set to be loaded as "Lite", I select the 3 vertical lines at the bottom left of the screen and get a list of the shown caches Then I select a cache and in the menu I get, I select "Show More ->" I do this 5 times for different caches as fast as possible. In my understanding Geooh would then make an API call to get the info, as the info already read is only light. But I don't get the "API limit reached" message
Shouldn't it be the same API call that is made when I click on a link to a cache?
With the current "problem" I it is only possible to look at 1 cache pr. minute if they are loaded via click on a link. I dont remember exactly what the API call limit is pr. minute, but it is more than 1 cache.
What other API calls are made when a cache is loaded via click on a link?
Last post by Geooh GO -
The official app has NO limits since it doesn't use the API.
No changes have been made to the install process in a very long time.
I plan to display a dialog to verify the user wants to show the cache screen after download. That will hopefully add a delay long enough to appease the API.
Last post by picht -
I tried to do the same with the official app, and I was not able to reach any API-limit. Tried to get 10 caches right after each other - no problem. With GO the API limit is reached after 2 caches.
This problem has not always been there. I think it started 5-6 months ago.
Last post by Geooh GO -
Nothing looks like a problem in settings. If it's happening to all cache types, It is probably just too many API calls within a particular time span. First there's the initial cache download, the opening the cache page which will in turn make API calls to get additional cache screen data. I could not automatically show the cache screen and just download into the Install list to reduce the auto API calls in sequence. I'll have to find time to test similar to what you provided. You could also see if delaying the time between extracting caches from the email runs fine. If so, that will help confirm the sequence of multiple downloads is just using up API calls. Something has to give... the app not download the cache screen or force some delay after an install, but then that could also cause complaints.
In my original post it was meant to say 2-3 events (not 32-3)
I'm not sure what to look for. I have attached the settings. It also happens on normal caches, when clicking on them from a link in an email. The first 2 clicks are OK and the the API limit is reached.
