2

I am using FDT 5 and trying to use IOS native extensions. I am pulling my hair out because every time I try running the application locally I get the following error: "Not supported native extensions profile"

So I've tried scouring the web to find solutions and I've tried the following and these are the results:

  • Renaming the ANE file to a SWC file and including it to the class path. Results: Nothing, same error

  • Tried adding extendedDesktop. Results: Error changes to "invalid profile specified 'Application does not support current profile'"

  • Tried manually adding the ane file to the class path. Results: Nothing

"Not supported native extensions profile" is the error that I just can't get around. Again, this is when I test locally in FDT (not on the device)

K2xL
  • 9,730
  • 18
  • 64
  • 101
  • Sounds like an issue with FDT then because adding the native profile should have done it. My advice if you want to go native, uninstall FDT, download eclipse CDT and start writing real native apps in C++. :) –  Jan 01 '12 at 17:12
  • I just posted to your question on Adobe forums ;). I think you may just be doing something incorrect regarding ANE and not an FDT issue. Is the 'extendedDesktop' function available in mobile and are you experiencing the issue when running the app within the ADL? Where does this error happen? At runtime or compile time? – Alan Klement Jan 02 '12 at 15:54
  • @AlanKlement Error happens at compile time. I haven't tried running the app in the ADL yet. Not sure about your question about extendedDesktop. – K2xL Jan 02 '12 at 18:52
  • I've used mobile ANE for with FDT but I'm not an expert ( who is? ). All FDT is doing is passin the arguments to the compiler - no magic there. Do you have any other info which could help? – Alan Klement Jan 02 '12 at 19:50
  • @AlanKlement are you on windows? could you by chance post a quick screencast of how you do it? it would be immensely helpful – K2xL Jan 02 '12 at 22:17
  • 1
    I'm out of time today to help more, (I'll be back tomorrow), but check out these ANE examples by Patrick Kulling. He created them with FDT https://github.com/patrickkulling/Air-Mobile-Extensions – Alan Klement Jan 04 '12 at 20:02
  • Still having issues? Have you tried Philipp's solution (below)? – Alan Klement Jan 17 '12 at 15:42

2 Answers2

3

You need to change the namespace of your application discriptor to match your Air SDK:

<application xmlns="http://ns.adobe.com/air/application/3.1">
Philipp Arnolds
  • 76
  • 1
2

In your application descriptor file, remove "desktop" from the list of supported profiles.

For instance, change

<supportedProfiles>desktop extendedDesktop mobileDevice</supportedProfiles>

to

<supportedProfiles>extendedDesktop mobileDevice</supportedProfiles>

This will alleviate the "Not supported native extensions profile" error.

Chuck Batson
  • 2,165
  • 1
  • 17
  • 15
  • Unfortunately it also disables Updater.isSupported when running on the desktop. It would be nice if there was another way to ignore the native extensions without losing this feature or modifying the app.xml with every compile. – Patrick Dec 05 '18 at 22:20