SWC Build issues, InApp Billing changes, iOS Simulator
There is a lot of work in progress at the moment with some major changes coming up later this year, particularly for Android and the Google Play store.
AIR 188.8.131.529 was released with some changes to the way SWC's are packaged and this affected our ANEs. Several of our updates went out with this version and caused issues in certain circumstances with errors such as circular references or duplicate definitions.
We found that SWC's that relied on other SWC's also had runtime errors such as "ABC data is corrupt, attempt to read out of bounds".
We have updated the extensions we believe were affected but if you find any issues like this with any of our ANEs please let us know as we likely will need to rebuild them with a different AIR SDK.
Reminder: Starting on August 2, 2022, all new apps must use Billing Library version 4 or newer. By November 1, 2022, all updates to existing apps must use Billing Library version 4 or newer. Learn more.
Currently our extension uses version 3 of the billing library and we are in progress of a major update to bring it to the latest version 5 (released in May). This is requiring some restructuring of the calls (particularly as some of the previously synchronous calls are now asynchronous) which we are endeavouring to manage internally to the extension however we may have to introduce some API changes here.
We are hoping to have this ready for developers by the end of August, well before the November deadline for all applications.
We are working through further development on the
apm tool at the moment, mainly around cleaning up some of the processes. If you have been using the tool and have any suggestions as to improvements we would love to hear from you on the discussion forum.
We have recently let the iOS simulator implementations of some of our extensions slip and this month we have updated all our build processes to ensure the iOS simulator builds are kept inline with the main build.
Previously this was difficult when dynamic frameworks were involved but we have devised a new system to handle these and correctly include them in both the repository and the airpackage's for all our extensions.
These updates will roll out with the next release of our extensions, starting with the Facebook extensions in July. If there are any that you are concerned about let us know and we will get them updated immediately.
As always, if you have any native development needs for AIR, Unity, Flutter or Haxe, please feel free to contact us at email@example.com.