Copy link to clipboard
Copied
I am using Flash Builder 4.7 to package my first app for the Google Play store. I export my release build, choose to package with a captive runtime, but my concern is with the certificate. I choose to create one within Flash Builder, so it essentially a self-signed certificate. Is this how most people do it, is this an acceptable or standard solution, or is there a more professional way that looks more legitimate to a final user that most of you use?
Thanks for any insight.
Copy link to clipboard
Copied
Hi,
You can use a self signed certificate for exporting the apk.
Thanks!
Pravishti | Adobe AIR Engineering
Copy link to clipboard
Copied
Thanks Pravishti!
Copy link to clipboard
Copied
Couple of other things, in case you see an option for these, you need to use 2048 bit not 1024, and you need to make the certificate last at least 25 years.
Copy link to clipboard
Copied
Thanks for the info Colin. I don't know if self-signing using Flash Builder gives you the opportunity to make it last for 25 years, but I will look into it.
Copy link to clipboard
Copied
I followed the steps in this Adobe doc, above halfway down the page is a "Signing apps for Android" section that explains the requirements and shows how to generate a certificate on the command line using adt:
Signing Adobe AIR applications | Adobe Developer Connection
Looks like it also has Flash Builder instructions if you don't want to use the command line. I used the adt method myself and have been using that same self-signed cert for years with no problems.