mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 12:56:59 +00:00
[GH-ISSUE #8114] [Bug] Registering by entering the email code doesn't work #3566
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#3566
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @timas130 on GitHub (Jul 9, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8114
Bug Description
No matter how hard you try, if you don't have an account and try to log in by using the code from the email instead of following the link, you will be greeted with an error.
How to Reproduce
Expected Behavior
I am able to sign up
Operating System
Web, Linux, Android
AppFlowy Version(s)
0.9.4
Screenshots
No response
Additional Context
Happens both on self hosted instances, as well as on appflowy.com.
@khorshuheng commented on GitHub (Jul 10, 2025):
If it is appflowy.com, how's the error like? What is displayed on the dev console?
@timas130 commented on GitHub (Jul 10, 2025):
@khorshuheng
In the console:
Over the network:
@timas130 commented on GitHub (Jul 10, 2025):
I have looked at the code for a bit, and what I found is that
/api/user/verify/{access_token}doesn't get called, and this meansverify_tokendoesn't get called, which is the only place wherecreate_useris called, and so a user isn't created. Hope that helps.@khorshuheng commented on GitHub (Jul 10, 2025):
Under normal circumstances, that should not happen - verify access token should always be called by AppFlowy web before logging in. One scenario that I am aware of, that this doesn't apply, is when old access token that corresponds to non existing users was still being stored on local storage. But that can be resolved by simply clearing all the site data.
I will see if I can find a way to make sure that the user profile is always created as long as a user sign up, rather than relying on the verify access token call.
@timas130 commented on GitHub (Jul 10, 2025):
Well
/api/user/verify/..is not actually called. Here what appears in the network tab when I sign in:I think that
/api/user/verify/..is only called from/auth/callback, which I'm not visiting as I'm not following the link from the email but rather entering the email code directly.@khorshuheng commented on GitHub (Jul 10, 2025):
Yes, if verify access token endpoint has been called you wouldn't have faced this issue. What we need to find out on our end is why that isn't the case. Especially since we were able to sign up using a completely new account on our end using magic link and authentication code. I will need to retest this again.
@annieappflowy commented on GitHub (Sep 2, 2025):
@timas130 , let me know if the issue persists. Closing it for now.