You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
firestore CREDENTIALS Error when deploying firebase cloud function written in python #126
i have code like below in for firebase cloud function in main.py.
when i test function using firebase emulators:start --only functions it worked perfectly
now when i try to deploy it using firebase deploy --only functions it gave me below error while pointing to db = firestore.client()
line in code
error
"""""""""
raise exceptions.DefaultCredentialsError(_CLOUD_SDK_MISSING_CREDENTIALS)
google.auth.exceptions.DefaultCredentialsError: Your default credentials were not found. To set up Application Default Credentials, see https://cloud.google.com/docs/authentication/external/set-up-adc for more information.
"""""""""
code
"""
from firebase_functions import https_fn, options
import firebase_admin
from firebase_admin import firestore
app = firebase_admin.initialize_app()
options.set_global_options(timeout_sec=1000)
db = firestore.client()
firebase function that write something to firestore database is written below
"""
[REQUIRED] Steps to reproduce
use above code in main.py inside functions folder and try to deploy functions you will get same error
[REQUIRED] Expected behavior
credential should be automatically added since i am logged into my account using firebase login and using correct Project ID. it did not ask for credential when i was tasing using firebase emulators:start --only functions and it was working perfectly.
changed the title [-]firestore CREDENTIALS) Error when deploying firebase cloud function written in python[/-][+]firestore CREDENTIALS Error when deploying firebase cloud function written in python[/+]on Aug 10, 2023
Hi @Daxitdon, thanks for filling this issue. I was able to replicate the behavior you mentioned. I tried to deploy the code snippet you provided and an error was raised. Let me notify our team about this issue so that we can provide more context about this and investigate this behavior.
I've set up GOOGLE_APPLICATION_CREDENTIALS, but still no luck. What's weird is that it was allowing me to deploy this morning without this issue.
Maybe related, maybe not, I think I was able to write to Firestore db from my local cloud function before I setup the credentials - at least, I'm fairly certain I hasn't set it up, unless something was set up automatically when I logged in Firebase via the browser auth workflow.
My Firestore rules look as follows:
rules_version = '2';
service cloud.firestore {
match /databases/{database}/documents {
match /{document=**} {
allow read, write: if false;
}
}
}
I've discovered if I move the db = firestore.client() into my cloud function, I'm able to deploy.
Reacted by Oukly, Paweł Pajewski, Diego Moreno, Johnny Oshika, daStroob, Cedric Fitzgerald, Albert Sokol, park.youngho, Dmitrii and Wesley de Souza Tavares
Reacted by Dimas Saputro, Paweł Pajewski, Yam Horesh, Kürşat Kaya and park.youngho
Hi folks, it looks like this issue is happening during our code discovery process. That process involves "running" your code and it looks like the creds aren't being passed to that process. For now, use the workaround above. I'm gonna move this issue over to the python sdk repo. thanks
Hey, I'm actually having the same issue during firebase deploy in GitHub actions. I'm using 2 different ways setting service account creds for the action:
Using google-github-actions/auth@v1, like this:
- name: Authenticate to Google Clouduses: google-github-actions/auth@v1with:
credentials_json: '${{ secrets.SERVICE_ACCOUNT }}'
File "/home/runner/work/family-finance/family-finance/functions/venv/lib/python3.11/site-packages/google/auth/_default.py", line 691, in default
raise exceptions.DefaultCredentialsError(_CLOUD_SDK_MISSING_CREDENTIALS)
google.auth.exceptions.DefaultCredentialsError: Your default credentials were not found. To set up Application Default Credentials, see https://cloud.google.com/docs/authentication/external/set-up-adc for more information.
127.0.0.1 - - [01/Oct/2023 20:34:52] "GET /__/functions.yaml HTTP/1.1" 500 -
[2023-10-01T20:34:52.253Z] Got response code 500; body <!doctype html>
<html lang=en>
<title>500 Internal Server Error</title>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p>
127.0.0.1 - - [01/Oct/2023 20:34:52] "GET /__/quitquitquit HTTP/1.1" 200 -
Terminated
The interesting thing is that the 1st approach works for functions written using Node.js, I have a different repo with proper deploy setup through GH actions, which I thought I would be able to reuse with Python 🤷
Before you ask, the SERVICE_ACCOUNT I'm using is properly generated in GCP Console with proper permissions.
(Updated) Sorry, I just noticed that it's getting addressed in firebase/firebase-tools#6274, feel free to ignore the text above 🙂
Hi folks, it looks like this issue is happening during our code discovery process. That process involves "running" your code and it looks like the creds aren't being passed to that process. For now, use the workaround above. I'm gonna move this issue over to the python sdk repo. thanks
@colerogers , I can see your pull request for fixing this issue is not merged yet. Any update on this issue?
Activity
[-]firestore CREDENTIALS) Error when deploying firebase cloud function written in python[/-][+]firestore CREDENTIALS Error when deploying firebase cloud function written in python[/+]aalej commentedon Aug 15, 2023
Hi @Daxitdon, thanks for filling this issue. I was able to replicate the behavior you mentioned. I tried to deploy the code snippet you provided and an error was raised. Let me notify our team about this issue so that we can provide more context about this and investigate this behavior.
mikeknapp commentedon Aug 16, 2023
+1 I'm having the same issue on Windows.
I've set up GOOGLE_APPLICATION_CREDENTIALS, but still no luck. What's weird is that it was allowing me to deploy this morning without this issue.
Maybe related, maybe not, I think I was able to write to Firestore db from my local cloud function before I setup the credentials - at least, I'm fairly certain I hasn't set it up, unless something was set up automatically when I logged in Firebase via the browser auth workflow.
My Firestore rules look as follows:
mikeknapp commentedon Aug 16, 2023
I've discovered if I move the
db = firestore.client()into my cloud function, I'm able to deploy.Daxitdon commentedon Aug 16, 2023
Great find!. I guess we have to continue doing it until the issue is resolved.
colerogers commentedon Aug 17, 2023
Hi folks, it looks like this issue is happening during our code discovery process. That process involves "running" your code and it looks like the creds aren't being passed to that process. For now, use the workaround above. I'm gonna move this issue over to the python sdk repo. thanks
LogansUA commentedon Oct 1, 2023
Hey, I'm actually having the same issue during
firebase deployin GitHub actions. I'm using 2 different ways setting service account creds for the action:google-github-actions/auth@v1, like this:GOOGLE_APPLICATION_CREDENTIALS, like this:In both ways I'm getting the same error:
The interesting thing is that the 1st approach works for functions written using Node.js, I have a different repo with proper deploy setup through GH actions, which I thought I would be able to reuse with Python 🤷
Before you ask, the
SERVICE_ACCOUNTI'm using is properly generated in GCP Console with proper permissions.(Updated) Sorry, I just noticed that it's getting addressed in firebase/firebase-tools#6274, feel free to ignore the text above 🙂
Cazforshort commentedon Jul 30, 2024
Can this be added to the docs as a warning so others don't spend a ton of time trying to figure out why its not working?
Bazina commentedon Sep 10, 2024
I still have the same issue while using this
while the env have all the variables required

eliotc commentedon Oct 12, 2024
@colerogers , I can see your pull request for fixing this issue is not merged yet. Any update on this issue?
berkdilek commentedon Nov 23, 2024
The issue still exists. Can the workaround above cause any cold-start problems?
@colerogers, the PR seems to have been open for more than a year now. Do you have any updates on this issue?
12 remaining items
cabljac commentedon Aug 21, 2025
Hi all,
I'm picking this issue up for investigation. Can I confirm - the bug now only occurs in certain CI environments (github actions, cloud build, etc)?
Also can anyone provide a minimal workflow yaml or configuration in which it's failing, so i can reproduce?
cabljac commentedon Aug 21, 2025
Ah I can confirm i've reproduced! I will investigate a fix
cabljac commentedon Aug 21, 2025
I believe the bug could be here
https://github.com/firebase/firebase-tools/blob/76f9f378fad7ecaf6aa91675d1da8d58952d7591/src/deploy/functions/runtimes/python/index.ts#L153-L156
where we're not merging
process.envit could be a one-liner, I will test a patched version.