Login error - "Failed to find request verification token"

[Lineflyer]

At this moment some users on social media and support report this login problem.
Its also reproducible to me with current nightly build.

As the website in browser seems to work just fine, I assume it could be a website change....could still be a temporary isseu on their side though..

Lets monitor...or maybe someone can reproduce and debug right now?

[TobElf]

Same problem here :-(

[Lineflyer]

I issued a notification message to users:

The problem seems to be widely distributed right now.

[murggel]

I had the same problem, but now it is working again

Edit: I am using an older nightly-version 2024.03.29-NB-74d93a2

[TobElf]

This morning everything is working again as usual.

[Lineflyer]

I can also confirm its working again.
Notification was cleared. Seemingly a server side problem.

[Lineflyer]

Problem is back to many users, more or less 24h after last occurrence. Maybe some kind of a staged change rolling out or be tested on server side? Or just repetitive maintenance actions?

Anyway, I raised the notification again to prevent massive support mail activity.

[SammysHP]

There was a website update three days ago that got rolled back yesterday due to numerous issues. It was applied again a day later. It also includes various other major changes and I expect more breakages.

https://forums.geocaching.com/GC/index.php?/topic/397274-release-notes-website-tech-migrations-february-26-2024/&do=findComment&comment=6138533

[Lineflyer]

Anyone of @cgeo/team available and could take a look into the login problem?

The situation is now permanent and affecting all users. c:geo is completely "offline" for gc.com functions right now.

[MagpieFourtyTwo]

In this article (within the thread mentioned above), a user reported problems with setting the language of gc.com - which c:geo does first, too, AFAIK. Although this is unlikely to be the main reason for the login problems (since e. g. my setting is "English" anyway), but may perhaps also be kept in mind.

But, as unpleasant as the constant tinkerings of gc.com's "Website Specialist" team may be, it's nevertheless an interesting experience to see how meager the life of a "Basic Member" is. Actually not worth living ... hopefully a solution will be found soon.

[eddiemuc]

Hopefully fixed with PR #15547

[MagpieFourtyTwo]

Wow - good work. Especially when you consider the flood of information over there ...

Got stuck on "dateCreated" in the search expression and therefore had a look at the source code of the start page for the very first time ... unbelievable how much data is hidden in this harmless and seemingly insignificant page ... seems to be everything in there ... unbelievable. And now it's no longer surprising why it sometimes takes soooo long to load ...

[Lineflyer]

@MagpieFourtyTwo
New nightly 2024.04.04-NB1-5ad1c57 is out in case you are interested to take a look for possible other regressions.

Our tests show, that TB logging might be affected as well.

[realMrTom]

For me it still doesn't work. And checking play store there is no new version available - and I applied as a beta user.

[Lineflyer]

@realMrTom
We did not yet release a new version but this issue is closed as the bug is fixed in our code.

We are currently looking into possible other regressions (e.g. trackable viewing is kind of broken) and evaluate whether we can fix it along the way.

We will need some more time (depending on available developers) to crosscheck and potentially fix that. Or we might decide to fix additional problem at a later time.
Anyway publishing to Google Play takes additional 4-6 hours. So you might expect a new release on Google Play tomorrow at the earlist.

[MagpieFourtyTwo]

Would have been faster - if only the apk download hadn't taken aaaaages ... first even ran into a timeout, next was incomplete, and so forth ... server overload? ;)
However, tested the following issues (which did not work for me before):

• Login: WFM - but only on third attempt: first failed, second resulted in "Login OK, Basic", eventually third worked out (after a fresh start), but took 4(!) seconds until it was done
• Live Map (download of caches) - does NOT work - in Live Map I only see offline saved caches, no fresh downloads,
  no matter if PM or not (scrolled map to a region I did not visit recently - no caches in Paris, e. g.)
• Download of PM cache (via GC code): WFM (even with filled logbook ;) )
• PN upload: WFM
• Change Coordinates on website: WFM
• Refresh of a offline stored cache: WFM
• Fieldnotes upload - WFM
• Posting a Write Note log from c:geo: WFM
• Logging a PM cache plus TBs as "Visited": WFM
• delete cache log: WFM
• edit cache log: WFM
• ...

WRT TB discover I'm out - do not discover anymore,

[MagpieFourtyTwo]

S/th new WRT caches in Live Map: Seems as if caches are downloaded, but not in the visible map area, only east of it ...
To reproduce:

1. swype to a map region which has not been visited before (and preferably contains no offline stored caches)
2. wait a few seconds (to give caches time to download - although you will see none)
3. in the currently visible region there are still no caches displayed
4. now move the map to the left (to see the region east of current section) BUT DO NOT LIFT YOUR FINGER
5. some caches will show up at the right display border, either in an vertical oval or vertical line
6. as soon as you lift your finger, the caches will disappear

Maybe the download order has been changed again ...?

[MagpieFourtyTwo]

As an alternative to "panning east", you can also quickly zoom out.
Effect is the same: Caches east of previous map region are shown for a second or so and then disappear.

[moving-bits]

Thanks, @MagpieFourtyTwo, for testing the new changes thoroughly. To make tracking and fixing those issues easier, may I ask to you create new issues for upcoming findings? This issue here is already closed (as the original issue is fixed), thus your new findings may easily get lost. Thanks.
(I'll open new issues for the two findings above.)

[MagpieFourtyTwo]

BTW: Caches appear in the north eastern "off" right now ... perhaps there are currently still changes going on ...?

[jobumo]

Still getting: Login failed (failed to find request verification token)
and still do not see an Google Play update....

Is it correct that (a) the problem has been identified and fixed, and (b) a public update has not yet happened. Comments above suggested that an update might come yesterday?

Any guidance would be appreciated - or a pointer to the right place to raise this. Thanks! jobomo

[moving-bits]

Yes, the login issues (and others) are caused by website changes on geocaching.com

We have a fix for the login issue already, and it's available in our nightly (developer) build, but not yet on Play Store. We will probably issue a new release in the next two days, as we want to fix other issues caused by the website changes as well.