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

Approriate Failure Reason. #1378

Closed
Abhishek-90 opened this issue Aug 10, 2023 · 4 comments
Closed

Approriate Failure Reason. #1378

Abhishek-90 opened this issue Aug 10, 2023 · 4 comments
Assignees

Comments

@Abhishek-90
Copy link

Describe the bug
I faced an issue while creating a new firebase project from Rowy. The issue was that my firebase authToken expired. But it was initially unclear to me because this reason was not visible to me unless I opened the console to check for logs. An error box appeared in the bottom left corner but it didn't display any message(check attached screenshot). If the message box displayed the reason it would be better rather than opening console.

It can be a good first issue and I would like to take it up.

Expected behavior
The error box(in bottom-left) to display appropriate error message.

Screenshots

Screenshot_1

Desktop (please complete the following information):

  • OS: Windows
  • Browser: Chrome
@shamsmosowi shamsmosowi assigned shamsmosowi and il3ven and unassigned shamsmosowi Aug 10, 2023
@Abhishek-90
Copy link
Author

Can I take this issue?

@harinij
Copy link
Member

harinij commented Sep 7, 2023

Hi @Abhishek-90 - this needs a bit of investigation to ensure this is a frontend issue vs backend.

cc @il3ven who will be looking into this adding comments.

@il3ven
Copy link
Contributor

il3ven commented Sep 7, 2023

@Abhishek-90 How can I reproduce this? From where does it originate? I think firebase handles refreshing of tokens so we shouldn't see this error in the wild. Anyway, if it is reproducible we can add an error message.

@il3ven
Copy link
Contributor

il3ven commented Sep 14, 2023

@Abhishek-90 Thanks for reporting this. I was able to find the reason and replicate it. It has been fixed internally.

@il3ven il3ven closed this as completed Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants