Highlighted

osx ane x86_64 fails with error #3500: The extension context does not have a method for name

New Here ,
Mar 31, 2016

Copy link to clipboard

Copied

Hello,

I'm developing my ANE for osx, tried sdk 19r (i386), 20r and 21r, you know they only support x86_64. No results as expected:

- myAneExt.framework is built with success in El Capitan / xcode 7.3.
- it's actually a POC to test a single method, quite sureI'm ok with my code (both c/c++ or actionscript)
- Max number version in extensiondescriptor name is 20, weird that 21 return an error (invalid namespace), so I have to build .ANE against 19/20

- Tried with no luck the workaround as suggested here: http://blogs.adobe.com/flashplayer/2015/12/air-64-bit-on-mac-osx.html

Of course, i'll continue to check it's my issue, but I'm quite sure is not, afaik not much devs are actually applying to osx ane, but they deserve things works.

Please, don't let this post without relevant answer.

thanx in advance

Marco Fusetti aka Jaco

TOPICS
Development

Views

1.9K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

osx ane x86_64 fails with error #3500: The extension context does not have a method for name

New Here ,
Mar 31, 2016

Copy link to clipboard

Copied

Hello,

I'm developing my ANE for osx, tried sdk 19r (i386), 20r and 21r, you know they only support x86_64. No results as expected:

- myAneExt.framework is built with success in El Capitan / xcode 7.3.
- it's actually a POC to test a single method, quite sureI'm ok with my code (both c/c++ or actionscript)
- Max number version in extensiondescriptor name is 20, weird that 21 return an error (invalid namespace), so I have to build .ANE against 19/20

- Tried with no luck the workaround as suggested here: http://blogs.adobe.com/flashplayer/2015/12/air-64-bit-on-mac-osx.html

Of course, i'll continue to check it's my issue, but I'm quite sure is not, afaik not much devs are actually applying to osx ane, but they deserve things works.

Please, don't let this post without relevant answer.

thanx in advance

Marco Fusetti aka Jaco

TOPICS
Development

Views

1.9K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Mar 31, 2016 0
Adobe Employee ,
Mar 31, 2016

Copy link to clipboard

Copied

Hi Jaco ,

From your post I can infer that to test your POC, you want to create ANE both for AIR 19 and AIR 20.

With AIR 20 we are providing the  64 bit AIR for Mac. So you need to create 32 bit ANE for AIR 19 and 64 bit ANE for AIR 20.

I hope that you have tried out the link Error #3500: The extension context does not have a method with name xxx for AIR 20(If not please try that out).

Please let me know whether you are getting Error#3500 for AIR 20 only?

Are you able to launch the app using adl when you are using AIR 19 without any issue ?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 31, 2016 0
New Here ,
Apr 01, 2016

Copy link to clipboard

Copied

hi Nitanwar and thanx

I don't want to build my ane for 19 and 20, just need it works with the latest 21 (I've other projects for mobile and it seems it fix an issue with iOS simulator), of course I tried the link you suggested, no success. However if it's working, it degrades an already overcomplicated process (build/test/debug) crossing two IDEs and four main projects/steps (xcode, lib, ane_build automation, final consumer app)

I can actually compile also against 21 (I had wrong adt cmd line, now fixed).

I made it to work just in this case:

compile against 19, with right requirements (32bit arch, ext_descriptor blah blah), downgrading air runtime to 19, which is higly unsatisfactory result with additional [annoying] runtime upgrade dialog box

20 and 21actually don't works, neither from debug or packaging as release then install/launch

If I try to package for 19 and launch having the latest runtime (21), it complaints about "missing extension", due to the missing 32bit support, so I higly suspect that app+ane built < 20 and currently installed by users with will stop to work at all after runtime updgrade.

I think is a severe issue, please fix asap, currently the c/c++ runtime in osx is screwed up.

let me know if you need source code, but it has nothing special, you can try starting from scratch.

I'm using xcode, intellij on El Capitan

regards

Marco Fusetti aka Jaco

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 01, 2016 0
Adobe Employee ,
Apr 01, 2016

Copy link to clipboard

Copied

Thanks Jaco for verifying it on AIR 19 and you are right, app+ane built <20 will not work with AIR runtime 20 or above.

It will be very helpful if you can send us your project so that we can can debug the issue at our end .You can email the project at nitanwar[@]adobe.com

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 01, 2016 0
New Here ,
Apr 01, 2016

Copy link to clipboard

Copied

hi Nitanwar,

k, message with source code was just sent.

for those who want to get a look, it can be downloaded here:

anepoc_stuff.zip - Google Drive

aside note: extendedDesktop profile setting seems to not affect results

thanx

Marco Fusetti aka Jaco

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 01, 2016 0
New Here ,
Apr 01, 2016

Copy link to clipboard

Copied

I'm also running into this problem updating two existing ANEs to support x64. The ANE previously worked under AIR 15.

When built with AIR 20, I get Error #3500 the first time a function is called (though extension/context initialization appears to work).

I've tried the steps on the linked troubleshooting page, which just result in "Not supported native extension profile" from the adl command after extracting the first ANE with the problem into the folder MyApp/bin-debug/META-INF-AIR/extensions/com.adobe.extension

The command I'm running is:

${AIR_SDK}/bin/adl -runtime ${AIR_SDK}/runtimes/air/mac MyApp/bin-debug/MyApp-app.xml

I've also tried naming the folder with the actual ANE name instead of "com.adobe.extension" with the same result.

Both ANEs contain dependencies in the form of dylibs within the framework, so the structure looks like:

mimetype

catalog.xml

library.swf

META-INF/ANE/extension.xml

META-INF/ANE/MacOS-x86-64/myane.framework/myane -> Versions/Current/myane

META-INF/ANE/MacOS-x86-64/myane.framework/Resources -> Versions/Current/Resources

META-INF/ANE/MacOS-x86-64/myane.framework/Versions/A/_CodeSignature/CodeResources

META-INF/ANE/MacOS-x86-64/myane.framework/Versions/A/myane

META-INF/ANE/MacOS-x86-64/myane.framework/Versions/A/Resources/Info.plist

META-INF/ANE/MacOS-x86-64/myane.framework/Versions/A/Resources/lib/dependency.dylib

META-INF/ANE/MacOS-x86-64/myane.framework/Versions/Current -> A

META-INF/ANE/MacOS-x86-64/library.swf

META-INF/signatures.xml

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 01, 2016 0
Adobe Employee ,
Apr 01, 2016

Copy link to clipboard

Copied

HI Unsanctioned .

Just to verify, have you set  <supportedProfiles>extendedDesktop</supportedProfiles> in your app-xml?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 01, 2016 0
New Here ,
Apr 01, 2016

Copy link to clipboard

Copied

The <supportedProfiles> key was unset in our app XML per the comments Setting that at least does get the app starting from adl on the command-line, but that doesn't give any additional information on the error #3500, which still occurs both launched from the command-line and from FlashBuilder.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 01, 2016 0
New Here ,
Apr 13, 2016

Copy link to clipboard

Copied

I fixed the problem by removing Adobe AIR.framework from Build Phases > Link Binary With Libraries section in XCode. You only need to include Adobe AIR_64. Under Build Settings > Architectures choose Standard Architecture (64bit-Intel) (x86_64). The resulting library only supports 64bit platforms but that shouldn't be an issue according to this post. I am using FlashBuilder 4.7 with Flex 4.15.0 + AIR 21.0 SDK.

Screen Shot 2016-04-14 at 03.37.39.png

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 13, 2016 2
New Here ,
Apr 14, 2016

Copy link to clipboard

Copied

many thanx FlashJoe, I'll check asap and return my feebacks.

Marco Fusetti aka Jaco

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 14, 2016 0
New Here ,
Apr 15, 2016

Copy link to clipboard

Copied

Removing the linking to Adobe AIR.framework didn't help with my ANEs - they're still getting Error #3500. The same ANEs are working fine for Android, iOS, and Windows, and were working before I tried to update to 64-bit and AIR 20+.

As an aside: are we going to get an updated version of FlashBuilder at some point that doesn't requiring ignoring packaging errors on the 64-bit Mac ANEs? It'd be nice to know if there are *actual* errors.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 15, 2016 0
New Here ,
Apr 15, 2016

Copy link to clipboard

Copied

hi,

yet I had no time to try, but i'm actually building ANE without .framework included, mine resulting .ane p.o.c. is ~10kb.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 15, 2016 0
New Here ,
Apr 15, 2016

Copy link to clipboard

Copied

I created a very simple ANE that has a dylib dependency to reproduce the problem. I've packaged it up and sent it over for the team at Adobe to look at. Hopefully we hear something official soon.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 15, 2016 0
Community Beginner ,
Apr 28, 2016

Copy link to clipboard

Copied

I have the same problem.

I've spent several days trying to figure out why I get Error 3500 when running my ANE on OSX64.

I presumed I'd screwed up, but now I found this thread, I realize that the problem is the build process and that Adobe have admitted they have an issue

( Error #3500: The extension context does not have a method with name xxx  )

Unfortunately, I have the same problem with embedding external libraries into the ANE.

I need to link the LAME MP3 compression library, but its only available as a Framework (unless I compile the whole of LAME myself - which I've currently not been able to do).

At the moment my ANE is only 8k, which indicates its not linking the LAME framework inside the ANE ;-(

However I can't see any way to either get XCode or adt to embed the LAME framework inside the ANE.

I will need to park this ANE (on OSX) until Adobe have resolved this issue, otherwise its going to consume a huge amount of time  (and hence money) to get it to work with the existing  hacks.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 28, 2016 0
New Here ,
Apr 17, 2016

Copy link to clipboard

Copied

hi 2 all,

got working build  with the latest 22sdk 0.97, I've xcode build .framework against latest runtime and install as release.

My next attempts will be: downgrade air runtime to 21, try to get a working sdk with my IDE (intellij), flex 4.15 + air sdk 22b. Debug workflow is actually affected to error #3500 since is not the latest.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 17, 2016 0
Participant ,
Apr 19, 2016

Copy link to clipboard

Copied

I was fighting hard with it too.. this is working simple ANE GitHub - Oldes/ANEAmanitaOSX: MacOS Air Native Extension if it helps.

And here is more advanced working ANE for SteamWorks GitHub - Oldes/FRESteamWorks at AIR21_SteamWorks136 .

Important part is in 'other flags' in xcode project as is visible here: FRESteamWorks/project.pbxproj at AIR21_SteamWorks136 · Oldes/FRESteamWorks · GitHub

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 19, 2016 1
New Here ,
Apr 19, 2016

Copy link to clipboard

Copied

Thanks for this - comparing my settings against yours got my ANEs up and working.

Some notes:

- Don't have the dylibs in your "linked frameworks and libraries" setting

- dylibs need to be copied to the Executable directory instead of the Resources directory. For that you can add a custom "Copy Files" build step so you don't have to do so with an external script (like your build-mac.command).

- set the dylibs to weak_library in the build settings.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 19, 2016 0
New Here ,
May 06, 2016

Copy link to clipboard

Copied

So - this was working briefly. Today, for no apparent reason, it no longer is. I've unpacked the ANEs into bin-debug/META-INF/AIR/extensions again, but I'm back to error #3500 when debugging.

There doesn't seem to be any logic to it at this point. This is making maintaining existing Air applications nearly impossible.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 06, 2016 0
New Here ,
May 07, 2016

Copy link to clipboard

Copied

I think adding "-weak_framework Adobe\ AIR" is the key to the problem.  Adding it to the Xcode project target Other Linker Flags got my extension working again in AIR 20.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 07, 2016 0