Can we access your project?
Current Behavior
The published web app at https://blank-4czop1.flutterflow.app shows a blank/white screen on every device (mobile + desktop). Console shows an uncaught JS exception during app startup:
Uncaught Error
at Object.k (main.dart.js:3957:20)
at main.dart.js:76925:15
at aTE.a (main.dart.js:5317:63)
at aTE.$2 (main.dart.js:43913:14)
at aSy.$1 (main.dart.js:43907:21)
at aOU.aCw (main.dart.js:45063:34)
at aOU.uV (main.dart.js:45066:13)
at aHM.$0 (main.dart.js:44401:11)
at Object.w8 (main.dart.js:5458:40)
at ak.pM (main.dart.js:44321:3)
No source map is available for the published build (main.dart.js.map 404s).
We isolated this to the Publish build pipeline itself, not our app code: we identified the exact Flutter engine revision the published build uses (78fc3012e45889657f72359b005af7beac47ba3d, from _flutter.buildConfig.engineRevision in the deployed index.html), traced it to Flutter 3.38.6, checked out that exact version locally, and rebuilt the unmodified exported project source (flutter build web --release). It compiled and ran with zero errors, even after also matching the exact cross-origin assetBase config (storage.googleapis.com/flutterflow-prod-hosting/builds/S9YFVIfiRvgTGWUzKfz0/) the real deployment uses, loading the same production environment.json/fonts/canvaskit. Same source, same exact engine revision, same asset bucket — and it works. The only difference is that main.dart.js was compiled by us locally vs. by FlutterFlow's build infrastructure.
Also ruled out: a OneSignal integration we added and fully removed (deployed bundle confirmed to contain zero OneSignal references, crash identical before/after); Test Mode (loads the same app version perfectly); stale caching (verified fresh via curl); manifest.json's 404 (also present, but browsers tolerate this fine); our Supabase config (hardcoded literals); the empty Production environment.json (our local repro loaded this same empty file with no issue); sign_in_with_apple_web's auto-registered web plugin (its "Injecting <script> tag" log line appears harmlessly in our working local repro too).
Expected Behavior
The published web app should load and render normally, the same way it does in Test Mode (which works perfectly for this exact same app version).
Steps to Reproduce
Publish the Sehavia project (blank-4czop1) as a web app.
Open the resulting published URL (https://blank-4czop1.flutterflow.app) in any browser, on desktop or mobile.
Observe a blank/white screen and the console error described above.
For comparison, launching the same project via Test Mode in the FlutterFlow editor works with no errors.
Reproducible from Blank
Bug Report Code (Required)
ITEelsn1z4pNj70A7c7Ib8BGiQMwJ0QlUIInj+0bWRMhfIj1PZl2dfTBblpLYteXT3xmIFGimngd+tr1vYbiFe1fAzusbKpdzr5XQQqVYHilVqXQCc+ROUdAO/xhCW6Z356Znx55Is5hWkIlwzqqN/CdG3qCf9qOYwx5e6fDbOY=
Visual documentation
Environment
- FlutterFlow version: current (Production environment, project blank-4czop1)
- Platform: Web (Publish/hosted deployment — NOT reproducible in Test Mode)
- Browser name and version: reproduced on Chrome (both desktop and mobile)
- Operating system and version affected: reproduced on both Windows desktop and mobile (Android/iOS browsers per the reporting user)
- Flutter engine revision (from the deployed build's _flutter.buildConfig): 78fc3012e45889657f72359b005af7beac47ba3d (Flutter 3.38.6)
Additional Information
This is blocking all real-device testing for our app (e.g. we cannot test browser push notifications, which require a real hosted URL rather than Test Mode). Full investigation writeup with all ruled-out causes is in the "Current Behavior" section above. Happy to share the generated_code/ export or exact local build commands if that helps. Note: the "Bug Report Code" and screenshots/video above still need to be added by the project owner before submitting, since generating that code requires an action inside the FlutterFlow editor's Widget Tree.
Can we access your project?
Current Behavior
The published web app at https://blank-4czop1.flutterflow.app shows a blank/white screen on every device (mobile + desktop). Console shows an uncaught JS exception during app startup:
Uncaught Error
at Object.k (main.dart.js:3957:20)
at main.dart.js:76925:15
at aTE.a (main.dart.js:5317:63)
at aTE.$2 (main.dart.js:43913:14)
at aSy.$1 (main.dart.js:43907:21)
at aOU.aCw (main.dart.js:45063:34)
at aOU.uV (main.dart.js:45066:13)
at aHM.$0 (main.dart.js:44401:11)
at Object.w8 (main.dart.js:5458:40)
at ak.pM (main.dart.js:44321:3)
No source map is available for the published build (main.dart.js.map 404s).
We isolated this to the Publish build pipeline itself, not our app code: we identified the exact Flutter engine revision the published build uses (78fc3012e45889657f72359b005af7beac47ba3d, from _flutter.buildConfig.engineRevision in the deployed index.html), traced it to Flutter 3.38.6, checked out that exact version locally, and rebuilt the unmodified exported project source (flutter build web --release). It compiled and ran with zero errors, even after also matching the exact cross-origin assetBase config (storage.googleapis.com/flutterflow-prod-hosting/builds/S9YFVIfiRvgTGWUzKfz0/) the real deployment uses, loading the same production environment.json/fonts/canvaskit. Same source, same exact engine revision, same asset bucket — and it works. The only difference is that main.dart.js was compiled by us locally vs. by FlutterFlow's build infrastructure.
Also ruled out: a OneSignal integration we added and fully removed (deployed bundle confirmed to contain zero OneSignal references, crash identical before/after); Test Mode (loads the same app version perfectly); stale caching (verified fresh via curl); manifest.json's 404 (also present, but browsers tolerate this fine); our Supabase config (hardcoded literals); the empty Production environment.json (our local repro loaded this same empty file with no issue); sign_in_with_apple_web's auto-registered web plugin (its "Injecting <script> tag" log line appears harmlessly in our working local repro too).
Expected Behavior
The published web app should load and render normally, the same way it does in Test Mode (which works perfectly for this exact same app version).
Steps to Reproduce
Publish the Sehavia project (blank-4czop1) as a web app.
Open the resulting published URL (https://blank-4czop1.flutterflow.app) in any browser, on desktop or mobile.
Observe a blank/white screen and the console error described above.
For comparison, launching the same project via Test Mode in the FlutterFlow editor works with no errors.
Reproducible from Blank
Bug Report Code (Required)
ITEelsn1z4pNj70A7c7Ib8BGiQMwJ0QlUIInj+0bWRMhfIj1PZl2dfTBblpLYteXT3xmIFGimngd+tr1vYbiFe1fAzusbKpdzr5XQQqVYHilVqXQCc+ROUdAO/xhCW6Z356Znx55Is5hWkIlwzqqN/CdG3qCf9qOYwx5e6fDbOY=
Visual documentation
Environment
Additional Information
This is blocking all real-device testing for our app (e.g. we cannot test browser push notifications, which require a real hosted URL rather than Test Mode). Full investigation writeup with all ruled-out causes is in the "Current Behavior" section above. Happy to share the generated_code/ export or exact local build commands if that helps. Note: the "Bug Report Code" and screenshots/video above still need to be added by the project owner before submitting, since generating that code requires an action inside the FlutterFlow editor's Widget Tree.