I migrated a Xamarin.Forms app to .NET MAUI. Since the last release was some time ago, I converted the keystore file to meet the latest demands, and then I could get Archiver to build the project properly.
Unfortunately, this resulted in:
/usr/local/share/dotnet/packs/Microsoft.Android.Sdk.Darwin/34.0.113/tools/Xamarin.Android.Common.targets(2409,2): error MSB6006: "jarsigner" exited with code 1. [/Users/me/Projects/MyApp MAUI/MyApp/MyMAUIApp.csproj::TargetFramework=net8.0-android]
Checking the dotnet publish command showed that the "-p:AndroidSigningKeyAlias" value was the same as the name of the .keystore file.
It took me some time to figure this out and wondering:
a) did i mis naming convention, that the alias needs to be the same as the keystore file?
b) is there a setting or something to configure this using the Archiver extension
c) should there be a selector/input step to select the alias from the keystore file
Love the extension, it really helps speed up delivery from VSCode!
I migrated a Xamarin.Forms app to .NET MAUI. Since the last release was some time ago, I converted the keystore file to meet the latest demands, and then I could get Archiver to build the project properly.
Unfortunately, this resulted in:
/usr/local/share/dotnet/packs/Microsoft.Android.Sdk.Darwin/34.0.113/tools/Xamarin.Android.Common.targets(2409,2): error MSB6006: "jarsigner" exited with code 1. [/Users/me/Projects/MyApp MAUI/MyApp/MyMAUIApp.csproj::TargetFramework=net8.0-android]
Checking the dotnet publish command showed that the "-p:AndroidSigningKeyAlias" value was the same as the name of the .keystore file.
It took me some time to figure this out and wondering: a) did i mis naming convention, that the alias needs to be the same as the keystore file? b) is there a setting or something to configure this using the Archiver extension c) should there be a selector/input step to select the alias from the keystore file
Love the extension, it really helps speed up delivery from VSCode!