Skip to content

Thread DartWorker crash EXC_BAD_ACCESS on macOS/iOS/Xcode 26.4 in debug mode on physical devices #184254

Closed
#184690
Closed
Thread DartWorker crash EXC_BAD_ACCESS on macOS/iOS/Xcode 26.4 in debug mode on physical devices#184254
#184690
Labels
P1High-priority issues at the top of the work listc: crashStack traces logged to the consolec: fatal crashCrashes that terminate the processdependency: dartDart team may need to help usfyi-toolFor the attention of Flutter Tool teamplatform-iosiOS applications specificallyteam-iosOwned by iOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-iosTriaged by iOS platform teamworkaround availableThere is a workaround available to overcome the issue

Description

@joserodpt
joserodpt
opened on Mar 27, 2026

Steps to reproduce

  1. Have macOS 26.4
  2. Create a default flutter project (using Android Studio)
  3. 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
Pinned by vashworth
@vashworthvashworthon Mar 30, 2026

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

View full comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High-priority issues at the top of the work listc: crashStack traces logged to the consolec: fatal crashCrashes that terminate the processdependency: dartDart team may need to help usfyi-toolFor the attention of Flutter Tool teamplatform-iosiOS applications specificallyteam-iosOwned by iOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-iosTriaged by iOS platform teamworkaround availableThere is a workaround available to overcome the issue

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions