Repository navigation
Closed
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: crashStack traces logged to the consoleStack traces logged to the consolec: fatal crashCrashes that terminate the processCrashes that terminate the processdependency: dartDart team may need to help usDart team may need to help usfyi-toolFor the attention of Flutter Tool teamFor the attention of Flutter Tool teamplatform-iosiOS applications specificallyiOS applications specificallyteam-iosOwned by iOS platform teamOwned by iOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-iosTriaged by iOS platform teamTriaged by iOS platform teamworkaround availableThere is a workaround available to overcome the issueThere is a workaround available to overcome the issue
Description
Steps to reproduce
- Have macOS 26.4
- Create a default flutter project (using Android Studio)
- Run flutter run for an iOS device (26.4)
Actual results
When I do a flutter run, the DartWorker crashes and I'm unable to execute my flutter app on iOS.
Logs
Logs
Running pod install...
Running Xcode build...
Xcode build done. 32,2s
Installing and launching...
Process 1125 stopped
* thread #21, name = 'DartWorker', stop reason = EXC_BAD_ACCESS (code=50, address=0x11fc000c4)
frame #0: 0x000000011fc000c4
-> 0x11fc000c4: ldur x6, [x24, #0x37]
0x11fc000c8: ldursw x7, [x6, #0x6f]
0x11fc000cc: add x7, x7, #0x1
0x11fc000d0: stur w7, [x6, #0x6f]
Target 0: (Runner) stopped.
Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.41.6, on macOS 26.4 25E246 darwin-arm64, locale pt-PT)
[✓] Android toolchain - develop for Android devices (Android SDK version 36.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 26.4)
[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Connected device (2 available)
[✓] Network resources
Reacted by Renato Marinho, Matt Hooper, Madhu, Ricardo Brunetto, Eddy, José Rodrigues, anonimowy-anonim-1234, Gian Patrick Quintana, Marco Bavagnoli, Lukáš Šimon and 50 more
Pinned by vashworth
Pinned comment options
Workarounds:
- Use a simulator
- Launch from Xcode
- Or use Xcode 26.3
- Or use a wireless device
Okay I was able to reproduce using https://github.com/flutter/flutter/tree/master/dev/integration_tests/flutter_gallery
- Verified that it's specific to Xcode 26.4. macOS 26.4 is also a requirement since Xcode 26.4 requires it.
- Recreates on master
- Recreates from Flutter CLI as well as IDE
- Works fine when launched from Xcode
Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: crashStack traces logged to the consoleStack traces logged to the consolec: fatal crashCrashes that terminate the processCrashes that terminate the processdependency: dartDart team may need to help usDart team may need to help usfyi-toolFor the attention of Flutter Tool teamFor the attention of Flutter Tool teamplatform-iosiOS applications specificallyiOS applications specificallyteam-iosOwned by iOS platform teamOwned by iOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-iosTriaged by iOS platform teamTriaged by iOS platform teamworkaround availableThere is a workaround available to overcome the issueThere is a workaround available to overcome the issue
Activity
gmr-renato commentedon Mar 27, 2026
Same scenario here for Flutter 3.41.6 on iOS 26.4 device
joserodpt commentedon Mar 27, 2026
Forgot to put it in the original body, but yea I'm also running iOS 26.4, Flutter 3.41.6 and macOS 26.4.
mjphooper commentedon Mar 28, 2026
Same here but for Flutter 3.38.0 on iOS 26.3.1 device. Running directly via Xcode seems to work fine.
kmadhu0 commentedon Mar 28, 2026
Reproduced this issue with Flutter 3.41.4 on iOS 26.3.1 (iPhone 16), Xcode 26.4.
Happens when running in Debug mode but works fine on Profile mode.
Works fine when running directly via Xcode.
alnitak commentedon Mar 28, 2026
This happens to me also since I updated to 26.4. It seems something related to code signing verification when running in debug mode (not in release/profile) on iPhone via USB cable.
Here is just a recap:
jk259 commentedon Mar 28, 2026
Same Problem after upgrading to Xcode 26.4, macOS 26.4, Flutter 3.41.6, Android Studio Panda 2 | 2025.3.2
Same crash on:
iPhone 13Pro iOS 26.3
iPad M3 iOS 26.4
running from Xcode direct works fine
reinstalled Xcode 26.3 and 26.3 Command Line Tools and everything works correctly.
anonimowy-anonim-1234 commentedon Mar 28, 2026
GLAD I'VE FOUND THIS ISSUE!
Same here
Environment details:
Flutter 3.41.x (tested on all minor 3.41 versions)
Xcode 26.4
MacOS 26.2 on M5 Pro MacBook
iPhone 16e with iOS 26.3.1, and iPhone 15 with iOS 26.4
Newest VSCode, with newest Dart/Flutter plugins
Flutter doctor without any issues
On both physical devices listed above I'm able to launch the application only for few times using flutter run with/without flavor, via VSC.
After that, the application is showing only splash screen, and not any breakpoint in main.dart is being hit. Debug console shows:
Sometimes it helps to reconnect the device, sometimes to start app from Xcode, and sometimes it helps to delete the app from iPhone before running it via flutter run.
Out of 100 runs, 80-90 fails when started from VSCode.
Out of 100 runs, almost all runs fine when started directly from Xcode
All runs on Android devices, or iOS Simulator are running fine.
The exact same setup (expect older M processor in MacBook and different iPhone model, but with same iOS) is working fine without any problems for one of my colleagues.
Today I've completely erased both iPhones and MacBook - First few runs were successful, rest was failing with the error pasted above.
jbannet commentedon Mar 29, 2026
Same issue. Almost exactly as described.
flutter 3.41.6 (though happened on an earlier version too)
Mac Mini Tahoe 26.2
Process 12972 stopped
frame #0: 0x0000000126c800c4
-> 0x126c800c4: ldur x6, [x24, #0x37]
0x126c800c8: ldursw x7, [x6, #0x6f]
0x126c800cc: add x7, x7, #0x1
0x126c800d0: stur w7, [x6, #0x6f]
Target 0: (X) stopped.
fazliddin-swe commentedon Mar 30, 2026
same scenario here
Crash log:
Flutter Doctor output
[✓] Flutter (Channel stable, 3.41.6, on macOS 26.4 25E246 darwin-arm64, locale en-UZ) [472ms] • Flutter version 3.41.6 on channel stable at /Users/fazliddin/fvm/versions/3.41.6 • Upstream repository https://github.com/flutter/flutter.git • Framework revision db50e20 (35 hours ago), 2026-03-25 16:21:00 -0700 • Engine revision 425cfb5 • Dart version 3.11.4 • DevTools version 2.54.2 • Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android, enable-ios, cli-animations, enable-native-assets, omit-legacy-version-file, enable-lldb-debugging, enable-uiscene-migration[✓] Android toolchain - develop for Android devices (Android SDK version 36.1.0-rc1) [1,477ms]
• Android SDK at /Users/fazliddin/Library/Android/sdk
• Emulator version 36.1.9.0 (build_id 13823996) (CL:N/A)
• Platform android-36, build-tools 36.1.0-rc1
• ANDROID_HOME = /Users/fazliddin/Library/Android/sdk
• 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.8+-14196175-b1038.72)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 26.4) [1,051ms]
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 17E192
• CocoaPods version 1.16.2
[✓] Chrome - develop for the web [6ms]
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Connected device (4 available) [6.2s]
• Fazliddin’s iPhone (mobile) • 00008140-001024E81E01801C • ios • iOS 26.4 23E246
• iPhone 17 Pro (mobile) • 807C8E54-7C58-4465-B7AB-E852B86EA397 • ios • com.apple.CoreSimulator.SimRuntime.iOS-26-2
(simulator)
• macOS (desktop) • macos • darwin-arm64 • macOS 26.4 25E246 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 146.0.7680.154
[✓] Network resources [534ms]
• All expected network resources are available.
• No issues found!
iOS version: 26.4
MacOS version: 26.4
XCode version: Version 26.4 (17E192)
68 remaining items
mraleph commentedon Apr 13, 2026
@vashworth I got confirmation from LLDB folks (here) that your original workaround with
continuewill also work just fine. So we probably don't need to waste time re-landing #184768 unless there are some strong reasons for that.Manually stop and continue LLDB breakpoints on Xcode 26.4+ (flutter#1…
Disable async mode with LLDB (flutter#184768)
Reverts "Disable async mode with LLDB (flutter#184768)" (flutter#184868)
Disable async mode with LLDB (flutter#184768)
[CP-beta]Disable async mode with LLDB (#185102)
[CP-stable] Disable async mode with LLDB (#184983)
DanisBikmaev commentedon Apr 17, 2026
I've also experienced exactly the same issue. Xcode 26.4, physical device on iOS 26.4, running via
flutter runcrashes withEXC_BAD_ACCESSon the DartWorker thread. Running directly through Xcode works fine.To help with debugging, I suggest that those who can reproduce the error try the following:
Run the app directly from Xcode (selecting your physical device). Verify that it builds and launches without the
EXC_BAD_ACCESScrash.After a successful launch from Xcode, without deleting the app from the device, immediately try running it again via
flutter run(or through your IDE).I'm curious (and I think the Flutter devs would be too) whether this changes the behavior. There have been reports in this thread that after launching from Xcode, the issue sometimes temporarily disappears. If that's the case, it might point to differences in build settings, code signing, or how Xcode and flutter run interact differently with the debugger on devices running iOS 26.4.
fazliddin-swe commentedon Apr 17, 2026
Update your Flutter version to 3.41.7 and Dart version to 3.11.5 the issue is resolved
mraleph commentedon Apr 17, 2026
@DanisBikmaev this issue is fixed on master and the fix is cherry-picked into beta.
You can read my comments above if you want to know what the issue was, tldr it's a bug in LLDB.
jmagman commentedon Apr 17, 2026
The fix is now available in stable 3.41.7.
github-actions commentedon May 1, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.Manually stop and continue LLDB breakpoints on Xcode 26.4+ (#184690)