In order to migrate my app from .apk to .aab I went through the App Signing process that Google Play requires.
I installed Java jdk-14.0.2.jdk (because I purchased a new mac with OS 10.15.5 and it kept saying I don't have Java) and ran the below command from the terminal in the directory that I downloaded pepk.jar from Google Play to
$ java -jar pepk.jar --keystore=user.keystore --alias=bball\ battle --output=encrypted_private_key_path --encryptionkey=eb10fe8f7c7c9df715022017b00c6471f8ba8170b13049a11e6c09ffe3056a104a3bbe4ac5a955f4ba4fe93fc8cef27558a3eb9d2a52912392761fb833b656cd48b9de6a
Then I uploaded the resulting file encrypted_private_key_path so now I can see all of my app signing info under the App Signing section in the dashbaord.
Then I selected my user.keystore in unity publishing settings, put in my password, and built the aab file. But when I uploaded it to google play I got a message:
“You uploaded a debuggable APK or
Android App Bundle. For security
reasons you need to disable debugging
before it can be published in Google
Play.nullLearn more about debuggable
APKs or Android App Bundlesnull.”
So then instead of using user.keystore I renamed encrypted_private_key_path to encrypted_private_key_path.keystore and selected that in Unity player settings. But when I select it in publishing settings, it says
"Unable to list keys in the keystore.
Please make sure the location and
password of the keystore is correct."
I know I am using the correct password.
Could this be because Unity is using OpenJDK, but I ran the pepk.jar command using Java jdk-14.0.2.jdk?
Does anyone know how to resolve or troubleshoot this issue?
Hey you are supposed to use Java NDK to build the aab the process is pretty much simple im providing a link of a youtube video can check that but make sure to uncheck the development build and check android app bundle box
https://youtu.be/j0L3SDYyMJI
And for the key if the key isnt working you can contact google that you lost the key and i guess you can generate a new one
I'd like to publicate my app to GooglePlay but first i would like to do a last testing with the signed apk to ensure that all of the used API keys are working correctly with the release version (GMaps, Facebook, etc)
So i just made a signed version of my app with our release key and when i try to install the app to the device i got an error:
I have tried to copy the apk to the device and install it with an apk installer app.
Strange thing is when i do the same process with debug signing key, all is well, I can install and run the app.
Here are the steps of the procedure:
I select the release key, type password.
I do select release build type instead of debugging
Just in case i also defined in the gradle file the signing keys but I must admit i dont know is it necessary.
I tried like 7 seven times now so i assume this problem is not just a
mistyped password, also I can make this work with the standard debug android signing key.
Please help if you can.
You may be using the android 5.0 or above device.
May be your development version is not uninstalled properly.
Try this,
Just go to the Settings --> Apps --> Click on your App. ---> In App info page at the action bar menu there will be an option called " Uninstall for All users " click that. Your app will be completely uninstalled and now you can try installing the new version with no issue. Hope this will help you
NOTE : This is for lollipop and above.
Refer the screenshot attached.
For Current Updated Android Studio 2.3 users this answer is for you as hardly people use eclipse nowadays for Android development as Android studio has huge advancements.
So, Follow this way to create your Signed apk file.
Build > Generate Signed apk.
Create Keystore path.
Put Password, alias, key password.
Build type select accordingly(eg to release in playstore use release).
Signature Version select both V1 and V2 checkboxes.
Finsih.
Go to from explorer where you selected for the apk to store and you will see your .apk file name as app-release.apk use it.
selecting Signature Version v1 and v2 both solved the problem for me....try it
The same thing happened to me, as long as I generated my apk from Build> Build APK. I could install and un-install the apk as many times as they were without any problem, but instead if I generated the Build> Generate Signed APK, when I passed the apk to the phone and try to install it, it only allowed me one occasion, the same one that came out the following message:
until then everything was fine if I selected "INSTALL IN ANY WAY", but what happened if I uninstalled the app and wanted to reinstall it (a possible scenario), the following happened:
so I solved the problem by disabling play protect, which I achieved (within Google Play)> Menu> Play Protect> Search for security threats (disable).
"App not installed" shows when an app with same package already installed in same device. just delete your first application which you were using for testing purpose before making it to signed apk. This will work. cheers!
Select both Signature Version v1 and v2 will resolve the issue
v1 scheme
A JAR file can be signed by using the command line jarsigner tool or
directly through the java.security API. Every file entry, including
non-signature related files in the META-INF directory, will be signed
if the JAR file is signed by the jarsigner tool. For every file entry
signed in the signed JAR file, an individual manifest entry is created
for it as long as it does not already exist in the manifest
V2 scheme
v1 signatures do not protect some parts of the APK, such as ZIP
metadata. The APK verifier needs to process lots of untrusted (not yet
verified) data structures and then discard data not covered by the
signatures. This offers a sizeable attack surface. Moreover, the APK
verifier must uncompress all compressed entries, consuming more time
and memory. To address these issues, Android 7.0 introduced APK
Signature Scheme v2
By default, Android Studio 2.2 and the Android Plugin for Gradle 2.2 sign your app using both APK Signature Scheme v2 and the traditional signing scheme, which uses JAR signing.
It is recommended to use APK Signature Scheme v2 but is not mandatory.
please see the details
In Android Studio 3.0 and Above
As described here
Note: The Run button builds an APK with testOnly="true", which means the APK can only be installed via adb (which Android Studio uses). If you want a debuggable APK that people can install without adb, select your debug variant and click Build Bundle(s) / APK(s) > Build APK(s).
Add android:testOnly="false" inside Application tag in AndroidManifest.xml
Reference: https://commonsware.com/blog/2017/10/31/android-studio-3p0-flag-test-only.html
Above shubham soni answer works for me,actually it happens to android version >=5.0.In above you able to install just use this while creating your apk...
Here I resolved this issue
The reason behind this issue is, there is already an application with the same package name in the phone, but you cannot find it in phone menu(U already made the un-installation but actually its still in your phone).
To see the application go to phones SETTINGS -> APPS.
There you can see the application, but inside that the UNINSTALL button may be disabled. click on the menu overflow button to see Uninstall for all users.
After performed uninstalled for all users I have successfully installed my signed apk.
You can also use adb to uninstall the app from phone.
adb uninstall package name
In addition to this,
if your mobile supports multiple users then check if respective app is not installed for other users. If it is installed for others then first uninstall previous app and try again
I faced the same issue today, I remembered that I signed my apk with the "new" Google Play signing:
Make sure if you signed your application with Google Play signing.
If you did:
Upload your apk to Google Console (like you
usually would when updating your application):
After it has successfully uploaded, open the Artifact library in the menu.
You will see the apk you have just uploaded.
Press the download button and select Download derived APK.
You will now be able to install the apk.
You can delete the draft after have downloaded the apk without having to update your application to the Google Play Store
minifyEnabled false
is the only that worked for me after 3 days of research on all forum!
Android Studio 4.1.1
If you want to create the debug apk, and just before creating the apk you tried running on your phone/simulator (doing create signed apk right away will cause the APP NOT INSTALLED),YOU SHOULD CLEAN THE PROJECT before creating signed bundle/apk
It's quite old question, but my solution was to change versionCode (increase) in build.gradle
Go To Build.Gradle(module:app)
use this - minifyEnabled false
That may because you run APK file from external SD card storage.
Just copy APK file into internal storagem problem will be solved
This can happen due to your choice of the signature version. On some phones, installation errors occur if the signature version was selected as V2. So if that happens, try selecting V1, it will surely work.
Removing android:testOnly="true" attribute from the AndroidManifest.xml worked.
link
I am using Android 10 in MiA2. The mistake I was making is that I tried to install the app via ES Explorer. I tried Settings -> Apps & Notifications -> Advanced -> Special App Access -> Install Unknown Apps -> ES File Manage -> Allow from this source. Even then the app won't install.
Then I tired to install the app using the default File Manager and it installed easily.
The checked answer is for rooted devices, or at least it doesn't work for me.
I found a way that you can simply solve the problem by uninstall your apk from adb by using adb uninstall app.package.name (make sure that Debug app is installed on your phone)
then try to install signed apk. Hope this helps you guys.
I was facing the same issue with my android application.
I just updated a library and then created a signed APK. Now it's working.
if Your Android Studio Version Greater than 3.0
Looks like we can not directly use the apk after running on the device from the build -->output->apk folder.
After upgrading to android studio 3.0 you need to go to Build -> Build Apk(s) then copy the apk from build -> output -> apk -> debug
File > Project Structure > Build Variants > Select release > Make sure 'Signing Config' is not empty > if it is select from the drop window the $signingConfigs.release
I did this with Android Studio 3.1.4 and it allowed me to create a release apk after following all the steps above of creating the release apk and release key and adding the info to the app gradle. Cheers!
You don't have to uninstall the Google Play version if App Signing by Google Play is enabled for your app, follow the steps:
1. Make a signed version of your app with your release key
2. Go to Google Play Developer console
3. Create a closed track release (alpha or beta release) with the new signed version of your app
4. You can now download the apk signed by App Signing by Google Play, choose derived APK
Install the downloaded derived APK
The reason is App Signing by Google Play signs release apps with different keys, if you have an app installed from Play Store, and you want to test the new release version app (generated from Android Studio) in your phone, "App not installed" happens since the old version and the new version were signed by two different keys: one with App Signing by Google Play and one with your key.
Kindly uninstall the debug app in the device or just increase the version code to overcome this issues
In my case I was trying to test installing a signed APK and the current installed version on my device was unsigned (building a debug version directly from Android studio)
I tried a lot of things and the following combination worked
Clean, Rebuild
Generating a new key. I used a new key alias that had not been used before. Also, for all the passwords, I used only alphabets and numbers without any spaces or special characters
To uninstall any apk, version etc from the device, I connected my device via usb and ran the command
gradlew uninstallAll
The signed release and debug apk worked
(Note: The debug and release configurations had)
minifyEnabled false
shrinkResources false
versionCode and versionName must be greater than preview version in app level build.gradle file.
I am working on the In-App tutorial and I am getting an error saying the version is not configured for billing through Google store.
There may be some confusion as to the version being used on my device.
This is my normal process
I have a signed key that has been setup and does work properly
I use Eclipse and I build my app there I build it constantly buy clicking the build icon and if my device is connected it opens on the device I do not sign anything that I know of (which leads to some confusion)
When I want to release the App I export it with the signed key and I have to export signed Application Package in the Android Tools I see when I right click on the App. An .apk file is generated and I upload that to google and everything works.
My question is when I simply run the App on my phone and it comes directly from eclipse what mode is it in
The In-App tutorial says I must be running the signed version on my phone.
Am I doing this automatically when I start it from Eclipse or is it in debug mode.
If it is debug mode how do I make it go into signed mode from Eclipse.
The version I need to upload to google is signed but is set as UNPUBLISHED as stated by the guide in the tutorial so I can not get it from the store.
To test anything that has to interact with the Google store, you need to use the release version of the .apk file. Export it as usual from Eclipse, then use the command line tool to install the release .apk on the device or emulator:
>adb install myApp.apk
If you previously ran on the same device or emulator from within Eclipse, the app will have been signed with the debug cert and you will have to completely uninstall it first. Even the -r switch on the apk install command won't install if the signing certs are different.
It is written in App-Signing that
The Android system will not install or run an application that is not signed appropriately.
But, I am wondering why I can still run an unsigned application in the emulator. I am thinking that signing of an application is only needed when publishing the application. Is my understanding correct?
Thanks,
artsylar
The android system checks your application certificate every time you install it. When you run an application on emulator, IDE signs it for you with generated debug certificate.
You can see that it is true by performing an experiment:
From one computer install an application using IDE on your device.
Then try to install the same application from another computer. You will get an error while installing : wrong certificate.
Remember, that this debug certificate is valid until you want publish the application. Then you will need to create a keystore and properly sign the application. Don not forget to backup the keystore!
Yes...
If you are running over the emulator no need to sign the app because android build tool will do that automatically.
If you want to make it available to end users you must sign it with your private key to avoid tampering of an application.
The application you are using in the emulator is signed at compile time with a debug certificate. So the app is signed but out of simplicity this is done automatically for you.
check this question
Note that "unsigned" is probably not what you are referring to here. When you create an APK during the normal development process, it is signed by a debug key. Such APKs can be distributed but will not work, for example, on the Android Market. A truly "unsigned" APK can be created, but it cannot be installed unless you manually sign it