FDT 5.5’s recent release has dramatically changed the way that FDT now compiles AIR applications. They have added in a plethora of options and tick boxes, to amuse and bewilder you for many an hour, all with the hope to speed up your development process and make it easier for you to package your AIR applications.
Unfortunately, the introduction of these innovations has also meant that the Custom Project Template I previously made is no longer useful and has no place in FDT’s new compilation environment. Until now that is…
There must be another way..
After a few days of blood sweat and tears, well mostly tears, and some back and forth discussions with the FDT bug reporting team, which I have to say were very helpful and responsive, I finally managed to recreate my Custom Project Template for the FDT 5.5 environment.
In this post I will predominantly cover the different compilation steps you must follow within FDTv5.5. Therefore if you would like to read up on more detailed instructions and information on how the Template actually works please refer to my previous post AIR 3.3 Simulator support.
Lets start the Party
Once you have installed the Template and selected the create a New FDT Project selection you will notice that the selection panel now offers you different template options to those available in FDT 4.6.
Instead of Web, Mobile and Desktop, you now have AIR, Web and FDT Plugin. Select AIR and you should see the “iOS AIR3” Custom Project Template as an option. Fill in the required fields making sure you populate the Certificate Password as this is the only location, other than that of the ANT properties file, that you’ll be able to amend later on. If you are unsure of what these options are for please refer to my previous post.
Your project is now created but before you crack open the champagne and tuck into your cake there are a few extra steps which need to take place before you are truly up and running.
If you look in your Debug Configurations you’ll notice there are some compilation options already available for you under the “FDT AIR Application”. These are:
1) Remote Debug on Device
2) Test on Simulator
3) Wireless Debug on Device
4) Wireless Debug on Simulator
If you then select one of the compilation options you’ll see all the configuration options available to use, just as in FDT 4.6, with the only difference being “configure project properties”. ”. In order to successfully compile your application you MUST select this option and populate your Developer Certificate, Provisioning Profile and Certificate Password under the “Digital Signature”
tab. Yes, that’s right; unfortunately you must fill in your Certificate Password again. FDT now encrypts the password and does not provide a way for Custom Project Templates to access this variable therefore in order to have access to it at this point (compilation), the variable also had to be populated at project creation.
Don’t blame the chef
FDT 5.5’s new compilation environment still has a few quirks with the way its launcher chain handles multiple launch configurations, I did raise this issue and was informed we should see this fixed in FDT 5.6.
So until then you may experience a few compilation problems from time to time. If this happens double check all your paths are correct and that you have correctly populated all the required compilation fields. As usual if you have any issues ping me back and ill make sure ill answer as soon as possible.