theboywhocriedWoolf | Tal Woolf

AIR 3.3 Simulator Support for FDT 5.5

4

With USB Debugging using Custom FDT Templates

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.
New Project Selection

Project selection options

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

Project compilation options

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.

Download the Air iOS Template for FDT5.5 or Spoon me on GitHub.

Discussion

  1. Greg M

    Tal, I downloaded and ran the runInstall.app and I’m getting a dialog window saying “Users:greg:Library:application support:FDT:projectTemplates:AIR wasn’t found.” The folder does in fact exist, but I noticed the error path has the “Application Support” folder name all in lower case.

    I assume your script does more than just copy the iOS AIR3 folder to the projectTemplates folder, because when I tried manually copying it and restarting FDT, the template icon in the New FDT Project/AIR menu is displayed as an error.

    Anything you can do to help?

    Thanks…

    • boycriedwoolf

      In Fact you are right, all the runinstall.app does is unzip the folder in the correct location. Make sure you are using FDT5.5 if not download my previous version. Try downloading the files again as I have updated the description.xml file which should solve your problem. Then extract the “iOS AIR3″ folder and place it in Users/greg/Library/application support/FDT/projectTemplates/AIR/”**”iOS AIR3″**.. let me know if you have any further problems. Thanks

      • Greg M

        Thanks a lot! Works like a charm now. All I had to do was make some path changes to my ios.properties file, edit a few lines in the sim build ANT scripts, and add in my application assets and I was good to go.

        One thing I changed in the two sim build scripts was the the path to the iPhone Simulator. The simulatorSdk was being appended to the user home directory, which was not the proper location in my setup. I simply took out the ${user.home} variable, and put the full path of the simulatorSdk in the properties file.

        One other thing that was throwing me off was the “check-SWF-exists” target. At the end of the antcall lines in the if/then block, the deploy.swf was being deleted. That action was causing the build to fail. I commented that line out and it seemed to fix the issue.

        Lastly, I added in my asset files and directories in the adt package command and it was all downhill from there.

        Again, thanks. Great set of tools that will definitely save me some time until (hopefully) the next version of FDT makes life a little easier…

  2. Alan

    Tal,

    Thanks for this blog post and FDT support. I missed this on Twitter and I wish I had caught it earlier.

    Consider sending me a DM (Twitter) or even an email: admin.fdt (the at symbol) powerflasher dotcom

Leave a Reply to Greg M / Cancel Reply

(* Required)