Core.init() error in AIR SDK 51.1.3.12

[everseen83]

When calling Core.init(), the following error occurs. (adl from VSCode)

This issue occurs with AIR SDK 51.1.3.12, but not with 51.1.3.10.

Error: The native extension context could not be created
	at com.distriqt.extension.core::Core()
	at com.distriqt.extension.core::Core$/createInstance()
	at com.distriqt.extension.core::Core$/init()

This issue is not specific to Core.init() - it also occurs with other ANE extensions
(InAppBilling.isSupported, GameServices.isSupported...)

I haven't modified anything other than changing the AIR SDK version. The ANEs in our project need to be updated. I would really appreciate your help with this.☺️

Environment

• AIR SDK version: 51.1.3.12
• Development IDE: VS Code
• Development OS: Mac OS
• Core ane Version: 7.6.0

[marchbold]

Hi,

I'd suggest you firstly make sure you have the latest of all our extensions. Also ensure that you are correctly packaging the extension with your application build.

Then if the error still occurs simply from changing the AIR SDK then I'd guess you've found an issue in the AIR SDK and would be best to create an issue on the AIR repo, (though I haven't had any other reports of this so I'd check the other items first).

[everseen83]

Thanks for the reply.
I’ve updated all ANEs to their latest versions, but the issue still persists.
The APK/AAB builds succeed without any problem, and the extensions work fine on actual Android devices.

The error only happens when launching the app with ADL for desktop debugging.
Replacing the /bin/adl file from AIR SDK 51.1.3.10 into 51.1.3.12 didn’t solve it — the same error still occurs.
The same behavior is observed on both Apple Silicon and Intel macOS machines.

Additional finding: only some ANEs fail under ADL (51.1.3.12).

• Failing: Core, InAppBilling, GameServices
• Not failing: Adverts, Firebase, Notification
  For example, Adverts.isSupported returns false cleanly on desktop, but GameServices.isSupported throws The native extension context could not be created.

If there’s any possible cause or known change in the AIR SDK or ADL that could affect this behavior,
please let me know.

I’ll also be reporting this on the AIR SDK repository for further investigation.

[marchbold]

Ah that sounds like the extensions that have macOS implementations. I'll have a look into it.

[marchbold]

Can you show me the adl command that is failing?

It seems to be working for me with adl and in intellij, correctly calling the native implementation.

I don't have a vscode project setup for any of these extensions yet but will do that next. My guess is that the process you are using isn't extracting the content from the ane's correctly and placing it in the extdir for adl.

[everseen83]

Sorry for the late reply.

In VSCode, I’m not launching ADL by manually entering the command line.
Instead, I’m using the built-in run/debug menu provided by the vscode-as3mxml extension,
which internally invokes ADL via asconfigc.

At the moment, I’ve added a simple guard around the problematic code path to continue development:

  if (AppSettings.isMacOS || !GameServices.isSupported)
       return;

With this in place, the issue doesn’t block progress for now, since the affected functionality
is not required on desktop.