Skip to content

Run Mode versions created but Preview artifacts are missing / returning 404 #7524

Description

@kgp52ypvfc-collab

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

Hello FlutterFlow Support,

Project ID: new-project-xr5nop

Two recent Run Mode versions appear successfully in the FlutterFlow project history, but their Preview artifacts are unavailable:

  • j5evwVvzfmbDIbXFzg3Dy
  • CJpCBI9eMICGYuhfRU61

For both versions:

  • the FlutterFlow Run page remains indefinitely on the loading spinner;
  • the MFO application never opens;
  • the Run page calls getRunModeData, but no application Preview iframe is created;
  • direct access to the corresponding Preview artifact returns “Page Not Found” / HTTP 404;
  • no client-side error from the application, Supabase, the RPC, or the Custom Action is shown.

Control Run that still works correctly from the same account, browser, device, network, and project:

  • TcEK3E9zDcpVlDxtqn0R

The project is shown as Synced, and the recent Run builds appear as completed in Project Run Versions.

This suggests that the Run record is created successfully, but the web Preview artifact is not being provisioned, deployed, registered, or authorized during the post-build phase.

Expected Behavior

The two recent Run Mode versions should open the MFO application and their Preview artifacts should be available instead of returning “Page Not Found” / HTTP 404.

Steps to Reproduce

  1. Open Run Mode version j5evwVvzfmbDIbXFzg3Dy.
  2. Observe that the FlutterFlow Run page remains indefinitely on the loading spinner and the MFO application never opens.
  3. Open the corresponding Preview artifact directly and observe “Page Not Found” / HTTP 404.
  4. Repeat the same steps with Run Mode version CJpCBI9eMICGYuhfRU61.
  5. Compare with control Run TcEK3E9zDcpVlDxtqn0R, which still works correctly from the same account, browser, device, network, and project.

Reproducible from Blank

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

Bug Report Code (Required)

IT4sivHq6otPvsdG1ZDuc8dB/WQWG1w6a+Y8scsZa0kdB4joPLJ/fs7BVFhBQuG6T0NhHE20mmIB+d77iOL1VO45IQyqfJx4+s9iYTnMc3q8Rc2PPqWaS0BBM9xbI36c4aW7mQhCPsRaLFo/6kOmJ/K8YC7DCZ+/Zwh9f6PHaOI=

Visual documentation

No additional screenshots are attached. The issue is reproducible through the Run Mode loading screen and the missing Preview artifact (404).

Environment

FlutterFlow v7.0.81 — Web — Google Chrome on Windows.

Additional Information

Could you please inspect the internal build and deployment logs for the two failing Run IDs and compare them with the working control Run?

No additional Run has been created since this diagnostic.

Thank you.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: needs triageA potential issue that has not been confirmed as a bug.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions