Android framework version
net10.0-android
Affected platform version
Visual Studio 2026 18.7.2, .NET 10 MAUI, Target Framework: net10.0-android, Android device: Android 16 (API 36)
Description
When creating an Android APK using the Visual Studio Archive Manager ("Publish" → "Archive Manager" → "Distribute"), the resulting APK cannot be installed on an Android 16 device.
The installation fails with:
adb.exe: failed to install app.apk:
Failure [-124: Failed parse during installPackageLI:
Targeting R+ (version 30 and above) requires the resources.arsc
of installed APKs to be stored uncompressed and aligned on a
4-byte boundary]
The same project builds and installs successfully when using a normal Release build with MSBuild signing (AndroidKeyStore=true).
Steps to Reproduce
- Build MAUI-App with Release/Android-LocalDevice
- Right-Click on MAUI-Project/Publish -> Archive-Manager starts and builds archive
- Archive-Manager Distribute apk-File to published folder
- Download apk-File to Android device
- Install apk-File -> Error "Not installed..."
Did you find any workaround?
- Build MAUI-App with Release/Android-LocalDevice
- Put apk-File from bin/Release/net10-android to published folder.
- Download apk-File to Android device
- Install apk-File -> OK, run as expected
Relevant log output
Android framework version
net10.0-android
Affected platform version
Visual Studio 2026 18.7.2, .NET 10 MAUI, Target Framework: net10.0-android, Android device: Android 16 (API 36)
Description
When creating an Android APK using the Visual Studio Archive Manager ("Publish" → "Archive Manager" → "Distribute"), the resulting APK cannot be installed on an Android 16 device.
The installation fails with:
adb.exe: failed to install app.apk:
Failure [-124: Failed parse during installPackageLI:
Targeting R+ (version 30 and above) requires the resources.arsc
of installed APKs to be stored uncompressed and aligned on a
4-byte boundary]
The same project builds and installs successfully when using a normal Release build with MSBuild signing (AndroidKeyStore=true).
Steps to Reproduce
Did you find any workaround?
Relevant log output