The document summarizes a failed job to deploy Firebase Cloud Functions to production. The job failed after 22 minutes when trying to fetch Firestore indexes from the default Firebase project, as it reported an invalid project selection and no access. The complete log is available for debugging.
The document summarizes a failed job to deploy Firebase Cloud Functions to production. The job failed after 22 minutes when trying to fetch Firestore indexes from the default Firebase project, as it reported an invalid project selection and no access. The complete log is available for debugging.
The document summarizes a failed job to deploy Firebase Cloud Functions to production. The job failed after 22 minutes when trying to fetch Firestore indexes from the default Firebase project, as it reported an invalid project selection and no access. The complete log is available for debugging.
/home/runner/work/backend/backend 51 > husky install 52 53 husky - Git hooks installed 54 added 347 packages from 227 contributors and audited 347 packages in 6.203s 55 56 46 packages are looking for funding 57 run `npm fund` for details 58 59 found 0 vulnerabilities 60 61 62 > solarladder-backend@ fetch-firestore- indexes /home/runner/work/backend/backend 63 > firebase use default && firebase firestore:indexes > firestore.indexes.json 64 65 ⚠ Authenticating with `FIREBASE_TOKEN` is deprecated and will be removed in a future major version of `firebase- tools`. Instead, use a service account key with `GOOGLE_APPLICATION_CREDENTIALS`: https://cloud.google.com/docs/authentic ation/getting-started 66 67 Error: Invalid project selection, please verify project default exists and you have access. 68 npm ERR! code ELIFECYCLE 69 npm ERR! errno 1 70 npm ERR! solarladder-backend@ fetch- firestore-indexes: `firebase use default && firebase firestore:indexes > firestore.indexes.json` 71 npm ERR! Exit status 1 72 npm ERR! 73 npm ERR! Failed at the solarladder- backend@ fetch-firestore-indexes script. 74 npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 75 76 npm ERR! A complete log of this run can be found in: 77 npm ERR! /home/runner/.npm/_logs/2023-04- 07T09_38_20_643Z-debug.log 78 yes: standard output: Broken pipe 79 Error: Process completed with exit code 1.