Clarify Windows Arm Android device debugging requirements#3376
Clarify Windows Arm Android device debugging requirements#3376jfversluis wants to merge 3 commits into
Conversation
Document Visual Studio 2026 Windows host requirements for Android physical-device debugging and point Windows on Arm users to physical devices because the Android emulator is unsupported there. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit 2bb85d9: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
There was a problem hiding this comment.
Pull request overview
Adds missing guidance to the Android physical-device setup doc so Windows on Arm users have an explicit first-party reference for host OS support requirements when debugging .NET MAUI Android apps on a physical device.
Changes:
- Updated
ms.dateto reflect the doc change. - Added a “Development computer requirements” section pointing to Visual Studio 2026 OS support and linking to existing Windows ARM emulator troubleshooting guidance.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit d875f07: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
1 similar comment
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit b0a146a: ✅ Validation status: passed
For more details, please refer to the build report. |
The Android physical-device setup article did not explain what Windows host requirements apply when debugging Android apps, which left Windows on Arm users without a clear support reference.
This update adds a short development computer requirements section that points to the Visual Studio 2026 system requirements for supported Windows versions, notes that Windows 10 ARM64 is listed as unsupported there, and links to the existing Android emulator troubleshooting guidance that directs Windows on Arm users to use a physical Android device because the emulator is unsupported.
The wording intentionally avoids making a debugger-specific support claim beyond the verified first-party documentation.
Fixes #3374
Internal previews