Web build: Uncaught TypeError "J.cp(...).ao is not a function" on page load breaks Firestore reads/writes

[vitalidieter85-arch]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

The published/run-mode web build throws JavaScript errors that break Firestore:

• "Uncaught TypeError: J.cp(...).ao is not a function" (main.dart.js:199) fires on page load of a page whose custom action reads Firestore (loadProjectsList, using .orderBy('updated_at', descending: true)).
• A second "Uncaught" (main.dart.js:6331) fires when a custom action writes to Firestore (createProject, writing to users/{uid}/projects/{autoId}).

Result: creating Firestore documents silently fails in the web build; the action chain aborts before completing.

Already verified / tried (none resolved it):

• All custom functions/actions reviewed: no dart:html/dart:io/dart:js, no manual DocumentReference construction, no collectionGroup in the failing path. Code is web-safe.
• Firestore security rules correctly allow users/{uid}/projects.
• User is authenticated (email/password) when the error occurs.
• Browser cache cleared, no service worker registered, hard reload done.
• Reconnected Firebase Project (new per-project access model): completed successfully, orange banner gone.
• Regenerated Config Files after reconnect.
• Firebase packages coherent: firebase_core 3.14.0, cloud_firestore 5.6.9, firebase_auth 5.6.0.

The error persists after all of the above. The minified symbol J.cp(...).ao cannot be mapped to a source line without sourcemaps, which are not available in the run/publish build.

Firebase project: vorarbeiter-app (Blaze plan). Browser: Chrome.

Expected Behavior

Firestore reads and writes work in the web build without JavaScript errors. Tapping "Anlegen" creates the project document and it appears in the list.

Steps to Reproduce

1. Open the ProjectsPage in the web build (run or publish) while logged in via email/password.
2. The "J.cp(...).ao is not a function" error fires on page load.
3. Tap the "+" button, enter a title, tap "Anlegen".
4. The second error fires; no document is created in Firestore.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT48zcmBw5dPm8dc1aXqdcBr/TgWOUs7U4Ik0Ox+Skk8KOPaPOw+Ps/BM0RtOcTmSnxcfGH8kWoW0sGNvdrxG+06aCitbbZ41apUQwLdWl6tVp/RFJWgT3x9INJXIEis1ruvgh54HLJvdV4s7U2QAty9VgjqHYP1IlYSDq/LZO4=

Visual documentation

See console screenshot: two red errors on the ProjectsPage in the web build —
"Uncaught TypeError: J.cp(...).ao is not a function" (main.dart.js:199) and "Uncaught" (main.dart.js:6331).

Environment

- FlutterFlow version:
- Platform: Web (run mode + publish)
- Browser: Chrome (latest)
- OS: Windows
- Firebase project: vorarbeiter-app (Blaze plan)
- firebase_core 3.14.0, cloud_firestore 5.6.9, firebase_auth 5.6.0

Additional Information

This is a blocking issue: it makes core Firestore functionality (creating documents) completely unusable in the web build. It started occurring around the time of the Firebase "per-project access model" migration. I have already reconnected Firebase and regenerated config files without effect. Quick guidance would be much appreciated.

[Juansarmi]

Hi there!

Sorry to hear you're running into this issue. I’ve tried to reproduce it on my end but haven’t had any luck so far.

If you’re able to recreate the issue in a new blank project, that would really help speed things up on our side.

Please also send me the bug report code from that new project so I can take a closer look.

Thanks in advance!