I've developed an application in Android Studio and now I'd like to generate the apk.
I followed some tutorials where I went in Build -> Generate Single Budle ... and a ".jks" file is generated.
Is this file that I should copy to my mobile phone? If so, how?(a message appears saying that the file is not supported).
Everything is very simple.
Build -> Generate Signed Bundle / APK -> Set APK
Use your key or create new *this key is your digital signage
After Successful build you can find your APK file inside the project folder itself.
(path: project_folder/app/release/apk-release.apk)
Put attention to digital signature! If you are publishing your APP in Google Play store, then you should keep that file safely. If you lose your key,then you can't submit any updates to your App. Even nunky from Google can't to do anything. Keep it in a safe place.
Related
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 am new to publishing to google play, but everywhere I looked says that you just click build then upload the apk file you get to google play. But the file I am receiving is an .aab file with no APK file to be found. I messed with my settings but cannot figure out why this is happening.
Thing I have tried:
1. Updating Unity
2. Change keystore file
I am not too familiar with unity, so I don't want to mess with too many settings with the risk of messing up the application further
when you generate Signed Bundle or APK for release, if you select Android App Bundle you can get .aab (bundle file).
if you want to get .APK you have to select APK.
in this screen.
I recently made my first app in Android Studio and made it into an APK. Google play said I had the wrong signature for the APK but I don't know how to change the APK with different signatures nor revert the program back in order to manually change it inside Android Studio. Any help on this?
Here is step by step what I did to get to this point. I finished writing my program and went to "build" then "generate signed apks" where I went through the process of making the keys, key store etc. At this point everything is fine. I just need to somehow go back into the apk and either change the signatures of it or unpack the apk in studio and redo the process of generating signed apks.
You need to sign the apk with the same public-key certificate which you use in the previous uploaded apk. When you build the release apk via Build -> Generate Signed Apk.., you will be presented with the following dialog:
Then you must use the same certificate file (something like android.jks) for the Key store path.
The documentation says:
Every app must use the same certificate throughout its lifespan in
order for users to be able to install new versions as updates to the
app. For more about the benefits of using the same certificate for all
your apps throughout their lifespans, see Signing Considerations
below.
So, if you lose the certificate file, there is no way you can upload the apk with the same package name again. It will lose forever, gone. You also can't delete the published apk to reuse the same package name again.
I created an android application to connect external sql server over WiFi and fetched some data and displayed. I generate its apk via Build>Build apk. It creates apk folder in output folder of build which contains 'app.debug.apk' and 'app.debug.unaligned.apk'. I installed it in my android smartphone. The app is opened and shows layout. It doesn't shows any error message. But I can't fetch my data from sql server.
I don't know what is the problem with that.
Help me.
You need to follow steps for generating signed APK:
Click on Build > Generate Signed APK in the menu.
Click Next to build an APK for the app module.
Click on Create New to create a new keystore file.
Fill in the fields to create your keystore and key as appropriate.
Generate your signed APK.
For pictorial representation and more detailed answer please refer this link : How to generate signed APK
I am developing for an application currently.
But when i will finish my app developement and i create .apk, should i sign it or make it unsigned while giving my app to my client for testing on their own devices??
He should not be able to put this apk on market as an author/ He should not distribute without my permission.
Any suggestions are welcome.
Thanks.
You can sign with your debug key which in windows resides in: username/.android/debug.keystore
Password is: android
Sec password is: android
Edit: But if the person has some knowledge he can just resign it with another key, you can't really protect yourself against this (afaik).
Steps:
In Android Studio Generate Build APK
Build -> Build APK
You get popup once apk is generated
Build APK
Apk(s) generated successfully.
Shown in File Manager.
Goto https://www.diawi.com/ and signup if if you are a new user, else login.
In above link you may find option "Upload your app".
Inside that box you ma find "Drag&drop files here .ipa or .zip(.app) .apk"
So Drag and Drop apk file or Browse apk file using + Add file(s) button.
After uploading apk Click on Send button.
This will generate a URL and Barcode.
Share that URL with a person who want to test the build.
you don't need to sign using debug key, android sdk does it automatically, and android applications signed by debug key is not possible to upload on market, you can get apk file in bin directry of your project.
file-> export
click on android
select "export android application"
specify the path