Don’t get me wrong. I LOVE FDT 5. I think it’s the best AS3 development IDE period. (The second best being intelijIDEA, if you must know.)
Especially with the new refactoring enhancements, improved mobile workflow, haxe support, build in Joa’s apparat / stripper / reducer abc optimisation tools and my two belowed magic shortcuts ctrl+1 and ctrl+shift+o that fix just everything you could wish for in the code. Having freshly upgraded from the version 4 Max to FDT 5 Max I was excited to try the new Air 3.2 gpu accelerated molehill capbilities on the iOS and android devices , perhaps revisit my Augmented Reality Demo so I can compare the performance now.
I have installed the latest official stable SDK from Adobe (4.6.0) and merged it with latest AIR 3.2 SDK from labs.
Made the simple hello world project, got all the appropriate certificates and provisioning profiles from our Apple Dev center, all the icons sizes, changed the app xml descriptor to say air 3.2 in the namespace, and hit the run button.
Instead of nicely compiled swf/ipa file I got this error message : An internal error occurred during “Compile”
Now, if this was an actionscript error, you could follow it up to stack, see where it originated, what caused it and hopefully know how to fix it. Unfortunately this is INTERNAL error of FDT threw in Java, so all I could try was to blindly try to change some settings, tweak some launch parameters. To no avail. Luckily after some time spent googling I was able to find this issue being added to FDT’s bug tracker. It was caused by using the SDK 4.6.0 ! And solution ? You can still use the latest sdk, just have to go to the SDK xml descriptor file and manually rename it’s version tag to 4.5.0.
Once I found the ‘solution’ for the SDK problem, I thought I was on my merry way to the land of mobile development. Unfortunately, that wasn’t the case.
Although swf now compiled fine, instead of getting ipa file, I got message : application descriptor not found
Although there clearly WAS an application descriptor file! To cut the long story short, there was again an entry for this in the bug tracker.
The issue is missing stringAttribute key=”ADL_DESCRIPTOR_FILE in the launch file. Once I added line
<stringAttribute key=”ADL_DESCRIPTOR_FILE” value=”bin/Air32Demo-app.xml”/>
to my .settings/launch/Air32Demo.launch file the ipa file has compiled correctly.
So at the end it all ended well. Right ?
Here’s my problem though..
Both of these problems were marked as “Solved” in the bugtracker. To me they are not solutions. These are “hacks” in the best case.
They’re both completely non transparent bugs, without any intuitive solutions. I think that for a $600 software, these ARE showstopper bugs, and should be dealt with immediately by releasing correction patch!