Existing users login issues

[mdroidian]

As we know, some existing users are experiencing login issues after the migration. Relevant slack thread.

Users in the thread have mentioned

• that they can log in via different browser (or incognito)
• clearing cookies / cache did not help

I imagine the issue has something to do with a pre-existing roamjs:oauth-google:{graph} local storage object.

Noting my superficial exploration so far for future me:

• index.ts > settings.panel.create (Log in) > roamjs-components OauthPanel

Probably related: #9
Tagging @dvargas92495 for visibility as he was working on this issue recently

[dvargas92495]

if it has to do with local storage, logging out and back in should fix. I'm seeing some undefined errors now

[dvargas92495]

Actually that id issue is Dropbox related and should now be fixed. I'll keep an eye out for any google-related emails

[mdroidian]

When I log out and log back into Roam, or Delete all ... from https://myaccount.google.com/connections, the localStorage key still exists.

2023-07-26.11-25-16.mp4

But I am now doubting my original hypothesis because the user is reporting seeing "Login with Google" which seems to only exist when the value is empty.

[dvargas92495]

it's probably disappears bc it's crashing after the error - it's existence is not dependent on whether there's a value set there or not.

That 500 should be a clue - let's see if there are any errors sent

[mdroidian]

Here's what I meant about the value being set:
If I remove the value, I see Login with Google.
If I set a fake value, I see Add Another Google Account as if I'm logged in.

2023-07-27.11-59-04.mp4

RE: 500 error
Nice catch, I wasn't looking for that. More often than not it doesn't show up. And it doesn't seem to affect my ability to login.

2023-07-27.12-10-30.mp4

Continued auth request
Another think I noticed is that sometimes it will continue requesting. @ 45 seconds in

2023-07-27.12-12-26.mp4