-
Notifications
You must be signed in to change notification settings - Fork 290
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
firebaseAuthEmulatorHost is ignored and requests to live servers are made #673
Comments
What are your versions of |
@kmjennison These are the used versions: |
Please try with Firebase v9.16.0 to see if the problem still occurs. I'm wondering if this is related to #614. |
@kmjennison No change after downgrading to 9.16.0 |
I think I have hit this issue as well, I have tried with 9.16.0. Our setup worked previously but stopped working after a few dependencies upgrades, but we are not sure which one was responsible of the issue. We are using firebase emulators in docker (using https://github.com/AndreySenov/firebase-tools-docker), I don't know if this can be related... |
@fabienheureux We didn't fix this. We stopped using this package |
Please try initializing the Firebase JS SDK yourself prior to initializing |
When filing a bug report, please confirm you've done the following:
onVerifyTokenError
andonTokenRefreshError
in your config and checked for any helpful errors? Yesdebug: true
in your config and read through server-side and client-side debug logs for any helpful messages? YesDescribe the bug
A clear and concise description of the bug.
Versions
next-firebase-auth
version: 1.0.0-beta.0Firebase JS SDK: 12.4.2
Next.js: 13.2.1
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Only requests to firebase auth emulators should be made
Debug and error logs
Additional context
![image](https://private-user-images.githubusercontent.com/12392666/253881871-622b1ca7-fd57-4c60-96fe-99a9493fc75d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNDA5NzMsIm5iZiI6MTczOTI0MDY3MywicGF0aCI6Ii8xMjM5MjY2Ni8yNTM4ODE4NzEtNjIyYjFjYTctZmQ1Ny00YzYwLTk2ZmUtOTlhOTQ5M2ZjNzVkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDAyMjQzM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRiZDUyMDk4M2ZiMDBlZTA3OTI4ZjNiOGM5YmI4YTNjYmMzZjZiODU2MjdmMGFhM2MyODk3Nzk0ZGUwN2ExNTEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.gM-_XYW1e6aAolpcUlUmlG9t7Dg23LBeiVpGY_ZRQpc)
Valid request to emulators at port 9099
Response
Invalid request to GCP servers
![image](https://private-user-images.githubusercontent.com/12392666/253881980-7a21b8db-213a-45d7-b06e-8133b46b9999.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNDA5NzMsIm5iZiI6MTczOTI0MDY3MywicGF0aCI6Ii8xMjM5MjY2Ni8yNTM4ODE5ODAtN2EyMWI4ZGItMjEzYS00NWQ3LWIwNmUtODEzM2I0NmI5OTk5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDAyMjQzM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRiOTU3ZTllOWQ5M2E2YjI4MjJjZjMxNTQ5ZmQ3YWQ0M2IzMmZhMmM1OWQ3YzIzOTJjOTVkMmQwZGFiYzU4MGQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.h3As7wkh3GKPZiZJlpcfke73klxhkdOeg65q0fCkgLU)
Response
The text was updated successfully, but these errors were encountered: