2

I have a build step setup to sign my APK file using:

/t:SignAndroidPackage

enter image description here

I then push to Hockey App for beta releases. The problem I'm having is that when the user downloads the new APK and chooses to update on their phone, I receive the "App not Installed" error.

After researching I feel it's some how related to this:

'App not Installed' Error on Android

However I'm not sure how exactly to change my build process so it's always signing with the same certificate (if that is my issue).

What do I need to do?

Community
  • 1
  • 1
aherrick
  • 19,799
  • 33
  • 112
  • 188
  • Have you tried substituting values as properties for the build step? E.g. here is how we are doing it on Jenkins (admittedly not VSTS but should show the point): jarsigner -verbose -sigalg MD5withRSA -digestalg SHA1 -keystore ${KEYSTORE_FILE} -storepass $KEYSTORE_PW -keypass $APK_KEY_PW -signedjar "${APK_SIGNED}" "${APK_BUILT}" $APK_KEY_ALIAS – Mark Larter Jun 08 '16 at 14:25
  • Isn't there dedicated build task for it `Signing and aligning APK file(s)` ? Also check here https://www.visualstudio.com/docs/build/apps/mobile/xamarin#define-your-xamarin-android-build – Milen Jun 08 '16 at 14:47

1 Answers1

0

Found this in Xamarin Build Process documentation that looks like it specifies the properties to be used for MSBuild, per my comment about substituting values.

Looks like this:

<PropertyGroup>
    <AndroidKeyStore>True</AndroidKeyStore>
    <AndroidSigningKeyStore>filename.keystore</AndroidSigningKeyStore>
    <AndroidSigningStorePass>keystore.filename.password</AndroidSigningStorePass>
    <AndroidSigningKeyAlias>keystore.alias</AndroidSigningKeyAlias>
    <AndroidSigningKeyPass>keystore.alias password</AndroidSigningKeyPass>
</PropertyGroup>

You should be able to use MSBuild variables to get the pathing correct for the keystore file.

Mark Larter
  • 2,343
  • 1
  • 27
  • 34