Can we access your project?
Current Behavior
With Experimental Speed Up (BETA) enabled, switching between Production and Staging in Local Run updates environment values, including the backend API URL, but leaves GoogleService-Info.plist configured for the previous Firebase environment.
The mismatch was confirmed in both the local source file and the compiled iOS simulator app. It was observed in both directions: Staging → Production and Production → Staging.
As a result, the app connects to the selected environment’s backend while Firebase Authentication still uses the previous environment’s project. Custom-token sign-in fails with:
“The custom token corresponds to a different audience.”
This was observed with Experimental Speed Up enabled. Disabling Experimental Speed Up resolves the issue: switching environments correctly updates the iOS Firebase configuration, and custom-token authentication succeeds.
Expected Behavior
Switching environments should update the native Firebase configuration together with the environment values. Both the local GoogleService-Info.plist and the copy bundled into the iOS app should match the selected environment.
Experimental Speed Up should detect this configuration change and refresh the affected files before building.
Steps to Reproduce
-
Use a project with Production and Staging environments, each configured with a separate Firebase project and backend API URL.
-
Enable Experimental Speed Up (BETA).
-
Select Production and launch the app on an iOS simulator through Local Run.
-
Switch the selected environment to Staging and run the app again.
-
Inspect assets/environment_values/environment.json: the API URL reflects Staging.
-
Inspect ios/Runner/GoogleService-Info.plist: PROJECT_ID and BUNDLE_ID still reflect Production.
-
Inspect the corresponding files in the compiled simulator app: the same mismatch is present.
-
Attempt Firebase sign-in. Authentication fails with the error above.
-
Disable Experimental Speed Up and repeat the environment switch and Local Run. The Firebase configuration now matches the selected environment, and authentication succeeds.
The reverse mismatch was also observed when switching from Staging to Production.
Reproducible from Blank
Bug Report Code (Required)
IT40k+fqxItNpbxE+KqIbcdr/Sc5KUQ7aOcw0up7aDUsIuOtBu0qZ+LOdlppXuGqaVNcG060gTs10PTruISSU8ABE0mAfI84ypFQSxfke2itV82wCs+sOHF8GZhmIUCw4J2FvxFDIst0SlFm3E6uBPC9TgPDFOu/Zwh9f6PHaOI=
Visual documentation
Environment
- FlutterFlow version: 7.0.78
- Platform: FlutterFlow macOS desktop app, Local Run
- Operating system and version affected: macOS 26.6.2 (25G83)
Additional Information
No response
Can we access your project?
Current Behavior
With Experimental Speed Up (BETA) enabled, switching between Production and Staging in Local Run updates environment values, including the backend API URL, but leaves GoogleService-Info.plist configured for the previous Firebase environment.
The mismatch was confirmed in both the local source file and the compiled iOS simulator app. It was observed in both directions: Staging → Production and Production → Staging.
As a result, the app connects to the selected environment’s backend while Firebase Authentication still uses the previous environment’s project. Custom-token sign-in fails with:
“The custom token corresponds to a different audience.”
This was observed with Experimental Speed Up enabled. Disabling Experimental Speed Up resolves the issue: switching environments correctly updates the iOS Firebase configuration, and custom-token authentication succeeds.
Expected Behavior
Switching environments should update the native Firebase configuration together with the environment values. Both the local GoogleService-Info.plist and the copy bundled into the iOS app should match the selected environment.
Experimental Speed Up should detect this configuration change and refresh the affected files before building.
Steps to Reproduce
Use a project with Production and Staging environments, each configured with a separate Firebase project and backend API URL.
Enable Experimental Speed Up (BETA).
Select Production and launch the app on an iOS simulator through Local Run.
Switch the selected environment to Staging and run the app again.
Inspect assets/environment_values/environment.json: the API URL reflects Staging.
Inspect ios/Runner/GoogleService-Info.plist: PROJECT_ID and BUNDLE_ID still reflect Production.
Inspect the corresponding files in the compiled simulator app: the same mismatch is present.
Attempt Firebase sign-in. Authentication fails with the error above.
Disable Experimental Speed Up and repeat the environment switch and Local Run. The Firebase configuration now matches the selected environment, and authentication succeeds.
The reverse mismatch was also observed when switching from Staging to Production.
Reproducible from Blank
Bug Report Code (Required)
IT40k+fqxItNpbxE+KqIbcdr/Sc5KUQ7aOcw0up7aDUsIuOtBu0qZ+LOdlppXuGqaVNcG060gTs10PTruISSU8ABE0mAfI84ypFQSxfke2itV82wCs+sOHF8GZhmIUCw4J2FvxFDIst0SlFm3E6uBPC9TgPDFOu/Zwh9f6PHaOI=
Visual documentation
Environment
Additional Information
No response