You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the Geocaching side of oAuth has stopped returning homeCoordinates as a part of the data structure. By looking at your code I assume your tests will fail due to this.
I will try to ask them if it's intentional. The data can still be retrieved with the API method /v{api-version}/users/{referenceCode}. But in my case it means an extra http call upon every oauth. On the other hand I guess most API partners don't use the home coordinates for anything.
The text was updated successfully, but these errors were encountered:
I think the default fields that are returned by the API have changed. To my knowledge (and from what I can find in git) Project-GC hasn't used $provider->setResourceOwnerFields before. But now when I added that and included homeCoordinates I am seeing them again.
I am currently waiting on more confirmations that my current code works for all the users. I have had some that have had issues logging in. This while I haven't seen any issues myself yet. I have logged out and in again a lot, and also removed some related data in the DB for my user. But I have had a bit too much success. Hard to test and debug without reproduction cases. :/
This is mostly an FYI.
It seems like the Geocaching side of oAuth has stopped returning
homeCoordinates
as a part of the data structure. By looking at your code I assume your tests will fail due to this.I will try to ask them if it's intentional. The data can still be retrieved with the API method
/v{api-version}/users/{referenceCode}
. But in my case it means an extra http call upon every oauth. On the other hand I guess most API partners don't use the home coordinates for anything.The text was updated successfully, but these errors were encountered: