Play Store Error- You uploaded a debuggable APK error

Solar2D Android
#1

I just built an apk using build 2012.971 and when I uploadad the APK to google play store I get the error 
 

 

Upload failedYou uploaded a debuggable APK. For security reasons you need to disable debugging before it can be published in Google Play. Learn more about debuggable APKs.Upload another APK  

 

On reading other forum topics, some had mentioned that updating Corona had solved the issue, but unfortunately I cannot do that. I NEED to use .971.

Why is the APK built as debugging APK?

 

#2

P.S I am not using the debug key.
I am using a signed key, which has given me no problems till now.

#3

On extracting the Manifest file from the apk, I see
 

android:debuggable="true"  

Why on Earth is this set?

#4

Google changed something before 1212 that causes this error.  I don’t know what that is in the manifest.  The solution from engineering is to build 1212 or later. 

Rob

#5

@Rob 
No other way?  I really don’t want to waste time porting from 971 to 1212.

I mean widget 2.0 , for a start, was released in the mean time, and probably a host of other changes would need to be made. 

Will it be OK if I just set android:debuggable =“false”  and rebuilt the APK with apktool ?

#6

If widgets are your concern, download the legacy widget library from github (https://github.com/coronalabs/widget-v1)

Drop the file into your project and do:

local widgets = require(“widgets-v1”).

We don’t support using apktool, but if it works for you, go for it.

Rob

#7

Ah well… I guess I’ll just port.

Will this be fixed anytime in the future, or is this the end of Pre-1212 builds?

#8

We don’t have the ability to patch older builds.  Newer builds are the builds with the patches.  Google, Apple and the other stores and 3rd parties are constantly making changes that we have to react to. 

#9

Er… I just went to the daily builds page and there is no 1212 build. 
Will any later build do?

Can you please tell me which is the earliest public release build after 1212(There seems to be no info regarding if a build is a public one or not in the builds page)?
I’ll just use that to be on the safer side. 

#10

You can find 1212 on the downloads page.  There is a link to “archive of public releases” or something like that.

Rob

#11

Ah yes. found the archive of public released : https://developer.coronalabs.com/downloads/archive

Apparently 1202 was the public release, not 1212.  
I take it then that you meant 1202 build when you said "Google changed something before 1212 that causes this error.  I don’t know what that is in the manifest.  The solution from engineering is to build 1212 or later. "

If not, there is no 1212 build (http://i.imgur.com/TSwIcCu.png)

#12

Sorry, I meant 1202.

Rob

#13

P.S I am not using the debug key.
I am using a signed key, which has given me no problems till now.

#14

On extracting the Manifest file from the apk, I see
 

android:debuggable="true"  

Why on Earth is this set?

#15

Google changed something before 1212 that causes this error.  I don’t know what that is in the manifest.  The solution from engineering is to build 1212 or later. 

Rob

#16

@Rob 
No other way?  I really don’t want to waste time porting from 971 to 1212.

I mean widget 2.0 , for a start, was released in the mean time, and probably a host of other changes would need to be made. 

Will it be OK if I just set android:debuggable =“false”  and rebuilt the APK with apktool ?

#17

If widgets are your concern, download the legacy widget library from github (https://github.com/coronalabs/widget-v1)

Drop the file into your project and do:

local widgets = require(“widgets-v1”).

We don’t support using apktool, but if it works for you, go for it.

Rob

#18

Ah well… I guess I’ll just port.

Will this be fixed anytime in the future, or is this the end of Pre-1212 builds?

#19

We don’t have the ability to patch older builds.  Newer builds are the builds with the patches.  Google, Apple and the other stores and 3rd parties are constantly making changes that we have to react to. 

#20

Er… I just went to the daily builds page and there is no 1212 build. 
Will any later build do?

Can you please tell me which is the earliest public release build after 1212(There seems to be no info regarding if a build is a public one or not in the builds page)?
I’ll just use that to be on the safer side.