The document reference is not valid. It must have an equal number of segments, but the reference cities/SF/landmarks has 3 segments

Question

The document reference is not valid. It must have an equal number of segments, but the reference cities/SF/landmarks has 3 segments

Hello! I am currently learning from the firestore tutorial

Initially, they guide me to populate the database with the following data:

    import { collection, doc, setDoc } from "firebase/firestore"; 

    const citiesRef = collection(db, "cities");

    await setDoc(doc(citiesRef, "SF"), {
        name: "San Francisco", state: "CA", country: "USA",
        capital: false, population: 860000,
        regions: ["west_coast", "norcal"] });
    // other city data...

Later in the tutorial, there is a step to create sub-collections using the code provided below:

    import { collection, doc, setDoc } from "firebase/firestore";  

    const citiesRef = collection(db, 'cities');

    await Promise.all([
        setDoc(doc(citiesRef, 'SF', 'landmarks'), {
            name: 'Golden Gate Bridge',
            type: 'bridge'
        }),
        // other landmark data...
    ]);

However, the above code snippet leads to an error message stating:

errors.ts:94 Uncaught FirebaseError: Invalid document reference. Document references must have an even number of segments, but cities/SF/landmarks has 3.

If anyone knows why this error is occurring, please let me know!

typescript firebase google-cloud-firestore

Answer 1

Answer №1

It seems there was an error in the code sample provided. As citiesRef is a collection reference,

doc(citiesRef, 'SF', 'landmarks')

is also a collection reference, and you cannot use setDoc on a collection reference.

To resolve this issue, you should use addDoc instead of setDoc, and replace doc with collection. Making these changes will improve the functionality:

addDoc(collection(citiesRef, 'SF', 'landmarks'), {
    name: 'Golden Gate Bridge',
    type: 'bridge'
}),

Last updated on June 16, 2022: The documentation has been corrected to use addDoc() instead of setDoc(), and collection() instead of doc().

Answer 2

It seems there was an error in the code sample provided. As citiesRef is a collection reference,

doc(citiesRef, 'SF', 'landmarks')

is also a collection reference, and you cannot use setDoc on a collection reference.

To resolve this issue, you should use addDoc instead of setDoc, and replace doc with collection. Making these changes will improve the functionality:

addDoc(collection(citiesRef, 'SF', 'landmarks'), {
    name: 'Golden Gate Bridge',
    type: 'bridge'
}),

Last updated on June 16, 2022: The documentation has been corrected to use addDoc() instead of setDoc(), and collection() instead of doc().

Answer 3

Answer №2

After facing the same issue and undergoing numerous trials, I finally found a solution that I felt compelled to share: The problem stems from incorrect document references when working with Firebase. It is crucial to follow the pattern of collection/document/collection/document for proper functioning. In my case, mistakenly referencing collection/document/document led to this error.

Here is an example of the wrong way:

setDoc(doc(db, "collectionName", userID, documentID), ...

Corrected approach (adding another collection in between):

setDoc(doc(db, "collectionName", userID, "anotherCollectionName", documentID), ...

Answer 4

After facing the same issue and undergoing numerous trials, I finally found a solution that I felt compelled to share: The problem stems from incorrect document references when working with Firebase. It is crucial to follow the pattern of collection/document/collection/document for proper functioning. In my case, mistakenly referencing collection/document/document led to this error.

Here is an example of the wrong way:

setDoc(doc(db, "collectionName", userID, documentID), ...

Corrected approach (adding another collection in between):

setDoc(doc(db, "collectionName", userID, "anotherCollectionName", documentID), ...

Answer 5

Answer №3

[addDoc]([collection](citiesRef, 'DC', 'landmarks'), {
    name: 'National Air and Space Museum',
    type: 'museum'
}),

Modify your addDoc method to replace setDoc and use collection instead of doc when referencing a collection.

Answer 6

[addDoc]([collection](citiesRef, 'DC', 'landmarks'), {
    name: 'National Air and Space Museum',
    type: 'museum'
}),

Modify your addDoc method to replace setDoc and use collection instead of doc when referencing a collection.

Answer 7

Answer №4

I encountered a similar issue, however, I preferred using the setDoc over addDoc.

The error message indicated an invalid document reference due to an odd number of segments in the collection path.

The root cause of my problem was calling doc(db, 'collection', id) with an empty string as the id.

To address this, I implemented a check to ensure that the collectionId is neither undefined nor an empty string.

Below is the modified code snippet:

export const addPlayedGame = async (collectionId: string) => {
  try {
    if (!collectionId) return false;

    const collectionRef = doc(firebase.db, 'collection', collectionId);

    const updateObject = {
     ...
    };

    await setDoc(collectionRef, updateObject, { merge: true });

    return true;
  } catch (error) {
    return false;
  }
};

Answer 8

I encountered a similar issue, however, I preferred using the setDoc over addDoc.

The error message indicated an invalid document reference due to an odd number of segments in the collection path.

The root cause of my problem was calling doc(db, 'collection', id) with an empty string as the id.

To address this, I implemented a check to ensure that the collectionId is neither undefined nor an empty string.

Below is the modified code snippet:

export const addPlayedGame = async (collectionId: string) => {
  try {
    if (!collectionId) return false;

    const collectionRef = doc(firebase.db, 'collection', collectionId);

    const updateObject = {
     ...
    };

    await setDoc(collectionRef, updateObject, { merge: true });

    return true;
  } catch (error) {
    return false;
  }
};

Answer 9

Answer №5

The conversation has been ongoing for quite some time, but I understand the issue at hand and no one has provided the correct solution yet, so here is my input. The problem lies with the "doc()" function which requires two arguments: the first argument being the collection reference (for example: collection(db, "i am a collection")), and the second argument being the id of the document you wish to retrieve.

For instance:

let firestore = getFirestore();

let colref = collection(firestore, "i am a collection");

let document = doc(colref, "id of the document");

Therefore, in your case, the "doc()" function already receives the collection name from your "citiesRef" variable. You should only include 2 arguments unless you intend to pass the "citiesRef" arguments into the "doc()" function's arguments.

Answer 10

The conversation has been ongoing for quite some time, but I understand the issue at hand and no one has provided the correct solution yet, so here is my input. The problem lies with the "doc()" function which requires two arguments: the first argument being the collection reference (for example: collection(db, "i am a collection")), and the second argument being the id of the document you wish to retrieve.

For instance:

let firestore = getFirestore();

let colref = collection(firestore, "i am a collection");

let document = doc(colref, "id of the document");

Therefore, in your case, the "doc()" function already receives the collection name from your "citiesRef" variable. You should only include 2 arguments unless you intend to pass the "citiesRef" arguments into the "doc()" function's arguments.

The document reference is not valid. It must have an equal number of segments, but the reference cities/SF/landmarks has 3 segments

Answer №1

Answer №2

Answer №3

Answer №4

Answer №5

Similar questions

Leveraging async/await in express

Leveraging the power of the map function to manipulate data retrieved

Tips for preventing a wrapped union type from collapsing

JavaScript: Organizing values based on their case sensitivity

Type error encountered in TypeScript when using React Hotkeys keymap

Converting Angular object into an array

What is the proper way to declare and utilize a constant list within a component template in NuxtJs?

Angular4 Blueprint

What is the reasoning behind TypeScript's acceptance of value as a data type?

Issue with Angular 8: discrepancy between the value utilized in component.html and the value stored in component.ts (Azure application service)

Guide to implementing validation on submit in Angular 7 reactive forms

Issue encountered when trying to access colors within MUI theme in Typescript

It has come to our attention that one or more of your Android applications share a SHA-1 fingerprint and package name combination that is already being utilized

Managing dynamic paths using Next.JS on Firebase (server-side)

When importing a React Component with styling into the pages folder, it fails to function properly

Why does `react/require-default-props` still display an error even when a default prop value has been set?

Tips for creating the overload of a function that accepts a class as a parameter

Retrieve information before rendering a component in Reactjs

A volume slide will decrease to zero if the 'mute' button is selected

Mastering the art of using Styled() with MUI V5