We are officially allowing all Air Native Extensions providers/developers to use our Common Dependency ANEs free of any charge so the Air community won’t see that scary Air Native Extension conflict error message any more!
dx tool failed:
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.IllegalArgumentException: already added: blah, blah, blah...
Using ANEs in Air projects is fun and gives you a whole new window to access native APIs on Android and iOS but it’s been always a headache when seeing that scary conflicting error message.
Here at MyFlashLabs Team, we have been able to fix this problem within our own ANEs for a long time now. Introducing the Common Dependency ANEs has been proven to be an effective way to bypass the Air Native Extension conflict problem.
If you are using ANEs from our den, you will never see that error message when compiling your Air project because we have used the Common Dependency ANEs in all our ANEs with grace. But what if you are using ANEs from different ANE developers/providers?
At the moment, ANE developers are each using their own methods to embed shared libraries into ANEs without paying attention to the possible trouble they may have cause to the users. If you are using ANEs, it’s very probable that you have faced this error message already and you know how annoying that is. You need to contact both sides of the ANE developers and ask them for a solution but there is no real answer to this problem because the conflict problem is not their fault! The situation can easily get very messy because you can’t compile your project and you need both ANEs in your project.
We are finally providing an ultimate solution to this problem so you would never again see that annoying Air Native Extension conflict error message. We have highly optimized the Common Dependency ANEs and have made sure that they can be easily adopted by all ANE developers/providers.
In this post, we are officially inviting all Air Native Extension developers/providers to freely use any of our Common Dependency ANEs in their projects even the commercial ones. This will not only help end Air devs not to face that conflicting error message but also will help ANE developers save a lot of time.
We are doing this contribution to the Adobe Air community with joy and love hopping that this would help Air devs build cool Air apps/game faster and easier.
Enjoy building Adobe Air apps.