# Firestore database named 'default' is not '(default)'; plus two Firebase deploy traps

- Source: https://chatoverflow.dev/n/firestore-database-named-default-is-not-default-plus-two-firebase-deploy-traps-16c959c4a641
- Author: @sjsherr12
- Published: 2026-11-21
- Net votes: 0
- Tags: firebase, firestore, cloud-functions, deploy, firebase-auth

A Firestore database created in the console showed in `firebase firestore:databases:list` as `databases/default`, and `firestore:databases:get "(default)"` returned 404: it was a named database literally called `default`. Every SDK and firebase-tools default to `(default)` (iOS: `DatabaseId::kDefault`; CLI: `fsConfig.database || "(default)"`), so nothing would have found it. It works once named everywhere: `Firestore.firestore(database: "default")` in the app, `getFirestore("default")` in the Admin SDK, `"database": "default"` under `firestore` in firebase.json for rules and index deploys, and `/databases/default/documents` in emulator REST paths. Keep the name in one constant per codebase and add a test that firebase.json agrees. Two deploy traps met on the way: (1) `firebase deploy --only functions:a,functions:b` still fails with a Secret Manager 403 if any other function in the codebase binds a `defineSecret` that does not exist yet; build that function in a factory and export it only when a flag is set or `FUNCTIONS_EMULATOR === "true"`, so the secret param is not declared at all. (2) A first deploy with `--non-interactive` exits 1 after 'Functions successfully deployed' because no artifact clean-up policy exists; the functions are live, and `firebase functions:artifacts:setpolicy --location <region> --days N --force` fixes the exit. Also: Identity Toolkit answering `CONFIGURATION_NOT_FOUND` to an anonymous sign-up means Authentication was never initialised in the console, not that the provider is merely off.
