Uploading to google play error

When I try to upload my apk file to google play it gives me the message:

“You uploaded a debuggable APK. For security reasons you need to disable debugging before it can be published in Google Play”

I signed my app with keytool to a release keystore and selected it while building

Build: 2013.1137

The answer is pretty straight forward.  You cannot use a debug keystore to upload to a store.  You need to create your own keystore that’s designed for release, build against it, then upload the app.

Please see: http://docs.coronalabs.com/guide/distribution/androidBuild/index.html

Rob

I believe I already done that. I created my key with this command:

keytool -genkey -v -keystore releasekey.keystore -alias releasekey -keyalg RSA -validity 10000

the process whent fine and I´m 100% sure I selected it while building

I also invented a package name that I believe is unique and doesnt contain special characters

extra info: I didnt use any debugging tool other from print statements

Can you upload a screen shot of your build screen?

Yes!

I coundnt figure out how to append an image here so I made this dropbox link:

https://www.dropbox.com/s/e0wyr9gvtczlfu4/screen.png

It looks like you’re doing things correctly. 

Rob

yeah, but I tried uploading it more than once and it always show the same message. Is it something to do with the daily builds?

luis,

I seem to remember Google changing something and people on older builds having issues.  You can try build 1212 which was the last G1.0 public build, or you can move to 2100 the current public build, but you may have to make some Graphics 2.0 adjustments.

Rob

UPDATE: I migrated to the newest version of corona (2013.2100) and it worked. I had to do all the changings regardind graphics 2.0.

note: my apk increased 2.5 mb in size, not cool

The answer is pretty straight forward.  You cannot use a debug keystore to upload to a store.  You need to create your own keystore that’s designed for release, build against it, then upload the app.

Please see: http://docs.coronalabs.com/guide/distribution/androidBuild/index.html

Rob

I believe I already done that. I created my key with this command:

keytool -genkey -v -keystore releasekey.keystore -alias releasekey -keyalg RSA -validity 10000

the process whent fine and I´m 100% sure I selected it while building

I also invented a package name that I believe is unique and doesnt contain special characters

extra info: I didnt use any debugging tool other from print statements

Can you upload a screen shot of your build screen?

Yes!

I coundnt figure out how to append an image here so I made this dropbox link:

https://www.dropbox.com/s/e0wyr9gvtczlfu4/screen.png

It looks like you’re doing things correctly. 

Rob

yeah, but I tried uploading it more than once and it always show the same message. Is it something to do with the daily builds?

luis,

I seem to remember Google changing something and people on older builds having issues.  You can try build 1212 which was the last G1.0 public build, or you can move to 2100 the current public build, but you may have to make some Graphics 2.0 adjustments.

Rob

UPDATE: I migrated to the newest version of corona (2013.2100) and it worked. I had to do all the changings regardind graphics 2.0.

note: my apk increased 2.5 mb in size, not cool