Are there any news regarding the switch of Geocaching4Locus from the old to the new Groundspeak API?
Retiring date of the old API is getting closer and closer ...
Hi Thomas, best to ask developer directly or check this add-on public repository here: https://github.com/arcao/Geocaching4Locus/issues/96
Unfortunately, I also do not have any news.
I emailed Arcao - no response. Looked on the public repository and it doesn't seem to show any recent activity. I am seriously worried that we will soon be struggling to use Locus for caching.
Hmm, that may be a problem ... we will see at the start of May. Then I'll try to do something with it ... (push Arcao a little or start coding by myself ...)
Quote from: Leeds Tyke on April 23, 2019, 19:59:26
I emailed Arcao - no response. Looked on the public repository and it doesn't seem to show any recent activity. I am seriously worried that we will soon be struggling to use Locus for caching.
You can still use Locus for caching. But you might have to deal with GSAK.
I use GSAK for cache management on the PC. It's much faster, clearer and much more convenient than Phone and Tablet.
Then the phone and tablet are automatically synchronized via WLAN and Locus goes completely offline. There are no API problems.
Logging is also possible via GSAK.
Is there any news about an update of Geocaching4Locus? The 1st of May has already come...
Because a lot of geocaching functions are implemented directly in Locus and for me it isn't complete clear what's in Locus/addon ... what functions are only in this addon available?
Means ... what wouldn't work if the addon isn't adapted?
For me the app is still working perfectly. Seems that the change of API hadn't had any negative effect.
Or are both APIs working on GS side for an overlapping period of time?
I wrote to Arcao a few days ago, but still no response. He is not active on Facebook, no changes on his GitHub account. No idea what happens.
And still working ... it should stop work on 1. 6. 2019. Groundspeak increased their dead-line till the end of May.
Thanks for your feedback.
It's strange, the addon was always maintained regularly....
I had contact with arcao today. The API is in progress.
https://github.com/arcao/Geocaching4Locus/issues/96
... and the new version is online 8) .... and seems to work. ;)
Unfortunately, for me it doesn't work. I'am redirected to the geocaching.com page, log in, see that logging in is successful, click on "Agree", then get back to Locus with the message:
"Because my login has expired (after 90 days) you're logged out. Please log in again" (but then in Dutch).
Tried multiple times, rebooted, restarted Locus Pro, but unfortunately: no success. Could this have to do with the new API?
I am using Geocaching4Locus 2.2.6 (17878f9) and Locus Pro 3.38.3.
Hmmm, for me it's working on two different devices in Pro and Beta.
... and it's faster then Locus with loading map parts. 😉😁
In your geocaching profile -》settings-》authorisized/trusted apps ( don't see the english word) ...
You can see if access is granted to geocaching4locus ... maybe you can see there something helping infos.
I tried that, and G4L was listed indeed. Then I revoked access. G4L asked for permission on my smartphone. I entered my credentials, and G4L was shown again on the GC.com API access page. But still, Locus cannot connect, and I see the 90 days timeout popup again.
I don't understand what's wrong. Can I create a debug report somehow?
Just an idea ... maybe Locus native access is expired. :-\
I'm sorry, but I don't know what is Native Access. Could you give me a hint.
Ohh, you're right. ::)
I thought that there is a special authorisation for Locus if you use it without G4L.
But I couldn't see it too ...
Quote from: JGeo on June 04, 2019, 09:40:42
I am using Geocaching4Locus 2.2.6 (17878f9) and Locus Pro 3.38.3.
I had the same issue (still on Locus Pro 3.37.x). Should be the new API. After updating G4L to new version 3.0 and logging in once again everything works perfect.
I fixed it by removing the G4L app and re-installing it. :D
First off, a big thank you for updating G4L for the new API.
I did find one glitch with 3.0.0. When you "Download logs" from the Locus share menu, it also downloads log image thumbnails as usual, but in reverse order. For example, my two logs on https://coord.info/GC2ZTTK . (I assume it's G4L handling that.)
Sometimes you like to tell a story with the pictures, and are careful to upload them in the correct order. Groundspeak then displays them in that same order on the cache page. But for now, G4L inserts them in reverse order.
I trust that's a simple fix. Hope so. Thanks.