8000 When running `flutter doctor -v` on Windows Arm64, why does the output show that the connected Windows device is of x64 architecture? · Issue #167175 · flutter/flutter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

When running flutter doctor -v on Windows Arm64, why does the output show that the connected Windows device is of x64 architecture? #167175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
kjxbyz opened this issue Apr 15, 2025 · 5 comments
Closed

When running flutter doctor -v on Windows Arm64, why does the output show that the connected Windows device is of x64 architecture? #167175

kjxbyz opened this issue Apr 15, 2025 · 5 comments
Labels
r: duplicate Issue is closed as a duplicate of an existing issue

Comments

@kjxbyz
Copy link
kjxbyz commented Apr 15, 2025 •
edited
Loading

When running flutter doctor -v on Windows arm64 architecture, why does the output show that the connected Windows device is of x64 architecture?

https://github.com/PicGuard/PicGuard/actions/runs/14466626912/job/40570401197

[!] Flutter (Channel [user-branch], 3.29.2, on Microsoft Windows [Version 10.0.22631.4890], locale en-US) [2.7s]
    ! Flutter version 3.29.2 on channel [user-branch] at C:\a\_temp\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 c236373904 (5 weeks ago), 2025-03-13 16:17:06 -0400
    • Engine revision 18b71d647a
    • Dart version 3.7.2
    • DevTools version 2.42.3
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[√] Windows Version (11 Enterprise ARM 64-bit Processor, 23H2, 2009) [23.0s]

[!] Android toolchain - develop for Android devices (Android SDK version 35.0.1) [32.2s]
    • Android SDK at C:\Android\android-sdk
    • Platform android-35-ext14, build-tools 35.0.1
    • ANDROID_HOME = C:\Android\android-sdk
    • ANDROID_SDK_ROOT = C:\Android\android-sdk
    • Java binary at: C:\hostedtoolcache\windows\Java_Temurin-Hotspot_jdk\8.0.442-6\x64\bin\java
      This JDK is specified by the JAVA_HOME environment variable.
      To manually set the JDK path, use: `flutter config --jdk-dir="path/to/jdk"`.
    X Could not determine java version
    • All Android licenses accepted.

[√] Chrome - develop for the web [8[57](https://github.com/PicGuard/PicGuard/actions/runs/14466626912/job/40570401197#step:4:58)ms]
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop Windows apps (Visual Studio Enterprise 2022 17.13.1) [852ms]
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Enterprise
    • Visual Studio Enterprise 2022 version 17.13.3[58](https://github.com/PicGuard/PicGuard/actions/runs/14466626912/job/40570401197#step:4:59)18.85
    • Windows 10 SDK version 10.0.26100.0

[!] Android Studio (not installed) [89ms]
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/to/windows-android-setup for detailed instructions).

[√] Connected device (2 available) [8.9s]
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22[63](https://github.com/PicGuard/PicGuard/actions/runs/14466626912/job/40570401197#step:4:64)1.4890]
    • Chrome (web)      • chrome  • web-javascript • unknown

[√] Network resources [397ms]
    • All expected network resources are available.

! Doctor found issues in 3 categories.
@kjxbyz kjxbyz changed the title When running flutter doctor -v on Windows arm64 architecture, why does the output show that the connected Windows device is of x64 architecture? When running flutter doctor -v on Windows Arm64, why does the output show that the connected Windows device is of x64 architecture? Apr 15, 2025
@darshankawar darshankawar added the in triage Presently being triaged by the triage team label Apr 15, 2025
@darshankawar
Copy link
Member

I think it is being done in the code itself, switching arm64 to x64 as I understand from it:

Image

flutter/packages/flutter_tools/lib/src/windows/windows_device.dart

Line 49 in 77c42fb

TargetPlatform get _targetPlatform => switch (_operatingSystemUtils.hostPlatform) {

See if this helps to answer your question.

@darshankawar darshankawar added the waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds label Apr 15, 2025
@kjxbyz
Copy link
Author
kjxbyz commented Apr 15, 2025 •
edited
Loading

https://github.com/PicGuard/PicGuard/actions/runs/14466626912/job/40570401197#step:4:10

The current channel's Dart SDK does not support Windows Arm64, falling back to Windows x64

Image

@github-actions github-actions bot removed the waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds label Apr 15, 2025
@kjxbyz
Copy link
Author
kjxbyz commented Apr 15, 2025

I think it is being done in the code itself, switching arm64 to x64 as I understand from it:

Image

This code means that if the host system is arm64 architecture, the build target is arm64, otherwise it is x64.

But the current situation is that my host system is arm64 architecture, but the build target is x64.

@darshankawar
Copy link
Member

Thanks for the update. This will give you more information on current state.

And you most probably need to follow-up in #62597 for the behavior you are seeing.
Closing based on it.

@darshankawar darshankawar added r: duplicate Issue is closed as a duplicate of an existing issue and removed in triage Presently being triaged by the triage team labels Apr 16, 2025
@github-actions GitHub Actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
r: duplicate Issue is closed as a duplicate of an existing issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kjxbyz @darshankawar
0