beni
beni

Reputation: 3029

Why my signed apk crashes?

I've signed an app with a sign which I've created. I've installed this apk in my phone and this is ok, but when I've tried to open the app crashes (doesn't show any activity), and it doesn't give me the posibility to watch the log (this dialog doesn't have the report button)

The problem is the sign which I've signed the app. I've tested with other sign and the app opens perfectly. I can't post any information about the creation of the sign, but only I can say I've used:

Letters and _ character in alias

Letters, numbers and - character in password

50 in years

and Letters in name

others field are blank.

The main problem is that the app is published in the google play, so How I can publish a new signed apk without to unpublish this app and create a new app?

Upvotes: 9

Views: 16984

Answers (8)

Aryan Tech
Aryan Tech

Reputation: 13

You can simply create a new keystore if you are in testing Or simply in my case retype the password

Upvotes: 0

Nur Hidayah Roslee
Nur Hidayah Roslee

Reputation: 151

In my case, I had to change the minifyEnabled to false in build.gradle

buildTypes { release { minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro' } }

Upvotes: 5

Ben
Ben

Reputation: 265

I had the same problem today and for me it turned out the reason was:

I used void blaMethod() in my Java code which I tried to call by onClick methods of XML Buttons. I had to learn that these methods need to be public void ... - I usually do that, but this time I got a little sloppy.

The strange thing is: my unsigned APK worked perfectly fine on all my devices, but the signed one just crashed when using those methods (could not find method (view) in a parent or ancestor context). Don't get why that is... May this help someone!

Greets

Upvotes: 0

Brad Adams
Brad Adams

Reputation: 2069

For anyone getting this in a react-native environment, remember to bundle your js before generating the signed APK.

Easy to forget if you're using something like Android Studios GUI 🙃

Upvotes: 8

voxoid
voxoid

Reputation: 1289

Another possible cause (as was the case for me) is using the wrong JDK/JRE version when building your signed APK.

If you're using Eclipse, check Window -> Preferences -> Java -> Installed JREs and see which one is checked as the default. Android is not yet compatible with Java 8.

Upvotes: 0

Palak
Palak

Reputation: 2215

Delete "gen" folder from the Project then Cleaning the project

Upvotes: 6

Zakharov Roman
Zakharov Roman

Reputation: 779

Cleaning the project solved the problem in my case.

Upvotes: 9

Palak
Palak

Reputation: 2215

You can see this publish APK and its details like version code and version name and etc. in you developer account on google play

There is one button "Upload new APK"

  • Click on "Upload new APK" Button
  • Upload new sign APK with bug fixed
  • deactive current APK
  • Active new apk

Note : Don't change package name for new APK

Upvotes: 2

Related Questions