I think I stumbled upon a bug in Flash Builder 4.6. I'm running FB on OSX 10.7 and I'm building native extension for OSX (AIR 3.1).

After successfull creation of my extension's native code .framework file in Xcode, writing Action Script wrapper around it and packaging everything together in ANE file (using adt) I discovered that I couldn't start a debug session from Flash Builder (4.6 and AIR 3.1). Since I was able to test my extension from terminal (using adl), I am pretty sure that I connected all the dots correctly.

I discovered that Flash Builder only before starting debug session unpacks the extension's .ane file into some temporary folder, beneath the workspace. Unfortunately, it messes the attributes of unpacked files so aliases are missing (they look like regular files) and main binary inside OSX's .framework package is missing executable attribute. Since those aliases and attributes are essential for things to work on OSX, FB simply fails to find extension and reports error like "ArgumentError: Error #3500: The extension context does not have a method with the name". Somebody else stumbled upon this in following post http://forums.adobe.com/message/3974973 (it seems it's specific to Linux and OSX, but not Windows - no aliasing there, huh?).

I would appreciate if somebody from Adobe could check that and verify if that's up to Flash Builder or not.

I don't decompress manually the ane file for extract the correct symlinks, but replace the wrong file with the same from the framework folder make by xcode

Launching the debugger from flex and replace (before call any ane code) the symlinks allow to debug without any more problems.

I'm developing a little function that fix the framework symlinks to call when the app start (maybe using the conditional compilation so this code is use only in debugger mode and not in final release). The problem is that flex don't allow to create a symlink and for this function I need to call an external process (like a bash script)...

I ran into this problem as well. One interesting thing that I discovered is that if you create a Flex Mobile project and add a iPhoine-ARM/MacOS-x86 dual platform extension everything works just fine. The problem appears to be isolated to AIR desktop apps.

There's another problem with the symlinks to watch out for. I built the framework then copied the directory over to the directory where I would build the ane from. I knew that by doing this the symlink files would still be pointing to the folders and files of the original framework folder that I copied, so I deleted the copied symlink files and remade them in Finder. Turns out that making these symlink files in Finder caused the files to not work. So instead of copying the framework folder I dragged it to where I would build the ane. I believe another way to do this would be to create the symlink files in terminal, though I haven't tried this. Hope this helps.

It seems I also have this problem, but I am not sure whether I can fix it with this. Where and how do I compile your code? Does it have to be in the final flash as3 code of the app that I try to make? Or is it a separate piece of coding? Or do I need to include this when exporting the library? I hope it still works anyhow, we are over a year later and both Xcode, Flash, Flash Builder and AIR have been updated several times ever since, so I am curious if somebody can help me here.