FlutterFlow Local Device Testing fails on iOS 26 - Debug mode blocked by memory protection

[t-o-m-h]

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

FlutterFlow Local Device Testing crashes immediately on iOS 26 physical devices during Dart VM initialization with error:

error: Unable to flip between RX and RW memory protection on pages
dart::Dart::DartInit(Dart_InitializeParams const*)+0x5a38

The app never launches - crashes before any user code executes.

Expected Behavior

Local Device Testing should successfully launch and run on iOS 26 devices, similar to how it works on iOS Simulator and how Release builds work via TestFlight.

Steps to Reproduce

1. Update iPhone to iOS 26.0.1
2. Open FlutterFlow 6.3.32 project
3. Click "Local Device Testing"
4. Select iOS 26 physical device
5. App builds successfully but crashes (stuck on blank screen and never progresses) on launch

Reproducible from Blank

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

Bug Report Code (Required)

IT4oiefq2It2m+FJ7qryccAwmSQWQm59bJ0Zl8pBazwbfe+uB4kqevfOTERtZNyoY39UO1mGhWoW3NbGveLhO/QoFzGdfKo9wcx6ZT3yJVytb83TFJWvdndfI+RVI2q505+3nxJCWLBpWFIC32eUG+yWaAzvNYDRDFUkDq/LZO4=

Visual documentation

Environment

- FlutterFlow: 6.3.32
- Flutter SDK: 3.32.4 (FlutterFlow bundled, custom branch)
- iOS: 26.0.1 (physical device)
- Xcode: 26.0.1
- macOS: 26.0
- Dart: 3.8.1

Additional Information

Root cause: iOS 26's stricter memory protection prevents Debug mode's JIT compilation from switching memory between RX/RW modes.

Workarounds that DO work:

• iOS Simulator (any version)
• TestFlight Release builds (AOT compilation)
• Manual flutter run --profile via terminal

Suggested fix: Add Profile or Release mode option to Local Device Testing UI, as these use AOT compilation which is compatible with iOS 26.

[Alezanello]

Hello!

This issue only occurs on physical devices — it doesn’t appear when running on a simulator. It seems to be resolved in Flutter 3.35.4, so it should be fixed once FlutterFlow upgrades to the latest Flutter version.

You can also track the related Flutter issue here: flutter/flutter#170416