emailLinkSignIn not working
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- authentication, frontend
Research direction
Start at the StyledFirebaseAuth entry point and reproduce the flow with firebaseAuthConfig.emailLinkSignIn.url set, comparing it with the working configuration without emailLinkSignIn. Trace whether clicking the email link invokes signInSuccessWithAuthResult and confirm that the user is signed in and redirected to the configured URL.
Written by the indexing model from the issue text.
Description
When setting firebaseAuthConfig (to be given to StyledFirebaseAuth), if emailLinkSignIn
is set and url inside it is defined, the sign-in is not successful, in the sense that clicking the email link won't sign the user in (and the signInSuccessWithAuthResult callback is not invoked --- this is where I set cookies and only if the cookies are set can a user be identified as having signed in). If I don't set emailLinkSignIn then everything is working fine.
What could be the problem, and how could it be fixed?
P.S. Just a note that when I have emailLinkSignIn set, I do see the url is visited but somehow the sign-in is not successful.
Another note: if I'm already signed-in, then including emailLinkSignIn and going through a new sign-in (an email is entered, the link is clicked) will send me to the url inside emailLinkSignIn successfully.
Updated: I've found out that if url points back the auth (it's where I ask for the emails) then it will be a success. I don't understand the current behaviour or if I'm using it correctly. Any help will be appreciated.
Thanks!
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 246
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firebase/firebaseui-web-react
-
This Project Is Dead Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
firebase/firebaseui-web-react#292 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 1/100
firebase/firebaseui-web-react#280 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
firebase/firebaseui-web-react#220 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
firebase/firebaseui-web-react#210 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
firebase/firebaseui-web-react#201 · 1 comment · 1 reaction ·
All issues in firebase/firebaseui-web-react
Similar issues
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
georgestephanis/p2026#40 ·
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Margaret-Petersen/food-delivery-app-clone-react-native#1981 ·