Dear Flex community and Flex engineering team, I have a challenge for you: let's make Flex 4 migration a one-step process.
(more...)
If you are using the same icon file in your app.xml file in AIR and embedding it to set it dynamically at runtime (for example if you have several icons that you switch between) then you'll most likely get the following error:
Error creating AIR file: YourApp-app.xml(94): error 303: Icon assets/icon.png is missing from the package.
(more...)
If you're storing information in the encrypted data store in your AIR app, you'll probably want to nuke that data on occasion while testing. You'll find the app-specific files for your application (on OS X) under:
~/Library/ApplicationSupport/Adobe/AIR/ELS/yourApplication
(more...)
Update: OK, so everyone's caught up on the EPIC FAIL title (hey, it got your attention!) so I've changed it — I retract my original statement: it's not an EPIC FAIL, heck, it's probably not even a FAIL. However, it's definitely a FOL, so let's move on to address the real issue here which is that it's in all of our interests to make Flex 3 to Flex 4 migration as easy as possible. As such, please read my follow-up post,
The Flex 4 One-Step Migration Challenge and let's try and make a list of the Flex 4 migration challenges for Flex 3 apps and try to address them.
Please also note what I mean by "migration" (from the comments):
(more...)