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

Add to docs note about headers that have conflict with Firebase Auth #127

Closed
andrevferreiraa opened this issue Mar 15, 2023 · 3 comments
Closed
Labels
enhancement New feature or request

Comments

@andrevferreiraa
Copy link

I just spent hours trying to debug an issue the Firebase Auth signInWithPopup.

I was getting the error (auth/popup-closed-by-user) and after trial and error I realised it was because of the headers crossOriginOpenerPolicy & crossOriginEmbedderPolicy set by nuxt-security. It started working after I set them to false.

Just thought it could be added to the documentation since it's likely more people will encounter this.

@andrevferreiraa andrevferreiraa added the enhancement New feature or request label Mar 15, 2023
@Baroshem
Copy link
Owner

Baroshem commented Mar 15, 2023

Hey @andrevferreiraa thanks for riding an issue! :)

This is rather a very specific use case. I dont think that it needs to be added to the general docs about the module as the aim of these docs is to provide generic guidance about the usage of the module.

Apart from your example there amy probably hundreds of different cases that would be beneficial to added to the docs. And then, the documentation would become really difficult to operate.

What I can recommend right now is to not add it to the docs. If the future users will have similar problems as you have, they will probably open up the module repository and search in the issues for Firebase. And then, they will see this issue with your explanation.

I think then, this issue can be closed as not planned but will be in the history for the future users

Let me know if that works for you :)

@andrevferreiraa
Copy link
Author

andrevferreiraa commented Mar 15, 2023

Yes, my main goal with this was actually for people to see this issue when they search for this specific problem. Hopefully it will help them. Let's close it up :)

Cheers

@Baroshem
Copy link
Owner

Thanks!

Also, if you have any ideas or recommendations regarding the module, please let me know :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants