Scaffold application signing

To sign your application you may use standard Flair signing properties, but Flair add an easier way to sign your application with .p12 files.

---

Android and Desktop

From platform folders (src/android, src/desktop), you'll find a signing folder with files you need. These folders contain self-signed certificates which are valid for production. They are created when structure is generated, you'll find password from the generated password.txt file along with certificate file.

If you don't want to use the generated certificate files, you may create you own using a certificate task in your build.gradle file as following:

import flair.gradle.tasks.Certificate

task myCertificateTask( type: Certificate ) {

	//required properties
	cname = "name"
	output = file( "src/android/signing/myCertificate.p12" )
	password = "1234"
	
	//optional properties with their default value
	type = "2048-RSA"
	years = 30
	orgUnit = null
	orgName = null
	country = null
}

You may check Adobe documentation for signing options.

This task will be displayed under signing group in your gradle task listing, execute it to generate your own certificate.

---

WARNING

Don't forget to set your password in password.txt file since Flair read that file to sign application.

---

---

IOS

With iOS Flair can obviously not auto generate certificates, you'll find though dummy files under signing folder you'll need to replace. In addition you'll get 3 sub folders under signing folder:

• adhoc
• store
• development

These are used depending on your package target:

• package target ipa-ad-hoc will use signing from adhoc folder
• package target ipa-app-store will use signing from store folder
• any other target will use signing from development folder

---

---

WARNING

If you choose to set you signing using Flair signing properties, files under src/{platform}/signing will be ignored.

---