Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CurrentUser is always null on the first call of app.auth() #155

Closed
qcdyx opened this issue Nov 4, 2023 · 1 comment · Fixed by #167
Closed

CurrentUser is always null on the first call of app.auth() #155

qcdyx opened this issue Nov 4, 2023 · 1 comment · Fixed by #167
Assignees
Labels
bug Something isn't working

Comments

@qcdyx
Copy link
Contributor

qcdyx commented Nov 4, 2023

Describe the bug

const currentUser = app.auth().currentUser;
if (currentUser === null) {
return null;
}

In the profile-service.ts file, the app.auth().currentUser always returns null on the first call.

Steps/Code to Reproduce

  1. Login
  2. Refresh the Account page
  3. Click Generate Access Token
  4. It's not generating a new token

Expected Results

It should generate a new access token.

Actual Results

It fails silently, and displays the previous token saved in the store.

Screenshots

Screenshot 2023-11-09 at 9 45 14 AM

Files used

No response

Additional notes

No response

@qcdyx qcdyx added the bug Something isn't working label Nov 4, 2023
Copy link

welcome bot commented Nov 4, 2023

Thanks for opening your first issue in this project! If you haven't already, you can join our slack and join the #mobility-database channel to meet our awesome community. Come say hi 👋!

Welcome to the community and thank you for your engagement in open source! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants