It would certainly help to have multi-dex supported, since developers reach the 64K limit quickly when including various Google Play Services libraries, social and other commonly used services. In the end, the developers are forced to cut down on the amount of features provided in their app.
I've pinged our development team to get their input. Thank you for adding the feature request. To be clear, when you got the error with 72530 references, was that because your code went over or did you pick up a new AIR SDK and found a regression in functionality?
We use a lot of ANEs. Moreover we support developing open-source ANEs for all developers. You can find it here marpies · GitHub
This is a list of current using extensions.
When we've included one more ANE we've got an error during package process:
Too many field references: 72530; max is 65536.
You may try using --multi-dex option.
Hope Adobe Team will add Multidex support in upcoming release.
Thank you for voting. Adobe has changed status of Feature#4190396 - Multidex support for Adobe AIR to ToTest.
I'll be glad if somebody else add a comment and vote for a feature.
Abhishek.Jain As I know you've developed some ANE. I think you can help us and add additional info to the feature request.
Thank you for looking into this issue.
I'd like to clarify status of feature request Feature#4190396 - Multidex support for Adobe AIR
Status: ToTest means that a developer has fixed it but the Quality team has not yet tested the fix.
I can help with testing if you need. As I said before we use a lot ANEs so it'd be easy for us to test it.
Reason: NeedMoreInfo means that the product team is unable to reproduce the problem as described or there may be more information required. If a bug has been set to this reason, please see the notes to see what is needed by Adobe and provide the additional information if possible.
Two days ago I added a note with a list of current using extensions. If you need additional info I'll add it as soon as possible.
You are almost right in understanding the workflow. Let me help you with the process we follow.
Whenever a bug is logged by developer/user in bugbase it goes to Unverified state. The number of user issues which we receive on daily basis is pretty huge. We scan all the issues reported and then we mark Bugs in ToTest/NeedMoreInfo state whenever that particular bug requires attention. Our team then tries to reproduce the issue and communicates with user if required. After successfully reproducing the issue we then clone it to an internal bug on which we work. Now, even after logging internal bug it might be possible that the priority of that issue is low. Now, that priority is being decided on the basis of the Votes external bug has and number of users reporting it. Votes play a very important role. We always try to make our users happy and keep on working bugs reported by them. We always communicate to our users once we have something concrete for them. We are working on your issue but we can't commit on timelines by when it will get fixed.
Hope this helps.
Adobe AIR Team
Do you have any news about this issue? Feature Request has about 50 votes.