I have published an app on the play store yesterday. Now the app is live but when I tried to install the app from the Play store, its not even showing the splash screen. It's just show unfortunately stopped Error. the .apk from the project is working fine.
How do I fix this?
I have used the following as reference to upload the apk on the play store
http://www.instructables.com/id/Publishing-an-Android-App-to-the-Google-Play-Store/?ALLSTEPS
When you sign apk some times if it is not properly signed then references are mismatched and exception will occur for casting views.So every time clean your project and directly export your apk without run the code.After exporting apk test in your device before uploading on play store to check weather it is running properly or not.
Clean your code and publish the signed apk again, it happened with me twice.
EDIT:
Removing warnings will be a plus point, Clean your project, make signed app and before deploying run this apk in to your phone for testing.
You need to check the apk file that you uploaded to play store.Do install the same and check the crashlog .I am sure the issue will be with the apk so you need to upload new.
Do clean the project and export your signed apk.
And also for checking the crash log for remote devices you need to add library like ACRA do check the SO post here
How do I obtain crash-data from my Android application?
Related
I'm developing a game for mobile and it's done, but google play asks for aab format. The issue is: when I build it as APK it works normally, but when I build it as AAB the user can't log in using google account.
I remade the build steps over and over, tried to build using mac and pc. Did all the SHA1 stuff I found online, but it still doesn't work as AAB. Anyone knows what it could be?
Recently trying to create a new App and upload a brand new APK with self signed certificate (Not Google App Signing) Results in the following error
You uploaded an APK or Android App Bundle that is signed with a restricted certificate. You need to upload an APK or Android App Bundle signed with your own certificate.
I don't believe this error is entirely correct as I do sign the certificate myself locally, this seems like a recent change to our on boarding process and opt-in is now default for google app signing but our infrastructure doesn't have the right pipeline for this yet.
Is there any other things to verify and test, as I see the keystone file is still there and there's no build errors when it's being signed. Also this is a brand NEW application I don't understand why this error would occur for the initial upload since there's no other keys to check against.
I've searched the net but most issues appear to be happening in 2018 and this is more of a recent change that started to occur for us.
EDIT: This is using Cordova build tools not through Android Studio.
Try to follow these trouble shoot steps and see if that will solve your issue:
Clear everything in the Release folder, present in app->build->outputs->apk->release.
Generate new signed apk which will get created in the same above mentioned directory.
Make sure you are bumping the version code.
I don't have a full answer as to Why it was failing, however right after the build for cordova build android --release that APK will upload. But If I use that APK in an emulator to test something first that APK is no longer valid to upload and I get the error pasted above.
basically in our pipeline I had to create a copy of the APK right before creating screenshots and then use the copied APK to upload onto google console.
I´m trying to make a signed apk using Intellij.
I can run normally this->.../build/app/outputs/apk/app.apk
But I´m trying to make a signed app to publish into Play Store.
According this Generating a Signed Release APK Through an Artifact
It´s possible to Intellij generate a signed apk to publish....but I can´t.
Sometimes it´s not possible to install the apk at the phone...other times it´s possible to install, but it´s not working.
I didn´t understand about the resources of the artifact. What is necessary to make an artifact to generate a correct apk?
What am I doing wrong?
Thanks
I am getting this error when trying to upload an update for my app.
I have changed my pc after releasing the previous update, so I had to reinstall Android Studio and everything with it.
Luckily I managed to recover my key.jks file that it's mandatory to update the app since it has to be unique.
I have signed the app from android studio using it, with the alias I remembered and it seems to have compiled and built the app without any problem (I only had to change the keystone and alias passwords).
Still when I try to upload the apk, I get an error in the developer console that says that the apk is not signed.
Any Idea on why this happens?
Using the keytool tool in the JDK 8, I signed my APK and successfully uploaded it to the play store. However, once I downloaded it, it said, "Package was not signed correctly". Does anyone know how to fix this?
Do you have your debug version of application still installed on your
device?
If yes, Now you have downloaded a different copy of the same app and it's causing this error.
Uninstall the app completely from your device. Then download it from the market again and it might work.
Another reason
I did a quick research and In Many links and Blogs, people seem to have faced the similar issue and they have started using jdk 6 and signed their app and uploaded to playstore again.
Published Android apk gives error "Package file was not signed correctly"
http://developer.appcelerator.com/question/146110/my-app-gives-package-file-was-not-signed-correctly-error-on-google-play-store
http://support.ludei.com/hc/communities/public/questions/200781567-Google-Play-error-Package-file-was-not-signed-correctly-
Hope this information helps.