Skip to main content
O
OMA2k
Inspiring
May 24, 2012
Question

Adobe Flash Pro CS6 removes the native extensions section of my app descriptor

  • May 24, 2012
  • 2 replies
  • 1674 views

In CS5.5 I had some problems with native extensions, but that's ok, since CS5.5 was not ANE-aware (it was released before that).

But in CS6, it's even worse. It just deletes the whole <extensions>...</extensions> from my "xxx-app.xml" descriptor file each time I publish my SWF. Why?

It shouldn't do that! CS6 supposedly works with ANEs (it even has a special ANE icon in the "ActionScript settings" window, whereas CS5.5 didn't), so why is it removing my extensions from the descriptor?

This topic has been closed for replies.

2 replies

J
juvelez
Known Participant
May 31, 2012

Well, in CS6 you don't need to put manually the <extensions> tag on the descriptor, it easier now:

1. Edit the ActionScript Settings with wrench

2. Add the ANE in the library with the new ANE button

3. Close the ActionScript Settings

4. Open the Edit Application Settings, then close it

5. The <extensions> tag must be automatically added to the applicaction descriptor file for you

I hope it works for you

O
OMA2kAuthor
Inspiring
August 7, 2012

Sorry for my very late reply. Thanks for your tip, juvelez. I already had the ANEs added previously from my CS5.5 project, so CS6 wasn't aware of them, it seems. I've removed the ANEs and then readded them as you suggest and now it works. Thank you!

F
FLAdude
Inspiring
May 24, 2012

To the right under "Target: AIR for Android" or "Target:AIR for iOS", click the wrench and go to the "permissions" tab. Check "Manually manage permissions and manifest additions".

I know that helped when it was messing with my intent filters and other stuff I entered (Stuff inside the CDATA/manifestadditions).

Not sure if it helps with the <extensions> tag, but its not deleting mine...

You could also try putting <extensions> directly after </android>, thats where mine is. I suspect some entries have to be in a specific order.

O
OMA2kAuthor
Inspiring
May 24, 2012

Well, my extensions are for iOS, but anyway, I suppose that will do the trick. Thanks.

F
FLAdude
Inspiring
May 24, 2012

Well in the iphone version it is simply </iPhone> instead of </android>. Did it work?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices