Skip to content

Debugging on apple silicon for macos device fails #175320

Closed
Closed
Debugging on apple silicon for macos device fails#175320
Labels
r: solvedIssue is closed as solved

Description

@rob-linton
rob-linton
opened on Sep 14, 2025

Steps to reproduce

On mac with Apple Silicon

  1. Install Arm64 version of flutter
  2. Install Arm64 version of xcode
  3. Install rosetta
  4. Set device to macos
  5. execute "flutter run -d macos"

Actual results

flutter run -d macos shows:

Launching lib/main.dart on macOS in debug mode...
Building macOS application...                                   
2025-09-12 22:27:36.073 xcodebuild[31325:18440846] Writing error result bundle to /var/folders/87/j94_scnj7fdf69x1t7ylgcv80000gq/T/ResultBundle_2025-12-09_22-27-0036.xcresult
xcodebuild: error: Unable to find a device matching the provided destination specifier:
                { platform:macOS, arch:arm64 }

        The requested device could not be found because no available devices matched the request.

        Available destinations for the "Runner" scheme:
                { platform:macOS, arch:x86_64, id:8A5DDD83-29D7-5EBE-B72E-CD7A43E79F94, name:My Mac }
                { platform:macOS, name:Any Mac }
Error: Build process failed

Flutter doctor shows:

rob@MACsecret_is % flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.35.3, on macOS 15.6.1 24G90 darwin-arm64 (Rosetta), locale
    en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] VS Code (version 1.103.2)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!

Flutter --version shows:

rob@MAC secret_is % flutter --version
Flutter 3.35.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision a402d9a437 (11 days ago) • 2025-09-03 14:54:31 -0700
Engine • hash 672c59cfa87c8070c20ba2cd1a6c2a1baf5cf08b (revision ddf47dd3ff) (11 days ago) •
2025-09-03 20:02:13.000Z
Tools • Dart 3.9.2 • DevTools 2.48.0

xcode build version shows:

rob@MAC1226 ~ % xcodebuild -version
Xcode 16.4
Build version 16F6

Logs

https://pastebin.com/d1CCb6sH

Flutter Doctor output

Doctor output 
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.35.3, on macOS 15.6.1 24G90 darwin-arm64 (Rosetta), locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] VS Code (version 1.103.2)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!

Activity

  1. darshankawar
    added
    in triagePresently being triaged by the triage team
    on Sep 15, 2025

  2. darshankawar commented on Sep 15, 2025

    @darshankawar
    darshankawar
    on Sep 15, 2025
    Member

    https://pastebin.com/d1CCb6sH

    From this log, the Build settings for target runner shows ARCHS = x86_64 and CURRENT_ARCH = undefined_arch and EXCLUDED_ARCHS = arm64 and VALID_ARCHS = x86_64 .

    @rob-linton Are you able to run via Xcode properly ?

  3. darshankawar
    added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 15, 2025

  4. rob-linton commented on Sep 15, 2025

    @rob-linton
    rob-linton
    on Sep 15, 2025 via email · Hidden as outdated
    Author
  5. github-actions
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 15, 2025

  6. darshankawar commented on Sep 16, 2025

    @darshankawar
    darshankawar
    on Sep 16, 2025 · Hidden as outdated
  7. darshankawar
    added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 16, 2025

  8. rob-linton commented on Sep 17, 2025

    @rob-linton
    rob-linton
    on Sep 17, 2025 · Hidden as outdated
    Author
  9. github-actions
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 17, 2025

  10. darshankawar commented on Sep 17, 2025

    @darshankawar
    darshankawar
    on Sep 17, 2025 · Hidden as outdated
  11. darshankawar
    added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 17, 2025

  12. rob-linton commented on Sep 19, 2025

    @rob-linton
    rob-linton
    on Sep 19, 2025 · Hidden as outdated
    Author
  13. github-actions
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 19, 2025

  14. darshankawar commented on Sep 19, 2025

    @darshankawar
    darshankawar
    on Sep 19, 2025
    Member

    if you can send me the verbose log of the successful build that you have completed and I'll compare that to this build and see what's is different.

    @rob-linton Sure, here's the successful run log for a counter app.

    flutter_macos_log.txt

  15. darshankawar
    added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 19, 2025

  16. rob-linton commented on Sep 23, 2025

    @rob-linton
    rob-linton
    on Sep 23, 2025
    Author

    I can see flutter doctor returns the following:

    Doctor summary (to see all details, run flutter doctor -v):
    [✓] Flutter (Channel stable, 3.35.4, on macOS 15.6.1 24G90 darwin-arm64 (Rosetta), locale en-GB)
    [✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    [✓] Xcode - develop for iOS and macOS (Xcode 26.0.1)
    [✓] Chrome - develop for the web
    [✓] Android Studio (version 2024.2)
    [✓] VS Code (version 1.104.1)
    [✓] Connected device (4 available)
    [✓] Network resources

    I believe flutter is running under rosetta even though the version downloaded was:

    flutter_macos_arm64_3.35.4-stable.zip

    You can see in my log when flutter executes uname it returns x86_64

    [        ] executing: uname -m
[  +10 ms] Exit code 0 from: uname -m
[        ] x86_64

    Whereas if I run it directly it returns the correct architecture:

    rob@MAC1226 bin % uname -m
arm64

    Whereas in your log it returns the following:

    [        ] [        ] executing: uname -m
[        ] [   +3 ms] Exit code 0 from: uname -m
[        ] [        ] arm64

    Which is correct.

    This may be an artifact that the time machine restore of this mac was from an intel macbook to an arm macbook.

    I'm assuming that there are other cached artefact's elsewhere on this mac that came over from the time machine backup.

    If you can point me to where these may be I'll see if I can clean them up, otherwise probably the only recourse is a complete rebuild of this mac from scratch.

    Thanks

  17. github-actions
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 23, 2025

  18. darshankawar commented on Sep 24, 2025

    @darshankawar
    darshankawar
    on Sep 24, 2025
    Member

    Thanks for the update @rob-linton and patience while we try to figure this out.
    I don't know if you are already aware, there are two separate Xcode releases as listed in https://xcodereleases.com/:

    Image

    The Xcode Apple Silicon version as the name suggests is for chips with Apple silicon support, while the other is most probably for intel, so please check if this could be a factor in your case or not.

  19. darshankawar
    added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 24, 2025

  20. rob-linton commented on Sep 24, 2025

    @rob-linton
    rob-linton
    on Sep 24, 2025
    Author

    I've downloaded the apple silicon version of xcode and flutter run -d macos is now working!

    Thanks for the assist, I appreciate your support in getting this issue resolved.

    Thank you.

  21. github-actions
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Sep 24, 2025

  22. darshankawar commented on Sep 24, 2025

    @darshankawar
    darshankawar
    on Sep 24, 2025
    Member

    Good to know. Closing as resolved.

  23. darshankawar
    closed this as completedon Sep 24, 2025
  24. darshankawar
    added
    r: solvedIssue is closed as solved
    and removed
    in triagePresently being triaged by the triage team
    on Sep 24, 2025

  25. github-actions commented on Oct 8, 2025

    @github-actions
    github-actionsbot
    on Oct 8, 2025 – with GitHub Actions

    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 -v and a minimal reproduction of the issue.

  26. github-actions
    locked as resolved and limited conversation to collaborators on Oct 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    r: solvedIssue is closed as solved

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions