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

Getting incorrect CORS 403 Error, resolves if I delete the Firebase function and re-deploy #193

Open
ahill187 opened this issue Apr 12, 2024 · 1 comment
Labels
waiting for customer response Issue is on hold awaiting more information from OP

Comments

@ahill187
Copy link

ahill187 commented Apr 12, 2024

Description

I deployed a Firebase Cloud Function which should not have been throwing a CORS error, since all my other cloud functions are called using the exact same code/headers/tokens etc and they are all working perfectly fine.

I get the following error message in the logs when I call this cloud function:

"The request was not authenticated. 
Either allow unauthenticated invocations or set the proper Authorization header. 
Read more at https://cloud.google.com/run/docs/securing/authenticating 
Additional troubleshooting documentation can be found at: 
https://cloud.google.com/run/docs/troubleshooting#unauthorized-client"

This error message is incorrect, it is not a CORS issue.

I deleted the failing cloud function and re-deployed, and now it works. I'm not sure what is going on, but obviously the error message being thrown is incorrect.

@exaby73
Copy link
Contributor

exaby73 commented Apr 18, 2024

Hey @ahill187. Can you give me a code sample I can try to use to reproduce the issue? It can be one with minimal code, without any business / proprietary code. Thank you

@exaby73 exaby73 added the waiting for customer response Issue is on hold awaiting more information from OP label Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for customer response Issue is on hold awaiting more information from OP
Projects
None yet
Development

No branches or pull requests

2 participants