Skip to main content
Participant
September 15, 2013
Question

ANE fails at Extension Context

  • September 15, 2013
  • 2 replies
  • 1177 views

Since upgrading to Flex SDK 4.10 with AIR 3.8, my ANE no longer seems to function when published with my Android project.

I've downloaded and tried publishing the Vibration demo and Lee Brimelow's Notification ANE and, while they all build properly, fail at the same point:

When calling something like  context =  ExtensionContext.createExtensionContext("com.example.ane", null) all that is ever returned is null. There are no build errors and I know the ANE itself is working, because I can call other public functions in the Interface from the project. It doesn't matter if I call it on creation of the interface or create a listener for a click even to try creating it. It always returns null.

Upon searching, it seems like there are TONS of people having this issue as well, with no resolution. Is there anyone here who has tried to build even the simplest ANE on the latest SDK versions with any success? Is the warning I get on building the APK "The application has been pacakged with a shared runtime." relevant to this issue? Because it's the only thing out of the ordinary that's happening...

If I open up my ANE as a zip file, I can explore the java classes and it looks to me that everything is as it should be.

This topic has been closed for replies.

2 replies

Participant
May 22, 2014

Did you find any solution for this problem, if yes can you please share with me ?

Adobe Employee
September 16, 2013

Hi,

Could you please confirm the following:

-Whether you are publishing your app using IDE(Adobe Flash Builder) or command line?If using Command line,please share the command you are using?

-If you are including ANE in your project,please confirm whether ANE is getting included in the app or not?Verify the same by searching for extension tag in application.xml file.

-Is your application is getting published and working fine before upgrading to Flex 4.10 and AIR 3.8?

If possible,please provide the source code and steps you are using for publishing the app so that we can reproduce the issue at our end and investigate it.

Thanks,

Sakshi

Adobe AIR Team