Recent "Roll Dart SDK" commit broke release mode #170038
Description
Steps to reproduce
After upgrading to the latest flutter master version I noticed that my app worked still fine in debug mode but crashed instantly on startup in release mode. I spent some hours with git bisect and tracked it down that the bad commit which introduces the crashes is this one: #168679
The previous commit stills works fine in release mode and since the linked commit (all the way up to the very latest commit) lead to an instant crash for my app.
This is happening on iOS (real device). I am a bit surprised that this issue was not reported by someone else already?
Not sure if I am able to create a code sample because I have no idea which part of the code actually causes the issue - because I can't find any useful log.
Expected results
No crash in release mode.
Actual results
Instant crash in release mode since the linked commit.
Code sample
Code sample
Screenshots or Video
Screenshots / Video demonstration
ScreenRecording_06-05-2025.02-43-51_1.MP4
Logs
Logs
Flutter Doctor output
Doctor output
flutter doctor -v
[!] Flutter (Channel [user-branch], 3.33.0-1.0.pre.36, on macOS 15.4 24E248 darwin-arm64, locale de-DE) [189ms]
! Flutter version 3.33.0-1.0.pre.36 on channel [user-branch] at /Users/felixmittermeier/Documents/flutter
Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
! Upstream repository unknown source is not a standard remote.
Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
• Framework revision 2982c93b9d (3 weeks ago), 2025-05-12 16:04:52 -0400
• Engine revision 2982c93b9d
• Dart version 3.9.0 (build 3.9.0-114.0.dev)
• DevTools version 2.46.0
• If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.
[✓] Android toolchain - develop for Android devices (Android SDK version 36.0.0) [1.174ms]
• Android SDK at /Users/felixmittermeier/Library/Android/sdk
• Emulator version 35.4.9.0 (build_id 13025442) (CL:N/A)
• Platform android-36, build-tools 36.0.0
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
This is the JDK bundled with the latest Android Studio installation on this machine.
To manually set the JDK path, use: `flutter config --jdk-dir="path/to/jdk"`.
• Java version OpenJDK Runtime Environment (build 21.0.5+-13047016-b750.29)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 16.3) [600ms]
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 16E140
• CocoaPods version 1.16.2
[✓] Chrome - develop for the web [9ms]
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2024.3) [8ms]
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 21.0.5+-13047016-b750.29)
[✓] VS Code (version 1.100.3) [7ms]
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.112.0
[✓] Connected device (4 available) [5,6s]
• iPhone 14 Pro Max (mobile) • 00008120-00086C192E60C01E • ios • iOS 18.5 22F76
• iPhone von Annika (wireless) (mobile) • 00008130-0002255E1E09001C • ios • iOS 18.5 22F76
• macOS (desktop) • macos • darwin-arm64 • macOS 15.4 24E248 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 137.0.7151.56
[✓] Network resources [1.109ms]
• All expected network resources are available.Metadata
Metadata
Assignees
Labels
High-priority issues at the top of the work listChallenges faced when attempting to productionize an appStack traces logged to the consoleIt was better in the past than it is nowDart team may need to help usTriaged by Dart teamflutter/engine related. See also e: labels.iOS applications specificallyIssue is closed as already fixed in a newer versionOwned by Engine teamTriaged by Engine team