Troubleshooting

I cannot edit anything

Every database starts read-only. Select the database in the sidebar and toggle Enable write access. It is per database — enabling it on one does not enable it on another. See Enabling write access.

My projects are not listed

FireFetch shows the projects the signed-in account can reach. Check that:

• You signed in with the right Google account — add another with Add account
• The account has the Firebase or Cloud Firestore permissions for that project
• For a service account, the key belongs to the project you expect

A query fails asking for an index

Firestore requires a composite index for some combinations of filters and ordering. FireFetch turns that error into a link that opens the Firebase Console page which creates exactly the index required. Create it, wait for it to finish building, then run the query again.

A write failed with a conflict

The document changed after you loaded it. FireFetch sends the document’s last-known update time as a precondition, so rather than overwriting someone else’s change it stops and tells you. Reload the document and reapply your edit.

An undo was refused

Undo is refused when replaying it would discard a change made after yours. FireFetch names the conflicting fields. Decide whether you still want the old value and, if so, set it explicitly. See Change history and undo.

The time travel control is unavailable

Point-in-time recovery must be enabled for that database in Google Cloud, and the timestamp must fall inside the retention window. FireFetch reads the window and will not offer timestamps outside it.

Pipelines are unavailable

The pipelines builder, including vector search, requires a Firestore Enterprise edition database. FireFetch says so rather than letting you build a pipeline that cannot run.

My assistant cannot see anything over MCP

FireFetch must be running — the MCP server reaches Firestore through the app, not directly. Also confirm you restarted the MCP client after editing its configuration. See MCP server setup.

A script will not stop

It will. Scripts run in a separate process, and Stop kills it. If the interface itself is unresponsive, that is a bug worth reporting.

Reporting a problem

Email [email protected] with your operating system, the FireFetch version from the About dialog, and what you were doing. Please do not include credentials, service-account keys or production documents.