Type 1120: Access of undefined property JSON
If you’re using as3corelib like I’ve been using for quite some time now, you will notice this error. To fix it you simply need to remove the following import (it may vary based on your project structure):
and then you’ll need to modify your code to replace:
You can find the full details of the new implementation of the native JSON support in AS3 on Adobe’s Reference Site
Namespace 2.6 in the application descriptor file should be equal or higher than the minimum version 3.1 required by Flex SDK. Unknown AIR application.xml Problem
Easy fix, just change:
If you’re updating from a version earlier than 4.5, please reference this post about upgading to 4.5
If you’re trying to use an TextInput or field that should only be a numeric input, you can use the attribute:
you can also set it to:
I’m currently working on deploying an application to both Mac OS X and Windows users with a native installer. With such, I have discovered that you must build the native packages from within their respective OS’s. Oddly enough, it was difficult to find anywhere that said this for certain, so I figured I would put this out there for the other seven people that will come across this question. In my frustration with this inability I was complaining to a colleague that just so happened to work at Adobe before his current position. He noted that he knew some of the fellas over at Adobe that worked within the Air team and offered to send along my question/concern as to why this wasn’t possible and if there were any plans to find a solution. Turns out, the answer is no (for certain) and there are no plans for it in the future. Reason being, which is understandable and what I assumed to be, is that the packaging utilizes “underlying OS facilities for the target platform”. The full response was:
“The SDK doesn’t support cross-packaging of native installers because the
native installer creation code uses underlying OS facilities for the
target platform. For example, we use the Windows Installer libraries to
make the Windows installers; those libraries simply aren’t available on
Mac OS or Linux. There are no plans to address directly; it would be
expensive for us to re-implement and there are no plans to do so.”
I fully understand this and makes perfect sense. The Adobe Air platform has spoiled me so much with the simple ability to deploy to nearly any environment that I was surprised when I finally came across something they hadn’t accomplished ( yet? one can only hope ). I just wish they made it openly apparent that if you’re building a native installer that you must build each on the corresponding operating system.
I’m working on a basic framework that is intended to be used with Adobe Air 2.6+ (SDK 4.5+) allowing an easy way to build natively. I’m using SVN as the version control because they provide a version number which allows for a better overall version management. It’s also has a native updater with a AMF (PHP) and MySQL back-end so one can easily update the main app. It uses Ant from the command line and versions the application automatically (including the *-app.xml file). I hope to post it here soon.
So if you’re upgrading to Flex SDK 4.5 and Air 2.6 Adobe’s changing/moving things around again w/ the descriptor file (MyApp-app.xml). If you get this error:
Process terminated unexpectedly.
invalid application descriptor: versionNumber must have a non-empty value.
Launch command details: "/Applications/Adobe Flash Builder 4.5/sdks/4.5.0/bin/adl" -runtime "/Applications/Adobe Flash Builder 4.5/sdks/4.5.0/runtimes/air/mac"
All you need to do is replace this:
<version>0.1.0 Alpha 1</version>
<versionLabel>0.1.0 Alpha 1</versionLabel>
Also you may have an error prior to run:
Namespace 2.0.0 in the application descriptor file should be equal or higher than the minimum version 2.6.0 required by Flex SDK<.code>
Just change this:
Hope this helps someone.
So it’s been over a year since this hooligan has posted anything on the blog. The dh’s have been on bit of a hiatus, but are back in the swing of things. In the past year, there has been some learnin’ going on and some actual ‘experiments’ beginning. The biggest is ‘the Sodium Salt experiment’ which will incorporate ‘the Frisbee experiment’ (more details of the frisbee to come). The plan is to build out a framework based on a real-time system powered by Red5 (working title, dh:RTS) which will be integrated into, the soon to be open sourced, dh:Core (0.1). The dh:Core is a work-in-progress all around server sided framework designed to work on a LAMP environment supporting RIA apps and eventually mobile (iOS and Android). It’s built in PHP 5 and based on some existing popular frameworks and methods.
Anyways, I digress, the point of this post is to introduce the new Red5 magic happening on the dirty hooligans front with the SodiumSalt experiment. IM (with video capabilities), live webcasts/podcasts, music, movies, politics, sex, drugs and rock ‘n’ roll. The expected initial release into the wild is by end of year and extended features to follow shortly after.
As things progress I/we will post updates and findings regarding the different adventures. Most importantly, the plan is to open-source everything as they become stable and ‘clean’ (comments, docs, etc) so stay tuned my nerdtastic comrades.
Ok, so in searching for the best way to set up a development environment and such; I have found the greatest up-to-date (Red5 0.8) tutorials. Assuming you have Red5 installed somewhere to deploy or if you just want play around locally on your MacBook Pro, Mac Pro or any Intel based Mac OS X 10.5+, then I have waywardly and deliriously stumbled across the solution: TCP:1935′s Blog found HERE
I’m hoping to follow up some of this fine site’s tutorials with ‘side’ tutorials that will include MySQL usage, AIR, Flex, Flash and other interaction based coding.
Yup, that’s right. Amazing, brilliant and unbeatable. Available for Mac and Windows. 14 day free trial, $35 new, $17 upgrade get it HERE