Open nolanlawson opened 7 years ago
This may be happening when a user navigates to toot.cafe/auth/signin
when they are already signed in right after going through Confirmation...
I had the exact same behaviour. I had one tab open, when the email arrived. I didn't reload the confirmation page, but went directly to toot.cafe
and all was well.
@b2m9 that sounds like you've reproduced it exactly. That report from twitter above was me, and it pretty accurately describes what I was doing. I think @Seebiscuit's point is relevant, but worth noting that going to toot.cafe/auth/signin
wasn't deliberate – the user gets redirected/forwarded there automatically, I think, which may be the issue. If the redirect/forward goes to toot.cafe
, it may avoid the problem entirely.
Hm, I'm wondering what in our code could possibly be causing this. I've never heard this reported by users of other Mastodon instances. Our change is so innocuous I really am not sure what the issue is here: tootcafe/mastodon#9 tootcafe/mastodon#10
Also I never got reports of this before merging those PRs, so I'm guessing it must be something related to that.
Many folks are reporting what appear to be cookie/redirect issues with our new passphrase-based registration system:
As someone reported on Twitter:
The relevant PRs are here: tootcafe/mastodon#9 tootcafe/mastodon#10 . Some help fixing this would be appreciated, since I'm not super familiar with Ruby. :smiley: That PR can be tested in a local Mastodon development environment.