Hi, Most of our ANEs have a minimum version of 8 in the platform.xml. You can manually unzip and change the platform.xml file. The ANEs aren't encrypted so you shouldn't have any issues doing this as long as you take care when recreating the ANE zip package. Cheers ... View more

I doubt this will be possible without an ANE as you need a receiver to handle the broadcasted boot intent which then launches the AIR activity. This code needs to be implemented natively. Cheers ... View more

Have you tried debugging using ipa-debug rather than ipa-debug-interpreter as your iOS package target? ... View more

Hi, The Media Player issue hasn't been removed you just probably don't have access to the Media Player extension repository. This issue is a hard one to isolate as we haven't been able to replicate and seems to only happen in this app. @William I think you have isolated your issue to conditional compilation? There really shouldn't be much difference between a test flight release and a local development build apart from the normal production / development profile and info addition changes. If there are issues with TestFlight in-app purchases then the most common cause is related to the user logged in on the device. We suggest signing out of the AppStore on the device and making sure you are using a valid test user, installing it through test flight. ... View more

Hi, We are aware of the issue with the low minimum version and are currently updating all our ANEs. If any of the ANEs are blocking your development, please let us know by reporting an issue on github and we will make them a priority. Cheers ... View more

You can redirect your user to this url replacing the sku and package name to match your subscription and application: https://play.google.com/store/account/subscriptions?sku=your-sub-product-id&package=your-app-package or just the generic page: http://play.google.com/store/account/subscriptions For information here: Add subscription-specific features  |  Android Developers ... View more

Can you explain to us why you can't update the linker? At least for macOS? It's one of our most common support issues. ... View more

That looks good regarding the missing NSException error so nice work there! However I believe the linker is still out of date. I'm still getting: ld: unexpected token: !tapi-tbd-v3 file '/Users/marchbold/work/sdks/ios/iPhoneOS12.1.sdk/usr/lib/libc++.tbd' for architecture arm64 ld: unexpected token: !tapi-tbd-v3 file '/Users/marchbold/work/sdks/ios/iPhoneOS12.1.sdk/usr/lib/libc++.tbd' for architecture armv7 Compilation failed while executing : ld64 when attempting to link against the iOS 12.1 SDK, but if I update the linker, (ie. `cp /usr/bin/ld lib/aot/bin/ld64/ld64` or the one from Xcode) it succeeds.  ... View more

The error doesn't seem related to the library change from stdc++ to c++, but to a missing object type. As I mentioned in the starling forum: Using the AIR 32 beta causes: Undefined symbols for architecture arm64: "_OBJC_EHTYPE_$_NSException", referenced from: GCC_except_table0 in ... Attempting to link against the 12.1 iOS SDK causes (eg from here😞 ld: unexpected token: !tapi-tbd-v3 file '/Users/marchbold/work/sdks/ios/iPhoneOS12.1.sdk/usr/lib/libc++.tbd' for architecture arm64 ld: unexpected token: !tapi-tbd-v3 file '/Users/marchbold/work/sdks/ios/iPhoneOS12.1.sdk/usr/lib/libc++.tbd' for architecture armv7 Compilation failed while executing : ld64 Updating the linker alone, still causes: Undefined symbols for architecture arm64: "_OBJC_EHTYPE_$_NSException", referenced from: GCC_except_table0 in ... Then updating the linker AND using the 12.1 iOS SDK is successful. So I suspect the beta has an old linker and missing some of the iOS frameworks. I started replacing frameworks in the AIR SDK and found if I update the CoreFoundation.framework from the iOS 12.1 SDK (in addition to the linker) then the AIR SDK would start to work correctly again. I believe this is the framework that normally contains NSException so pretty good guess this is the issue? ... View more

The most common reason we've run into this error is when you are attempting to use a signed dynamic framework. In my discussions with the Adobe devs they are currently ignoring frameworks that are already signed and so the error above is produced. I haven't been able to get a reason for this but it seems to be an error from my perspective. Most frameworks provided from service providers are signed and you need to resign them when packaging in an application. Our method of getting around this has just been unpacking the IPA, signing those frameworks, and then repackaging. Eg this one is for the Branch framework Resign Script for Adobe AIR applications using the Branch ANE · GitHub Definitely agree Adobe need to resolve this as dynamic frameworks are becoming common place. I'll push the AIR devs I have been in contact with again to see if they have made any progress yet.           ... View more

zwetan_uk​ I found a copy, thanks. Definitely looks as though the format in the SharedObject is a variant on the AMF standard object encoding, but I've got it extracting what I need now. ... View more

zwetan_uk​ Gotten exactly that far already myself Though the padding in your "data" block is actually the AMF version, and will be 3 for newly created SharedObjects (AMF3). data |_ LSO name length: 2 byte short  readUnsignedShort |_ LSO name bytes: readUTFBytes |_ AMF version: readInt |_ data ... I was hoping to use the ByteArray.readObject function to read the AMF data block at the end, but it's not working, keeps throwing range errors. The data definitely is there, though looks slightly different from what I've read about AMF data, but not sure if I just don't understand the AMF data format. Have you got a copy of that cvlib? Doesn't seem to be on Google Code any more? Hoping I don't have to write an AMF parser as well. ASWC​ Isn't SQLite still stored in a file in the application storage? So the user can just as easily delete that as a shared object? Definitely agree that SharedObjects aren't the best solution for storage though. ... View more

Hmmm, no I have not. And that sounds like a great idea! Started writing a sol parser but going to try that as well. ... View more

Unfortunately we can't rely on that in this case. Our user's are irregular updaters and we have a critical issue I have to address. Definitely going to be even more hesitant on using SharedObject for mobile apps in the future. ... View more

Good idea, but that method would involve ensuring everyone updated through both versions right? Anyone who skipped one of the versions would lose data? Think I'm going to have to bite the bullet and write an as3 sol parser. ... View more

I realise this is quite an old post but just wanted to post in case this helps anyone. The most common reason I've found for this message is an error in the extension xml, with either the name of the nativeLibrary, the initializer or the finalizer being incorrect. Even a simple capitalisation error can cause this message. ... View more

Sorry but that's not really a solution as the @available flag can be used in a third party framework and setting the deployment target that high will reduce the number of devices we can support with native extensions. ... View more

Hi, That's not quite correct. @available was introduced with Xcode 9 but it still works on older versions of iOS. ... View more

Just an FYI for anyone attempting to get around this, we've added a few additions to the distriqt Core ANE that implements the required functionality to get the @available flag working. Simply by including the Core ANE in your application you should be able to use any ANE that uses the @available flag. It's available here: GitHub - distriqt/ANE-Core: ANE providing a centralised notification / delegation system ... View more

Seems odd that adding an ANE resolved the IOPS rejection. Are you sure your first attempt was with 122? Glad you've passed review either way! ... View more

Same thing happened to us, we had a build approved and released early this week and then an update yesterday with only minor changes triggered the location usage description errors. We just added them to our info additions and review passed, so definitely appears to be another Apple requirement change here. ... View more

Don't think you need to change anything regarding the naming of the icons in your application descriptor. The AIR processes you have followed in the past still work. The icons in the Assets.car will be used for iOS 11 + and the ones in the application descriptor for other cases (Android, iOS < 11 etc). ... View more

You can create the Assets.car with this online tool: http://applicationloader.net/appuploader/icontool.php​ I've put together a list of the other methods we use below if that helps: AIR Native Extension Tutorials by airnativeextensions ... View more