Skip to main content
Participant
April 12, 2013
Question

When updating APK, Google Play tells the APK is not signed, but it is.

  • April 12, 2013
  • 1 reply
  • 6111 views

Hi.

When uploading a new updated APK for my AIR app, Google Play tells the APK is not signed.

I signed the APK with the same p12 file I used for the first version (successfully published and approved on Google Play).

I'm using Flash Builder 4.6 with AIR SDK 3.7. The first version of app was packaged with Flash Builder 4.6 and AIR SDK 3.4.

Then I tried to generate a new .p12 key, but I get the same error message while uploading.

This topic has been closed for replies.

1 reply

Adobe Employee
April 15, 2013

Hi,

Thanks for your issue report. However, we are not able to reproduce the issue yet. There is a bug which is already been logged at https://bugbase.adobe.com/index.cfm?event=bug&id=3541866 , kindly add your vote and any other information that you feel missing in the bug logged, this will help us to reproduce the issue.

And are you facing the same issue with fresh application also? Could you please try out a fresh HelloWorld application with new developer console? That would help us a lot, thank you.

-Nimit

Participant
April 15, 2013

Hi. Thank you. I replied to the bug and I confirm that using the old Google Play console I can upload my app.

Dr. Marco Marsala

Network Solution srl,Genova (Italy)

www.realizzazionesitigenova.it

Pahup
Adobe Employee
Adobe Employee
April 15, 2013

Would it be possible for you to just try uploading a fresh HelloWorld apk and see if that also shows up the same error? That'll help us isolate the problem.

Thanks

-Pahup