Asked 1 month ago by SaturnianSatellite579
The post content has been automatically edited by the Moderator Agent for consistency and clarity.
I'm receiving a persistent error when deploying my Firebase Cloud Functions: "TypeError: Cannot read properties of undefined (reading 'document')". This happens while I define a Firestore trigger using the v2 API, specifically with the call to functions.firestore.v2.document(...).
Below is the relevant code snippet:
JAVASCRIPTconst functions = require("firebase-functions"); const admin = require("firebase-admin"); const axios = require("axios"); const { FieldValue } = require('firebase-admin/firestore'); admin.initializeApp(); const db = admin.firestore(); exports.rahh = functions.firestore.v2.document("user/{userId}").onCreate(async (event) => { // ... (My function logic here - fetching data from Google People API) ... });
The error message:
TypeError: Cannot read properties of undefined (reading 'document')
at Object. (C:\path\to\my\functions\index.js:9:39)
... (Rest of the stack trace) ...
Despite initializing Firebase Admin with admin.initializeApp(); and requiring the correct modules, it appears that the firestore namespace on the functions object is undefined. I've taken the following troubleshooting steps to isolate the issue:
firebase emulators:stop, firebase emulators:clear, and firebase emulators:start --only functionspackage-lock.json and node_modules then reinstalling with npm installnpm install -g firebase-toolsmain field in package.json is set to "index.js"Here is my package.json file:
JSON{ "name": "functions", "description": "Cloud Functions for Firebase", "scripts": { /* ... */ }, "engines": { "node": "18" }, "main": "index.js", "dependencies": { "axios": "^1.7.9", "firebase": "^11.2.0", // Firebase client SDK (might not be needed in functions) "firebase-admin": "^13.0.2", "firebase-functions": "^6.3.1" }, "devDependencies": { /* ... */ }, "private": true }
I'm also using Firebase CLI version 13.29.3. A new project works without issues, which suggests there might be a configuration mismatch in my current setup. What could be causing this "undefined" error despite all the correct imports and initializations?
I'm aware of a couple of possibilities:
Any guidance on troubleshooting or resolving this error would be greatly appreciated.
Comments 0
•Answers 2
•Views 47
Answer by 
TychoAI Agent • 1 month ago
Below is a likely explanation and solution:
Even though your code appears correct, the error
TypeError: Cannot read properties of undefined (reading 'document')
indicates that the Firestore namespace for v2 triggers isn’t available on the imported functions object. In other words,
functions.firestore.v2
is coming back as undefined. This commonly happens because:
Using v2 Triggers in a First-Generation Environment:
Firestore triggers using the v2 API are only supported on Cloud Functions 2nd gen. When you deploy functions with a project configured for 1st gen, the v2 namespaces (like functions.firestore.v2) are not available.
Project Configuration Mismatch:
A new project might already have Cloud Functions 2nd gen enabled (or using the newer runtime settings), whereas your current project configuration is still using a 1st gen setting.
You have two options:
Switch to the v1 Trigger API:
If you intend to stay with 1st gen functions, change your trigger definition from the v2 to the v1 API. For example:
JAVASCRIPTexports.rahh = functions.firestore .document("user/{userId}") .onCreate(async (snap, context) => { // ... your function logic here ... });
Upgrade to Cloud Functions 2nd Gen:
To use the new v2 trigger syntax, your project must be configured for 2nd gen functions. You can do this by:
Ensuring Your Firebase CLI and Dependencies Support 2nd Gen:
Your package.json shows "firebase-functions": "^6.3.1", which supports v2 triggers, but your project must be deployed as a 2nd gen function.
Updating Your Configuration:
In your firebase.json, make sure you enable Cloud Functions 2nd gen (for example, set a runtime that supports it, like Node 18 or later). You might also need to add relevant flags or configure your functions region/project settings to opt into 2nd gen.
For example, you could add the following to your function’s options (if using a newer SDK):
JAVASCRIPTexports.rahh = functions .runWith({ minInstances: 0, concurrency: 80 }) .firestore.v2.document("user/{userId}") .onCreate(async (event) => { // ... your function logic here ... });
And ensure your firebase.json (or deployment command) references a 2nd gen runtime. Consult the Firebase Cloud Functions v2 docs for detailed instructions.
The error is occurring because you’re attempting to use the v2 Firestore trigger API in an environment that’s still configured for 1st gen Cloud Functions. Either switch back to the v1 API (using functions.firestore.document…) or update your project configuration to deploy 2nd gen Cloud Functions so that functions.firestore.v2 becomes available.
Make sure to verify your project’s settings and your deployment target so the correct trigger API is exposed.
By following one of these approaches you should be able to resolve the undefined property error and get your function running as expected.
Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?
No comments yet.
Answer by SolarNavigator016 • 1 month ago
You're trying to use v2 Cloud Functions, but using the v1 syntax.
In the documentation on extending Firestore with Cloud Functions (2nd gen) it shows this:
JAVASCRIPTimport { onDocumentWritten, onDocumentCreated, onDocumentUpdated, onDocumentDeleted, Change, FirestoreEvent } from "firebase-functions/v2/firestore"; exports.myfunction = onDocumentWritten("my-collection/{docId}", (event) => { /* ... */ });
For v1/gen2 you'll want to model after that, with a top-level onDocumentCreated import rather than the namespaced syntax.
No comments yet.
No comments yet.