As some of you may have noticed, there’s a bug in Xcode V7.0 or higher regarding
-hideAneLibSymbols option that effected AIR SDK V20 too and causes some ANEs to get conflicted when used in a project. This is true about any kind of ANEs as far as some of their IOS side methods have the same exact name.
Only when you are starting a new project with our latest ANEs or if you are updating it to be compiled with AIR SDK 20 or greater, then this bug appears (on iOS side only) when trying to use some ANEs together in a single project.
Our urgent update for all of our ANEs and our Club members
As soon as we have noticed this bug in Xcode V7.0 and AIR SDK 20, we contacted Adobe and also posted on their forums so that they would fix this issue for the next SDK release. But this would take time and we had to wait until the next SDK version release, What we don’t have is time to wait and we’re sure the same thing is true about you too 🙂 So we decided not to wait! And instead we updated our ANEs to bypass this bug. So everything is up-to-date now and all our ANEs would work perfectly together just like before although this bug do exists in the current version of AIR SDK, it no longer cause any problem on any of our ANEs.
So what is the conclusion?
If you’re starting a new project or updating a previous project of yours and now compiling it with AIR SDK 20, please login to your panel on our website and download the latest version of the ANE that you have purchased or download the latest Club package if you’re a club member and use the updated ANEs in your project, that’s it! You’re good to go.
FAQ
What about my old projects that has been compiled via the previous versions of AIR SDK?
Nothing! You just don’t need to do anything, as the older versions will perfectly work with the old version of the ANEs or the new version of the ANEs, it doesn’t matter.
What happens when a newer version of AIR SDK gets released and the bug has been fixed inside of it?
Again no worries! Our fix in the current version of our ANEs will still work for the AIR SDK V20 or higher versions.
How about the Common Dependencies ANE? Is there an update for it too?
No, it’s not. You don’t have to touch that ANE in your project.
Urgent fix on our ANEs required for AIR SDK V20 or higher
As some of you may have noticed, there’s a bug in Xcode V7.0 or higher regarding -hideAneLibSymbols option that effected AIR SDK V20 too and causes some ANEs to get conflicted when used in a project. This is true about any kind of ANEs as far as some of their IOS side methods have the same exact name.
You can read more about the bug here:
https://forums.adobe.com/thread/2055508
https://forums.adobe.com/message/8294948#8294948
In what projects this bug appears?
Only when you are starting a new project with our latest ANEs or if you are updating it to be compiled with AIR SDK 20 or greater, then this bug appears (on iOS side only) when trying to use some ANEs together in a single project.
Our urgent update for all of our ANEs and our Club members
As soon as we have noticed this bug in Xcode V7.0 and AIR SDK 20, we contacted Adobe and also posted on their forums so that they would fix this issue for the next SDK release. But this would take time and we had to wait until the next SDK version release, What we don’t have is time to wait and we’re sure the same thing is true about you too 🙂 So we decided not to wait! And instead we updated our ANEs to bypass this bug. So everything is up-to-date now and all our ANEs would work perfectly together just like before although this bug do exists in the current version of AIR SDK, it no longer cause any problem on any of our ANEs.
So what is the conclusion?
If you’re starting a new project or updating a previous project of yours and now compiling it with AIR SDK 20, please login to your panel on our website and download the latest version of the ANE that you have purchased or download the latest Club package if you’re a club member and use the updated ANEs in your project, that’s it! You’re good to go.
FAQ
What about my old projects that has been compiled via the previous versions of AIR SDK?
Nothing! You just don’t need to do anything, as the older versions will perfectly work with the old version of the ANEs or the new version of the ANEs, it doesn’t matter.
What happens when a newer version of AIR SDK gets released and the bug has been fixed inside of it?
Again no worries! Our fix in the current version of our ANEs will still work for the AIR SDK V20 or higher versions.
How about the Common Dependencies ANE? Is there an update for it too?
No, it’s not. You don’t have to touch that ANE in your project.
Share this:
Related