Could someone tell me the steps of how to actually get your app (built in AS) on the play store?
I already:
made myself an Android developers console account.
paid the 25$ fee.
built a Signed version of my apk.
( i don't know where he built it to, AndroidStudioProjects\MyApplication\app\build\outputs\apk ? )
Do i need to rename the built apk to the desired app name ?
So please could someone describe the steps starting from 0, So future people with the same problem can find the solution easly ?
Before publishing your app to play store, you need to follow following two steps:
1. Get the signed version of apk: If you are using Eclipse,
Right click on project > Android tools > Signed version of application package
2. Zip align the apk obtained from above step:
"\sdk\build-tools\android-4.4W\zipalign.exe" -f -v 4 "\SignedProject.apk" "\Project_ZipAligned.apk"
The project that you created should have a .apk file or you can create a signed apk file . To sign you application go here http://developer.android.com/tools/publishing/app-signing.html. Once you have you apk file, app icons ready you need to upload them on the website. At this point you will be ready to publish.
Related
When I upload it to the Google Play Store, it tells me it's been signed in debug mode and needs to be signed in release mode.
I only have the apk file and unfortunately lost the source files.
Try to decompile your apk and restore your source code then signed it
Decompile Apk and Dex Android files to Java
First of login to google console and get keygen.
In keygen property file, enter the credential like
key.store=debug.keystore
key.alias=androiddebugkey
key.store.password=abc
key.alias.password=abc
Also download keystore file from google console and place it in /app folder.
After then, run the command as -
./gradlew assembleRelease
This will create sign release apk in output folder
It is not possible to add it in playstore without having source code.
Anyway , in future , you will need source code in order to make updates to the
app .
For next projects try to use git in order to keep your projects.
Are you the author of this app ? From where do you have the apk ? Did not generate it ? Apk is in general in project output folder . Or do you have this apk from someone and you want to put it in play ?
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.
PhoneGap Build seems like a great tool and I've build an .apk with it and tested it on multiple Android devices.
Now I need to submit it to the Google Play store but I need to sign the apk.
I've read all about signing an .apk on Google's developer site but it seems that I need to install the Android development tools and use Eclipse. I've installed it but I can't find a way to import my .apk so I'm stuck.
I don't get it - what is the point of PhoneGap Build then?
This is all very disheartening. The app is ready to go but...
This was the solution.
I got the Android dev kit - http://developer.android.com/sdk/index.html
From there I used this video to get KeyTool: http://www.youtube.com/watch?v=IaXE2FUENFI
From there I could create a KeyStore. Make sure you keep a record of the Alias and Password (I wrote them down and did not store them on any electronic device) and the location of the keystore.
When you are in PhoneGap Build and you pull files from GitHub (which is the way I'm doing it) after the build is done you'll see there is a dropdown. Select "add a key" and upload your keystore.
Note: The keystore will usually be locked. You have to unlock it in order to build with it. It only stays unlocked for one hour.
You PhoneGap Build apk will now be appended with -release instead of the usual -debug.
It's now ready for uploading to Google Play!
Go Build! :)
I have never used PhoneGap or signed an apk, but I found this on the phonegap.com website:
https://build.phonegap.com/docs/config-signing-android
Sounds like you can just add your signing key (How to get one) to your phonegap account and when a release build of your app is made with the PhoneGap Build they sign it.
You need to provide Title, Alias and a Keystore File to PhoneGap Build.
Generate a private key using keytool (comes with the Java SDK - so no Eclipse required)
On your next PhoneGap Build be sure to enter the Information under Options>Add a key
PhoneGap Build takes care of the rest.
As far as the keytool goes, someone else gave a short & sweet description of how to...
I'm having a few issues with Android/Eclipse with using Android Market Billing. I have to sign my application properly for it to work (according to the dev guide), but I don't want to have to go through the whole process all the time.
Is there a step I can add to Eclipse so it'll automatically sign the APK?
You can use Ant to export a signed APK with a single command. There is no single-click 'Export signed APK' action in Eclipse.
You can use the Export Wizard from Package Explorer.
With 3 simple steps you are ready to publish on an application marketplace such as Google Play.
Check the link below for more info
http://developer.android.com/guide/publishing/app-signing.html#ExportWizard
I would like to know about Android application signing.
IFAIK, blackberry and iphone application must be signed to work on the real device.
For the Android, does application need to sign ?
If so, how to sign the application ?
Please advice. guys.
Thanks in advance.
If you are using the Eclipse plugin.
Right click on the project > Android Tools > Export Signed Application Package
Follow the instructions for creating a .keystore file and you're sorted!
There's a guide to signing Android applications on the developer website: http://developer.android.com/guide/publishing/app-signing.html
To answer your immediate concern: you don't need a real device to sign an application. You sign during the build process, so it can be done on any computer with the correct software (which is all free). The easiest way to build a signed application is to just use Eclipse's ADT plugin, which has an "export signed application" feature.
As #Laurence Dawson mentioned one way to do this is just by opening your project in eclipse then
Right click on the project > Android Tools > Export Signed Application Package
BUT you MUST create a Keystore prior to do this, this is really easy and simple the option will appear after you select "Export Signed Application Package" from right click options, it will ask you to "sign" your APK (in order to Beta/Alpha/Production publish) this process is done simply by creating this Keystore, once its created just select this new keystore (it will appear right in the options of "Export Signed Application Package") and voila! then it will just ask you for enter the path where to upload your signed APK ready for google developer website!