+Kacher82 Posted March 7, 2018 Share Posted March 7, 2018 I have been trying to get GSAK to link to Geocaching via the API. When I try to authorize it, I first get a window saying my access has been authorized, immediately followed by a message box with the message "The Groundspeak api has returned the error 'Not authorized'. The most common cause of this error is an expired or corrupt token. Would you like to try and fetch another token now?" If I select "yes", it just repeats the process, again ending in the same error. I have tried everything I could find on GSAK forums, and just now completely uninstalled GSAK and reinstalled it, with the same result, so it doesn't seem to be a problem with GSAK. Anyone else have this issue, that could give me some ideas? Quote Link to comment
+Kacher82 Posted March 7, 2018 Author Share Posted March 7, 2018 I've also tried revoking the permission from the Geocaching website, to have a fresh start. That didn't work, either. Quote Link to comment
+ktom413 Posted June 4, 2019 Share Posted June 4, 2019 I'm having this same issue right now - not sure what to do! Tried a different account, will try revoking access and re-installing GSAK. Wish me luck! Quote Link to comment
Keystone Posted June 4, 2019 Share Posted June 4, 2019 Make sure you're using the current version of GSAK (v.9.0 or higher), that's connected to the new version of the API which just came into effect. Quote Link to comment
+Team-S. Posted June 5, 2019 Share Posted June 5, 2019 I had the same problem when I switched to GSAK version 9. Then I switched to version 8.7.0.0 and the token worked again. Now the token has been rejected since yesterday and I should update to version 9. I did that. But now I get the same error message again. I now have this effect on 3 different PCs. I also tried to install the new token using the different methods. These are reported as successfully installed, but there is still the problem with the token when accessing the GC server. Quote Link to comment
+kittyshrink Posted June 6, 2019 Share Posted June 6, 2019 I went down the same rabbit hole before finding the solution: Select “NO”. If you haven’t already, update to v9 (there should be a little reminder box lower right corner). Then click the Geocaching.com tab: dropdown menu items should have the word ”New” in from of each. Select the one that says something about fetching a new token. 1 Quote Link to comment
+Randy58 Posted June 11, 2019 Share Posted June 11, 2019 The aforementioned suggestions did not work for me. Today I accessed my geocaching.com account and viewed my list of "authorizations" and GSAK is not listed for me. Note: prior to viewing the list, I renewed the token on GSAK. I feel like I am going backwards. Quote Link to comment
+CROSSBENCH Posted June 11, 2019 Share Posted June 11, 2019 I am getting the same problem as the rest of you and have contacted geocaching HQ re this issue, and have had no solution as yet from the of how to sort the problem Quote Link to comment
+GeoTrekker26 Posted June 11, 2019 Share Posted June 11, 2019 Did you do what Keystone advised in the 4th message above yours? If not, you should. If you did and still have problems you need to provide more details. (In case you don’t follow the forums, the upgrade is free.) Quote Link to comment
+hal-an-tow Posted June 12, 2019 Share Posted June 12, 2019 If you haven't already, try the suggestions here where GSAK specific advice is available. It seems a few people have had problems with duplicate user names and security software, but otherwise there is little recent report of such problems. 1 1 Quote Link to comment
+Randy58 Posted June 12, 2019 Share Posted June 12, 2019 I download the GSAK Freeware onto a new computer. Downloaded the update. Attempted to update the token. Got the message that it was successful. Tried to download PQ's and got the dreaded unauthorized token / corrupt message. I accessed Project GC com, did the "authentication" thingy. Got the message that I successfully "authenticated" my geocaching account. I then visited my profile on Geocaching.com and looked at my list of authorizations and GSAK and Project GC were not listed. The only items authorized is my Garmin and the geocaching forum. I feel like a GSAK junkie as I am spending crazy time on trying to get it to work properly. Quote Link to comment
+Randy58 Posted June 13, 2019 Share Posted June 13, 2019 Success! I changed my geocaching.com user name from "Giz" to Randy58. For whatever reason, changing the user name allowed the process to work and I was able to download the pocket queries. Observation: I wonder if my old user name caused conflicts with the API and Token Renewal. Was it a question of the old name? Did it have to do with quotation marks around my old user name? Did the Russians hack my account? Quote Link to comment
+kunarion Posted June 13, 2019 Share Posted June 13, 2019 47 minutes ago, "Giz" said: Success! I changed my geocaching.com user name from "Giz" to Randy58. For whatever reason, changing the user name allowed the process to work and I was able to download the pocket queries. Observation: I wonder if my old user name caused conflicts with the API and Token Renewal. Was it a question of the old name? Did it have to do with quotation marks around my old user name? Did the Russians hack my account? There have been some weird things going on around Geocaching.com with symbols and spaces in user names. IOS has been the culprit at times. Here's an article about quotation marks: https://www.howtogeek.com/344310/how-to-turn-off-smart-punctuation-on-your-iphone-and-ipad/ Quote Link to comment
+Randy58 Posted June 13, 2019 Share Posted June 13, 2019 kunarion, Thank you for forwarding the article about IOS and punctuation. I stumbled across this topic earlier in the year because I was unable to log into my geocaching app on my iPhone. Finally figured it out. Thanks again, appreciate you sharing this. Quote Link to comment
+Artemis&Apollo Posted June 19, 2019 Share Posted June 19, 2019 I too had this problem and with a special character in our username I was concerned. But I used the following GSAK forum to resolve the issue. https://gsak.net/board/index.php?showtopic=34380&st=20 Quote Link to comment
+Bush_Doc Posted July 7, 2019 Share Posted July 7, 2019 I was getting the same messages as above. I have been using GSAK under 2 user names and it appears it was messing with the new API token generating the "unauthorised" error. If you check under the "new" Geocaching.com access tab (Version 9.0+) at the bottom you can see how many user names you are trying to access geocaching.com from GSAK. The new API will only work with one user name. If you have more than one you will have to remove all but one of the accounts. Worked for me. Quote Link to comment
Keystone Posted July 7, 2019 Share Posted July 7, 2019 I am using GSAK v9.0 with four, count 'em, four, premium usernames. I've had absolutely no issues. Each GSAK menu username matches its Geocaching.com account name, regarding capitalization, spacing, etc., and each account is authenticated properly for the API. 1 Quote Link to comment
+LHCper Posted August 7, 2019 Share Posted August 7, 2019 (edited) I encountered this problem today after downloading GSAK 9. Had not been using my old GSAK installation for over a year. But I think I solved my problem. Did log in in the browser showing in GSAK, but still had problems. So I logged out from two of my other browsers (two other I were not logged in to). When retrying to get a new authorization token I choose to log into as another user (but selecting same user). This seemed to work, and I managed to update the caches in the current database. Good, that means I can be using GSAK for some more time. (Forgot one thing - I only have one account in my GSAK installation. So that was never a problem.) Edited August 7, 2019 by LHCper Adding information about number of accounts Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.