Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Cant upload a signed APK to PlayStore

I made an app and I published it on the PlayStore.
I made an update and now I'm trying to re-import it into the Android publish web site.

I generated my app like this : (with Android Studio)

  • Build
  • Generate Signed APK...
  • I choosed my app
  • Click "next"
  • And I used the same key, same password etc ...

The apk is succefully generated (and signed). Image

But when I tried to upload the app on the publish website (to update the app online) it tells me:

You have imported an APK file without a signature. You must create an APK file with a signature.

enter image description here

Have you got an idea why it's crashing?

It's contradincting, Android studio tells me that the signed app is generated but the website tells me it's not a signed app.

EDIT :
I tryed to "Build -> Clean Project" and "File -> Invalidate Caches / Restart..." without success. I also tryed to make a new project, copy past all code and retry :/

like image 380
TomSkat Avatar asked Apr 11 '17 07:04

TomSkat


People also ask

How do I publish an APK signed to Google Play?

In the menu bar, go to Build and select the option Generate Signed Bundle or APK. You will see a new popup screen where you will have two options to select, Android App Bundle and APK. The Android App Bundle is also used to upload the application to the Google Play Store we will talk about it later on.

Can I upload unsigned APK to Play Store?

You cannot upload to Google Store a not signed and not aligend APK. Ask your developer to give you the signed and aligend APK. Or you can ask them to provide the key to you so you can sign and align it yourself using that key .

Why does an APK need to be signed?

Application signing ensures that one application cannot access any other application except through well-defined IPC. When an application (APK file) is installed onto an Android device, the Package Manager verifies that the APK has been properly signed with the certificate included in that APK.


2 Answers

I assume that you're creating your keystore correctly and none of the solutions in AMAN SINGH's answer worked for you.

There's a new signing scheme in Android called Apk Signing Scheme v2. https://source.android.com/security/apksigning/v2

When you're signing your apk there're two checkboxes. v1 (jar signing) v2 (apk signing)

v1 signature is required, if the APK's minSdkVersion is 23 and lower. Android versions before Android Nougat (API Level 24) ignore v2 signatures so apks which don't have a valid v1 signature will be rejected by Play Store.

In Android 7.0, APKs can be verified according to the APK Signature Scheme v2 (v2 scheme) or JAR signing (v1 scheme). Older platforms ignore v2 signatures and only verify v1 signatures.

enter image description here

Edit:

Thanks Alex Klyubin for information.

like image 110
savepopulation Avatar answered Sep 30 '22 06:09

savepopulation


I don't understand the language in which the image is there but if you already uploaded your APK once then,

*) You need to use same signed keystore signature which you used first time at generating signed APK.

*) Check your Manifest.xml, android:debuggable="true" if this is there remove this line or make debuggable="false"

*) check `versionCode' should be greater than last uploaded

*) Check versionName should be greater than last uploaded

*) Tick Mark in both the column while building the Signed APK

like image 33
AMAN SINGH Avatar answered Sep 30 '22 04:09

AMAN SINGH