When I create a release archive of a Xamarin Android app in the latest release of Visual Studio for Mac (8.1.3 build 19), I end up with two .apk's, with filenames like: com.whatevs.android.apk com.whatevs.android-signed.apk Why does it do this? What can I change in my project setup to prevent it? If it can't be prevented, then which one is the appropriate file to upload to Google Play? This actually used to be a problem a year ago or so, but went away, and now it's back...

Reputation: 14494

Visual Studio for Mac creates 2 .apk archives, one with -signed.apk

When I create a release archive of a Xamarin Android app in the latest release of Visual Studio for Mac (8.1.3 build 19), I end up with two .apk's, with filenames like:

com.whatevs.android.apk
com.whatevs.android-signed.apk

Why does it do this? What can I change in my project setup to prevent it? If it can't be prevented, then which one is the appropriate file to upload to Google Play?

This actually used to be a problem a year ago or so, but went away, and now it's back...

Upvotes: 3

Answers (2)

Mattia Ducci

Reputation: 432

This happen when you build the app and create an archive for publishing with a physical device selected in Visual Studio for Mac as target device. Select an emulator, Build all and Archive for publishing.

Upvotes: 2

Raimo

Reputation: 1536

The major differences are the debug flag and the signing keys, I guess. You can read more about signing here and manually signing here.

Upvotes: 2

Visual Studio for Mac creates 2 .apk archives, one with -signed.apk

Answers (2)

Related Questions