Can we access your project?
Current Behavior
Project: YgjNoPK4DttwuMUvyy5u
Branch: pb-access-entitlement-v1
Environment: Development
Candidate commit: ksRWb1URpzzKqCc64eYs
Project Issues reports 0 errors and 2 warnings after reload, and fresh server-side code generation/export succeeds. Clicking Run Mode briefly shows a spinner, then creates no Run-history entry; Run history remains "No previous builds. Hit the Run button to start a build." One new-Test-Mode attempt and one legacy-Test-Mode attempt each produced no test session, runtime URL, or actionable build diagnostic. No product or backend changes were made between these attempts.
Expected Behavior
Run Mode should start the documented cloud build and create a project-member runtime URL plus a Run-history entry. Test Mode should open a test session. If the build service cannot do either, the editor should return an actionable error tied to the failed build/session.
Steps to Reproduce
- Open https://app.flutterflow.io/project/YgjNoPK4DttwuMUvyy5u on branch pb-access-entitlement-v1.
- Select the Development environment and confirm the synced head ksRWb1URpzzKqCc64eYs.
- Reload Project Issues and observe 0 errors and 2 warnings.
- Open the Run/Test menu and click Run once.
- Wait for the brief spinner to stop.
- Reopen Run history: no build entry exists and the empty-state message remains.
- Enable new Test Mode and invoke Test once: no session or runtime surface appears.
- Disable new Test Mode and invoke legacy Test once: no session or runtime surface appears.
- Fresh server-side codegen/export for the same head succeeds, so the missing cloud runtime surface is the remaining boundary.
Reproducible from Blank
Bug Report Code (Required)
IT40pfGA+bBOx898+rjqKcdKqGEhJ1x9bI0W0+t7aCosfZT2BLMcec/RVERDQsTnTFZ6IFqamWoW0eCMifzPKfUDE06afb5OzahMZTrNVkC5aYimFJWgPnYnQOZNGlCbyraw2hNvBLd2WFoa2VOmfevIb3PvQb7sInowDa/LZO4=
Visual documentation
The behavior was reproduced directly in the current FlutterFlow web editor on the exact project/branch/environment above. The Bug Report Code binds the current project state. No console secrets or credentials are included.
Environment
- FlutterFlow version: Current hosted web editor as of 2026-09-07
- Platform: Web
- Browser name and version: Chromium-based Codex in-app browser, current managed version
- Operating system and version affected: Windows host (exact build not exposed to the browser session)
Additional Information
This blocks creation of the non-public Run/Test runtime needed for independent acceptance of an isolated private-beta candidate. The currently accepted deployed runtime remains untouched. Local compile/codegen evidence is available but is not being substituted for the missing cloud runtime. One fresh attempt was made for each supported mode; identical retries were intentionally avoided.
Can we access your project?
Current Behavior
Project: YgjNoPK4DttwuMUvyy5u
Branch: pb-access-entitlement-v1
Environment: Development
Candidate commit: ksRWb1URpzzKqCc64eYs
Project Issues reports 0 errors and 2 warnings after reload, and fresh server-side code generation/export succeeds. Clicking Run Mode briefly shows a spinner, then creates no Run-history entry; Run history remains "No previous builds. Hit the Run button to start a build." One new-Test-Mode attempt and one legacy-Test-Mode attempt each produced no test session, runtime URL, or actionable build diagnostic. No product or backend changes were made between these attempts.
Expected Behavior
Run Mode should start the documented cloud build and create a project-member runtime URL plus a Run-history entry. Test Mode should open a test session. If the build service cannot do either, the editor should return an actionable error tied to the failed build/session.
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT40pfGA+bBOx898+rjqKcdKqGEhJ1x9bI0W0+t7aCosfZT2BLMcec/RVERDQsTnTFZ6IFqamWoW0eCMifzPKfUDE06afb5OzahMZTrNVkC5aYimFJWgPnYnQOZNGlCbyraw2hNvBLd2WFoa2VOmfevIb3PvQb7sInowDa/LZO4=
Visual documentation
The behavior was reproduced directly in the current FlutterFlow web editor on the exact project/branch/environment above. The Bug Report Code binds the current project state. No console secrets or credentials are included.
Environment
Additional Information
This blocks creation of the non-public Run/Test runtime needed for independent acceptance of an isolated private-beta candidate. The currently accepted deployed runtime remains untouched. Local compile/codegen evidence is available but is not being substituted for the missing cloud runtime. One fresh attempt was made for each supported mode; identical retries were intentionally avoided.