Can we access your project?
Current Behavior
No action fires when a widget is tapped, EXCEPT "Navigate To" actions. This affects every widget I've tested, including a brand-new native Button on a brand-new blank page - so it is not related to a specific widget, Custom Component, or page. Navigation-type actions work perfectly; every other action type (tested: Show Snackbar, Create Document) does nothing at all - no visual feedback, no error, no network request, no console output.
Original issue this stems from: an "Add New" button on the StaffDirectory page (Create Document action, writing to the "invites" collection) does not fire when tapped in Run mode, despite a correct configuration. This appears to be one symptom of the broader bug described here.
Expected Behavior
The action fires as configured. Example: tapping the button shows the snackbar message "Works", and/or a new document is created in the "companies" Firestore collection with the specified field value.
Steps to Reproduce
- Create a new blank page (e.g. TapTest) with a single native Button widget.
- On the Button's On Tap trigger, add a "Show Snack Bar" action with message "Works".
- Add a second action on the same trigger: Backend/Database, Firestore, Create Document, targeting an existing collection (e.g. companies), with a simple field (name = TapTest Diagnostic).
- Run the app in a fresh Test Mode session (also reproduced in a full Run/production build).
- Tap the Button.
- Observe: no snackbar appears, no new document is created (verified directly in the Firestore Data Manager / CMS view, confirmed after a full page refresh), and no relevant console errors or network requests are logged. "Navigate To" actions on the same buttons/pages fire correctly in the same session.
Reproducible from Blank
Bug Report Code (Required)
IT4ohc/1z5J2n7xZ0Kr2a/lanSQ4G1N8UOYk18pOGDsdF4iuPOxzacnCblBCYO7jSmxhKEWLuHIx0tL8v9jDNfQ3BwuYY65+waliexbNVnq/aoS4DIeVP3BBM8VVCmKl38OOkSV7PtFqL2Ng7F6QN+SvUh3XJr34Zwh9f6PHaOI=
Visual documentation
(Automatic image upload isn't working from my end right now, so describing what the screenshots show instead - happy to attach the actual images in a follow-up comment if needed.)
Screenshot 1 - Action Flow Editor for the Button's On Tap trigger: shows "Action 1: Show Snack Bar" (Snack Bar Message value = "Works") and "Action 2: Backend Call > Create Document" (targeting the "companies" collection) both configured correctly on the same trigger.
Screenshot 2 - Firestore Data Manager / CMS view of the "companies" collection: after tapping the button multiple times in both Test Mode and a full Run build, and refreshing the CMS view, no new "TapTest Diagnostic" document appears - confirming Create Document silently did not execute.
Also confirmed via the browser's Network and Console panels: tapping the button produces no relevant network request and no console output at all - not even an error. Meanwhile, a separate "Navigate To" action on another button in the same project fires immediately and correctly every time.
Environment
- FlutterFlow version: Latest (as of Aug 2026, checked via app.flutterflow.io)
- Platform: Web (FlutterFlow Test Mode and Full Run/production build)
- Browser name and version: Google Chrome (latest)
- Operating system and version affected: N/A - reproduced in-browser (Web); not tied to a specific desktop/mobile OS
Additional Information
This is a core-functionality blocker: it prevents any non-navigation action (Create/Update/Delete Document, Show Snackbar, etc.) from working anywhere in the app, including the original "Add New" invite-creation flow on our Staff Directory page. Users cannot create records, show feedback, or perform most interactive actions at all - only page navigation works. This makes the app unusable for its core purpose until fixed.
Can we access your project?
Current Behavior
No action fires when a widget is tapped, EXCEPT "Navigate To" actions. This affects every widget I've tested, including a brand-new native Button on a brand-new blank page - so it is not related to a specific widget, Custom Component, or page. Navigation-type actions work perfectly; every other action type (tested: Show Snackbar, Create Document) does nothing at all - no visual feedback, no error, no network request, no console output.
Original issue this stems from: an "Add New" button on the StaffDirectory page (Create Document action, writing to the "invites" collection) does not fire when tapped in Run mode, despite a correct configuration. This appears to be one symptom of the broader bug described here.
Expected Behavior
The action fires as configured. Example: tapping the button shows the snackbar message "Works", and/or a new document is created in the "companies" Firestore collection with the specified field value.
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT4ohc/1z5J2n7xZ0Kr2a/lanSQ4G1N8UOYk18pOGDsdF4iuPOxzacnCblBCYO7jSmxhKEWLuHIx0tL8v9jDNfQ3BwuYY65+waliexbNVnq/aoS4DIeVP3BBM8VVCmKl38OOkSV7PtFqL2Ng7F6QN+SvUh3XJr34Zwh9f6PHaOI=
Visual documentation
(Automatic image upload isn't working from my end right now, so describing what the screenshots show instead - happy to attach the actual images in a follow-up comment if needed.)
Screenshot 1 - Action Flow Editor for the Button's On Tap trigger: shows "Action 1: Show Snack Bar" (Snack Bar Message value = "Works") and "Action 2: Backend Call > Create Document" (targeting the "companies" collection) both configured correctly on the same trigger.
Screenshot 2 - Firestore Data Manager / CMS view of the "companies" collection: after tapping the button multiple times in both Test Mode and a full Run build, and refreshing the CMS view, no new "TapTest Diagnostic" document appears - confirming Create Document silently did not execute.
Also confirmed via the browser's Network and Console panels: tapping the button produces no relevant network request and no console output at all - not even an error. Meanwhile, a separate "Navigate To" action on another button in the same project fires immediately and correctly every time.
Environment
Additional Information
This is a core-functionality blocker: it prevents any non-navigation action (Create/Update/Delete Document, Show Snackbar, etc.) from working anywhere in the app, including the original "Add New" invite-creation flow on our Staff Directory page. Users cannot create records, show feedback, or perform most interactive actions at all - only page navigation works. This makes the app unusable for its core purpose until fixed.