Adding Base64-encoded RSA public key to your binary for Submission to Google Play

I’m trying to submit a paid App to Google Play and it says I have to add a:

Base64-encoded RSA public key to include in your binary.

to be my License key for the application.

How do I go about doing this in Corona?

Thanks in advance.

Joe [import]uid: 94768 topic_id: 34667 reply_id: 334667[/import]

Have you set up a release keystore? Corona ships with a default “Debug” keystore. This is the apps encryption protection. You cannot release a “Debug” app to any of the Android stores. If you’re on windows:

http://wildlionsoftware.blogspot.com/2012/04/creating-android-keystore-for-corona.html

or follow this forum thread:

http://developer.coronalabs.com/forum/2011/04/16/signing-android-applications-3-easy-steps

If this isn’t want you’re talking about and you’re talking about Google’s new replacement for their deprecated DRM way of protecting your apps, I don’t think we can do that if you’re not an Enterprise customer yet.
[import]uid: 199310 topic_id: 34667 reply_id: 137783[/import]

Thanks for the reply Rob,

I think I am referring to Google’s new replacement. So they give me the public key but I have no Idea what to do with it within Corona. So it sounds like there is no way for me to protect my Corona Apps for the Google Play store.

This is what the Google Play licensing pages says:

SERVICES & APIS
LICENSING & IN-APP BILLING
Licensing allows you to prevent unauthorized distribution of your app. It can also be used to verify in-app billing purchases. Learn more about licensing.

YOUR LICENSE KEY FOR THIS APPLICATION
Base64-encoded RSA public key to include in your binary. Please remove any spaces.

[import]uid: 94768 topic_id: 34667 reply_id: 137836[/import]

Have you set up a release keystore? Corona ships with a default “Debug” keystore. This is the apps encryption protection. You cannot release a “Debug” app to any of the Android stores. If you’re on windows:

http://wildlionsoftware.blogspot.com/2012/04/creating-android-keystore-for-corona.html

or follow this forum thread:

http://developer.coronalabs.com/forum/2011/04/16/signing-android-applications-3-easy-steps

If this isn’t want you’re talking about and you’re talking about Google’s new replacement for their deprecated DRM way of protecting your apps, I don’t think we can do that if you’re not an Enterprise customer yet.
[import]uid: 199310 topic_id: 34667 reply_id: 137783[/import]

Thanks for the reply Rob,

I think I am referring to Google’s new replacement. So they give me the public key but I have no Idea what to do with it within Corona. So it sounds like there is no way for me to protect my Corona Apps for the Google Play store.

This is what the Google Play licensing pages says:

SERVICES & APIS
LICENSING & IN-APP BILLING
Licensing allows you to prevent unauthorized distribution of your app. It can also be used to verify in-app billing purchases. Learn more about licensing.

YOUR LICENSE KEY FOR THIS APPLICATION
Base64-encoded RSA public key to include in your binary. Please remove any spaces.

[import]uid: 94768 topic_id: 34667 reply_id: 137836[/import]

Same question here. How do we include the Google Play license key in our binary? They key is located under SERVICES & APIs (instructions say to include it in the binary - see below).

SAMPLE

Your license key for this application

[LONG LICENSE KEY]

Base64-encoded RSA public key to include in your binary. Please remove any spaces. [import]uid: 40033 topic_id: 34667 reply_id: 139064[/import]

As for Google’s new “copy protection system” that they refer to as their Licensing, that is currently not supported by Corona SDK and you should continue to use the DRM based protection. If you are an Enterprise subscriber then it’s pretty easy to use the new method. We are aware of the need but have other things we have to get done first.
[import]uid: 199310 topic_id: 34667 reply_id: 139082[/import]

Same question here. How do we include the Google Play license key in our binary? They key is located under SERVICES & APIs (instructions say to include it in the binary - see below).

SAMPLE

Your license key for this application

[LONG LICENSE KEY]

Base64-encoded RSA public key to include in your binary. Please remove any spaces. [import]uid: 40033 topic_id: 34667 reply_id: 139064[/import]

As for Google’s new “copy protection system” that they refer to as their Licensing, that is currently not supported by Corona SDK and you should continue to use the DRM based protection. If you are an Enterprise subscriber then it’s pretty easy to use the new method. We are aware of the need but have other things we have to get done first.
[import]uid: 199310 topic_id: 34667 reply_id: 139082[/import]

Hello what’s more important than publishing your app on the store? isn’t that what we paid for? I’d like to know when it will become available to corona subscribers to be able to use new google RSA license, as they say that you must include it for publishing an apk right? I’m right now trying to publish my apk but I don’t know if this is needed do you have an ETA for including this in the build process?

Thanks in advance! [import]uid: 105667 topic_id: 34667 reply_id: 140938[/import]

It is currently not required from what I’m being told.

[import]uid: 199310 topic_id: 34667 reply_id: 140983[/import]

Hello what’s more important than publishing your app on the store? isn’t that what we paid for? I’d like to know when it will become available to corona subscribers to be able to use new google RSA license, as they say that you must include it for publishing an apk right? I’m right now trying to publish my apk but I don’t know if this is needed do you have an ETA for including this in the build process?

Thanks in advance! [import]uid: 105667 topic_id: 34667 reply_id: 140938[/import]

It is currently not required from what I’m being told.

[import]uid: 199310 topic_id: 34667 reply_id: 140983[/import]

Any solution about this problem?.

When you create a new App in Developer Console, it says whether you have in you app in-app billing system, you need to to switch to the new design to get your license key. In my case, my app uses that service, and it is absolutely necessary for my app. Does anybody tried to create an app with the old system and use the inApp billing system?.

When is it going to work in Corona?

What about the patch CoronaSDK 2013.1025 :
Android: Modified store transaction callback to provide information needed to verify Google Play in-app purchases via the “event.transaction.receipt” and “event.transaction.signature” properties.

Is it related with this issue? I cannot find any information about it. Anybody can help me?

Thank you in advance.
[import]uid: 47279 topic_id: 34667 reply_id: 142476[/import]

Google is telling you this, but it’s still not required. You can still access the old form and chose DRM for your app’s protection.

That patch in 1025 is for a different bug.

[import]uid: 199310 topic_id: 34667 reply_id: 142559[/import]

Now I have a problem. I published the app on Google Play because it was ready to sell it. But nobody could buy by means of inApp service because of the new service.

I can’t delete an application which was previously published on Google Play. Even though you unpublished the app, you cannot delete it. Therefore, I can’t upload in the old user interface the app again because of it is still on the new user interface.

Any solution?. When are you going to make compatible corona SDK with the new licensing of Developer console?. I think it is a critical task.

Regards [import]uid: 47279 topic_id: 34667 reply_id: 142615[/import]

Any solution about this problem?.

When you create a new App in Developer Console, it says whether you have in you app in-app billing system, you need to to switch to the new design to get your license key. In my case, my app uses that service, and it is absolutely necessary for my app. Does anybody tried to create an app with the old system and use the inApp billing system?.

When is it going to work in Corona?

What about the patch CoronaSDK 2013.1025 :
Android: Modified store transaction callback to provide information needed to verify Google Play in-app purchases via the “event.transaction.receipt” and “event.transaction.signature” properties.

Is it related with this issue? I cannot find any information about it. Anybody can help me?

Thank you in advance.
[import]uid: 47279 topic_id: 34667 reply_id: 142476[/import]

Google is telling you this, but it’s still not required. You can still access the old form and chose DRM for your app’s protection.

That patch in 1025 is for a different bug.

[import]uid: 199310 topic_id: 34667 reply_id: 142559[/import]

Now I have a problem. I published the app on Google Play because it was ready to sell it. But nobody could buy by means of inApp service because of the new service.

I can’t delete an application which was previously published on Google Play. Even though you unpublished the app, you cannot delete it. Therefore, I can’t upload in the old user interface the app again because of it is still on the new user interface.

Any solution?. When are you going to make compatible corona SDK with the new licensing of Developer console?. I think it is a critical task.

Regards [import]uid: 47279 topic_id: 34667 reply_id: 142615[/import]