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
I lost my account and Invitation Code because of this bug and #2131
I find that my Email in github was Windelly@qq.com,but my email in follow was windelly@qq.com. Maybe that's the reason I got a new account when I tried to login another device via Github.I changed the Email in github and login again,now I got a new account and lost Invitation Code.
Can I get a new Invitation Code?
Feed Info
This bug is not about feed
Reproduction Video
No response
Environment
No response
Validations
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
This issue is valid
Contributions
I am willing to submit a PR to fix this issue
I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
The text was updated successfully, but these errors were encountered:
There are currently some issues with our email delivery service, please wait a moment
But I have already login with my Github account and overwrite my account.Can I get my old account back(with Email windelly@qq.com and empty Unique Identifier )? or Get a new Invitation Code.
Describe the bug
I tried to login throw email, and tried to get my password back via https://app.follow.is/forget-password
I didn't receive any email, not in spam.
I lost my account and Invitation Code because of this bug and #2131
I find that my Email in github was Windelly@qq.com,but my email in follow was windelly@qq.com. Maybe that's the reason I got a new account when I tried to login another device via Github.I changed the Email in github and login again,now I got a new account and lost Invitation Code.
Can I get a new Invitation Code?
Feed Info
This bug is not about feed
Reproduction Video
No response
Environment
No response
Validations
Contributions
The text was updated successfully, but these errors were encountered: