Develop Reference

Google Console APK Upload - New App fails

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.

Android Studio how to create working APK

I have an Android Studio Project and I need to create a runnable apk file for my beta testers (I pass the apk to them directly (via mail)). I tryed both to build an unsigned APK and to generate a signed one. But when I or my beta testers try to intall the APK, the installer say "App not intalled".
How can I build an APK file which work?
Thanks for help.

Having seen you case, you need to make sure that you are trying or installing signed apk. I was facing the same issue of App not installed what I did to over come the issue I build signed apk. And everything worked fine. Although the version before 3.0, without signed apk used to work, but after 3.0 or above without signed apk(if you installed directly) will not work. This will throw the same App not installed error.

Updating Android Application in Play Store Signing issue

I'll try my best to convey what my problem is, but I am having issues updating a clients application that is currently in the Play Store. The old version of the app was created by different developers.
The previous version of the app by the looks of things was created using Adobde Air, I don't have any experience at all with Adobe Air, so not too sure about the signing process with the APKs.
My new version is a new project (with same package name) created in Android Studio.
I obviously need to sign the release APK with the same certificate as the previous version. Can I do this via Android Studio using the Build > Generate Signed APK?
Will the previous developers have to provide a .keystore or .jks file? as I said i'm not sure how the signing process works when using Adobe Air.
Any help would be appreciated.
Thanks.

If you can build an apk and have the original keystore file you can sign it via the command line.
Take a look here:
You uploaded an APK that is not zip aligned error
You'll need to do the jarsigner step first, then the zipalign on the resulting file. 4 works for me as the alignment value.

React Native APK release

I'm trying to build a Singed apk using android studio. I'm using react-native. As new to this field I actually can not find how to make it. I just run it from terminal and it just builds from there.
What are the process for building a Signed apk using react-native.

The React Native Documentation for Generating a Signed APK is fairly comprehensive and should answer your question.
Be careful when generating your keystore - if you lose this you won't be able to upload updates to Google Play.

Follow this guide to sign your APK: https://facebook.github.io/react-native/docs/signed-apk-android.html#adding-signing-config-to-your-app-s-gradle-config
Run ./gradlew assembleRelease on android folder and your signed APK will be compiled in android/app/build/outputs/apk.

Exported (Uploaded) apk to the Play store getting crashed

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?