Fails to deploy to Android on vs2019 but not with vs2022

Question

Fails to deploy to Android on vs2019 but not with vs2022

Damian 1

After installing vs2022 (17.1.0 preview 1.1) alongside vs2019 (16.11.7), I am unable to deploy my apps to the Android emulator on vs2019. On vs2019 I am met with, Error: SB6006: "java.exe" exited with code 2" every time it tries to deploy to the emulator. On the flip-side, it does deploy with vs2022.

Note, this issue occurs with all of my apps, even the default Xamarin.Forms template apps. And, I keep my dev laptop environments minimal - Visual Studio, .NET SDK, Notepad++.

Could this be a PATH Environment Variable being out of order with the recent install of VS2022?

Reproduce

Below are the specs of a project freshly created with a new emulator generated that fails to deploy on vs2019.

Open, Visual Studio 2019 (Enterprise)
Create a new Xamarin.Forms project (Android only)
Build
Debug (play button)
Environment
- Xamarin.Forms: v5.0.0.2012
- Emulator - Pixel2 API30 (default)
- Proj - Minimum Android Version: Android 5.0 (API Level 21 - Lollipop)
- Proj - Target Android Version: Android 11.0 (API Level 30 - R)
  Build
  ...
  1>Starting deployment to pixel2_-_api_30 ...
  1>Deploying to pixel2_-_api_30 ...
  Build started.
  Project "Base2019.Android.csproj" (Install target(s)):
  Found Java SDK version 1.8.0.
  Found Java SDK version 1.8.0.
  Dex Fast Deployment Enabled: False
  MonoAndroid Tools: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\Android\
  Android Platform API level: 30
  TargetFrameworkVersion: v11.0
  Android NDK:
  Android SDK: C:\Program Files (x86)\Android\android-sdk\
  Android SDK Build Tools: C:\Program Files (x86)\Android\android-sdk\build-tools\30.0.2\
  Java SDK: C:\Program Files\Eclipse Foundation\jdk-8.0.302.8-hotspot\
  Application Java class: android.app.Application
  Project "Base2019.csproj" (GetTargetFrameworks target(s)):
  Done building project "Base2019.csproj".
  Project "Base2019.csproj" (GetTargetPath target(s)):
  Done building project "Base2019.csproj".
  Project "Base2019.csproj" (GetNativeManifest target(s)):
  Done building project "Base2019.csproj".
  Skipping target "_ResolveLibraryProjectImports" because all output files are up-to-date with respect to the input files.
  ...
  ...
  Skipping target "_CompileToDalvik" because all output files are up-to-date with respect to the input files.
  Copying file from "C:\work\labs\zFailures\Base2019\Base2019\Base2019.Android\obj\Debug\110\android\bin\com.companyname.base2019.apk" to "C:\work\labs\zFailures\Base2019\Base2019\Base2019.Android\bin\Debug\com.companyname.base2019.apk".
  Creating "obj\Debug\110\android_debug_keystore.flag" because "AlwaysCreate" was specified.
  C:\Program Files (x86)\Android\android-sdk\build-tools\30.0.2\zipalign.exe -p 4 "C:\work\labs\zFailures\Base2019\Base2019\Base2019.Android\obj\Debug\110\android\bin\com.companyname.base2019.apk" "bin\Debug\com.companyname.base2019-Signed.apk"
  C:\Program Files\Eclipse Foundation\jdk-8.0.302.8-hotspot\bin\java.exe -jar "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\Android\apksigner.jar" sign --ks "C:\Users\damians\AppData\Local\Xamarin\Mono for Android\debug.keystore" --ks-pass pass:android --ks-key-alias androiddebugkey --key-pass pass:android --min-sdk-version 21 --max-sdk-version 30 C:\work\labs\zFailures\Base2019\Base2019\Base2019.Android\bin\Debug\com.companyname.base2019-Signed.apk
  Failed to load signer "signer #1"
  java.io.IOException: Invalid keystore format
  at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:666)
  at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:57)
  at sun.security.provider.KeyStoreDelegator.engineLoad(KeyStoreDelegator.java:224)
  at sun.security.provider.JavaKeyStore$DualFormatJKS.engineLoad(JavaKeyStore.java:71)
  at java.security.KeyStore.load(KeyStore.java:1445)
  at com.android.apksigner.SignerParams.loadKeyStoreFromFile(SignerParams.java:353)
  at com.android.apksigner.SignerParams.loadPrivateKeyAndCertsFromKeyStore(SignerParams.java:239)
  at com.android.apksigner.SignerParams.loadPrivateKeyAndCerts(SignerParams.java:181)
  at com.android.apksigner.ApkSignerTool.sign(ApkSignerTool.java:277)
  at com.android.apksigner.ApkSignerTool.main(ApkSignerTool.java:83)
  MSB6006: "java.exe" exited with code 2.
  Done building project "Base2019.Android.csproj" -- FAILED.
  Build FAILED.
  1>Deployment failed to pixel2_-_api_30. ==========
  Deploy: 0 succeeded, 1 failed, 0 skipped ==========

Damian 1 Reputation point

2022-01-03T18:10:29.557+00:00

As an FYI, this has nothing to do with toggling the Multi-Dex option. And though it does mention the KeyStore, it wasn't configured before installing VS2022 and it worked.

Hope this helps. Let me know what other info may assist if someone has any ideas.

2 answers

Your answer

Damian 1 Reputation point

2022-01-03T18:10:29.557+00:00

As an FYI, this has nothing to do with toggling the Multi-Dex option. And though it does mention the KeyStore, it wasn't configured before installing VS2022 and it worked.

Hope this helps. Let me know what other info may assist if someone has any ideas.

Answer 1

Damian 1

Updated the Java JDK from v1.8 to 11.0.12.7.1 and make sure it's configured correctly in Visual Studio.

Install, JDK 11.0.12.7
- https://aka.ms/download-jdk/microsoft-jdk-11.0.12.7.1-windows-x64.msi
VS2019 > Tools > Options > Xamarin > Android
Set, SDK Location to: "C:\Program Files\Microsoft\jdk-11.0.12.7-hotspot"

More info can be found at:
* https://github.com/xamarin/xamarin-android/wiki/JDK-11-Warning

Damian 1 Reputation point

2022-01-03T21:06:38.913+00:00

This is the accepted answer, however, I don't have a way to mark the fix. lame
The issue was found on Line 15: "Java SDK: C:\Program Files\Eclipse Foundation\jdk-8.0.302.8-hotspot\"

As it turns out, Eclipse JDK-8.0 was installed during the Microsoft Azure Compute Emulator and Azure Authoring Tools install process. Nothing quite like one MS tool breaking another.
Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 36,436 Reputation points Microsoft External Staff

2022-01-04T05:48:30.077+00:00

When you change the SDK loaction to: C:\Program Files\Microsoft\jdk-11.0.12.7-hotspot, it still can't deploy your APP, right? May I ask if there are any updates of Microsoft Azure Compute Emulator and Azure Authoring Tools? Since you are using vs2022 (17.1.0 preview 1.1), you could try to install the stable version or send feedback, refer to https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes-preview#feedback-and-suggestions
Damian 1 Reputation point

2022-01-09T04:13:31.557+00:00

Hi Wenyan,
In this case, it was fixed by updating the SDK location to "...\Microsoft\jdk-11.0.12.7-hotspot".

Yes, I can to send feedback to the suggested link. At this time, I'd prefer not to downgrade back down to stable VS2022. Thank you for getting back to me. Hope you have a wonderful weekend.
Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 36,436 Reputation points Microsoft External Staff

2022-01-10T02:52:15.95+00:00

You are welcome. Happy new year!
jose rodrigo 1 Reputation point

2022-07-19T18:06:34.353+00:00

Thank you @Damian , i was looking for a solution a few days and this worked like a charm. Thanks!
Ahmed Thabet Elshamandy 40 Reputation points

2023-03-20T09:25:51.12+00:00

I solved it by change ( Java Development Kit Location) Jdk to: "C:\Program Files\Microsoft\jdk-11.0.12.7-hotspot"

Thanks @Damian for your help

Answer 2

Ahmed Thabet Elshamandy 40

VS2019 > Tools > Options > Xamarin > Android setting

I solved it by change ( Java Development Kit Location) Jdk to: "C:\Program Files\Microsoft\jdk-11.0.12.7-hotspot"

Thanks @Damian for your help

Report

Share via

Fails to deploy to Android on vs2019 but not with vs2022

Reproduce

Environment

Build

2 answers

Your answer