Releasing to Android

Getting Started Newbie Questions
#1

Anybody have a general idea of the process to undergo for releasing my app to Android?

I am on their website now and it looks overwhelming, I am trying to make sense of it, but some extra help would be nice.

Thank you.

#2

This tells you what information are used when listing your application.

https://developer.android.com/distribute/best-practices/launch/store-listing

The .apk file you build will have to be signed. This process took me the longest.

https://docs.coronalabs.com/guide/distribution/androidBuild/index.html

#3

So after typing that command in the tutorial, I get an enter Keystore password. I never made one.

#4

Does anybody know how to go through with this entirely?

LIke the process, they went through, because the guides on Google are not helping what so ever.

#5

I haven’t released an Android app yet, but I have managed to get an app uploaded and in a published state… Just haven’t bothered to release it to production yet.

It was definitely a pain.    I had to use a combination of google’s docs and the coronalab docs since im not using Android Studio.

I believe it’s possible to not have set a password… so you might have just hit <enter>

The way google lets you just have an upload key for the app makes it (relatively)  simple, imo.   Choose the option to let google manage the app signing part.

  1. generate the upload key with keytool

  2. select that key in the dropdown when building  and build

  3. create an app on google play

  4. upload the APK for it

5.  Google will  re-sign your app and you only have to use that upload key for future uploads of that app.  (each app will have it’s own upload key)

6.  Once the APK is uploaded, it is then just a matter of filling out all the stuff that has grey checkmarks next to it.

That was my experience… hopefully it helps a bit.

#6

This helps. Thanks for your input.

#7

We have a guide on signing your APK: http://docs.coronalabs.com/guide/distribution/androidBuild/index.html

We don’t document how to manage the Google Play developer console because Google changes it way too frequently.

Rob

#8

Sorry if I sound a bit flustered, I almost lost my developer account, but I found it again. So, I am coming back to this with a positive attitude now.

#9

Ok, got it, I generated a keystore for the app, now what do I do? 

Actually, I need to upload the apk, nevermind.

#10

  • generate a keystore (just once, and MAKE A SECURE BACKUP OF IT, and don’t forget the password)

  • build, signing with that same keystore every time you rebuild

  • upload the signed apk (i don’t let gplay resign my apps, but you can if you want)

you’ll have to also finish the other parts of your listing before you can actually publish, but that’s a separate issue.

#11

This tells you what information are used when listing your application.

https://developer.android.com/distribute/best-practices/launch/store-listing

The .apk file you build will have to be signed. This process took me the longest.

https://docs.coronalabs.com/guide/distribution/androidBuild/index.html

#12

So after typing that command in the tutorial, I get an enter Keystore password. I never made one.

#13

Does anybody know how to go through with this entirely?

LIke the process, they went through, because the guides on Google are not helping what so ever.

#14

I haven’t released an Android app yet, but I have managed to get an app uploaded and in a published state… Just haven’t bothered to release it to production yet.

It was definitely a pain.    I had to use a combination of google’s docs and the coronalab docs since im not using Android Studio.

I believe it’s possible to not have set a password… so you might have just hit <enter>

The way google lets you just have an upload key for the app makes it (relatively)  simple, imo.   Choose the option to let google manage the app signing part.

  1. generate the upload key with keytool

  2. select that key in the dropdown when building  and build

  3. create an app on google play

  4. upload the APK for it

5.  Google will  re-sign your app and you only have to use that upload key for future uploads of that app.  (each app will have it’s own upload key)

6.  Once the APK is uploaded, it is then just a matter of filling out all the stuff that has grey checkmarks next to it.

That was my experience… hopefully it helps a bit.

#15

This helps. Thanks for your input.

#16

We have a guide on signing your APK: http://docs.coronalabs.com/guide/distribution/androidBuild/index.html

We don’t document how to manage the Google Play developer console because Google changes it way too frequently.

Rob

#17

Sorry if I sound a bit flustered, I almost lost my developer account, but I found it again. So, I am coming back to this with a positive attitude now.

#18

Ok, got it, I generated a keystore for the app, now what do I do? 

Actually, I need to upload the apk, nevermind.

#19

  • generate a keystore (just once, and MAKE A SECURE BACKUP OF IT, and don’t forget the password)

  • build, signing with that same keystore every time you rebuild

  • upload the signed apk (i don’t let gplay resign my apps, but you can if you want)

you’ll have to also finish the other parts of your listing before you can actually publish, but that’s a separate issue.