distriqt has a free solution for this if you don't want to make your own GitHub - distriqt/ANE-CustomResources: Android Custom Resources for AIR Applications ... View more

So far this seems to be working, actually we didn't have to repackage all of our ANEs, after copying ld and libclang it seems to work. I guess we might repackage the rest of them to be on the safe side. Now we can move forward with iOS 12 features - Thanks! ... View more

Check this thread Android 8.0 adaptive icons support ... View more

someone in the starling forums is reporting an even easier way: Adaptive icons for Android « Starling Forum ... View more

I definitely was over-reacting especially when I decided to rant at the undeserving person who actually created this thread 😕 Having said that, XCode 10 is most definitely not in beta, and the main thing that I was reacting to was that Adobe has been completely silent about everything AIR-related for months. I don't think it's too much to ask that somebody just tell us *something* even if it's not 100% definitive. And they did, so that satisfies my main gripe with them. Not here, but in the ticket tracker. Hello Everyone, We are looking into this issue and will be updating this ticket once we are done. Regards, Rohit Comment by Rohit Kumar Guglani FWIW react-native also isn't up-to-date with XCode 10's new build system, but in that case it's possible to tell XCode to use the legacy build system, and who knows, maybe that's all we need AIR to do, so we can avoid the practice of relying on legacy versions of standard build tools that are no longer supported and must be downloaded separately. *diminishing into the west* ... View more

Fair enough, sorry for the rant. In any case, we're stuck, we need this and would like to know the roadmap so we can actually know which features we can and cannot implement. ... View more

el111​, that was a totally different situation, because when the iOS 11 platform SDK was released it was possible to package using the existing AIR SDK by specifying the iOS 11 platform SDK in the -platformsdk parameter - see the topic of this post. We actually released to the appstore with iOS 11 feature support in October 2017. Right now we can't package the app at all with iOS 12 platform SDK. We're not asking for specific iOS 12 feature support in AIR - simply the ability to package our AIR app using current platform tools, so we can implement that feature support ourselves. "I don't set -platformSDK and it works fine. You only have to set -platformSDK if using ANEs that are compiled with that version." So, you don't need iOS 12 feature support, you don't need to use iOS 12 functionality in ANEs, and therefore the problem described in the topic of this post isn't a problem for you. That's nice for you, but again it's inherently off-topic for this thread. You're not actually saying the problem doesn't exist, but that we shouldn't care about it since you don't! If Adobe plans to release a beta in November and a release version in December supporting iOS 12 platform SDK, it would be ever so helpful of them to let us know that's what they're planning on. Whenever they did whatever they did last year is not a reliable gauge of when or if they're going to do this in 2018. ... View more

Can someone from Adobe please respond to this and let us know if this is going to happen or not, and if it is, roughly when? There are multiple issues caused by this that have varying degrees of severity and time sensitivity: - It's not possible to test apps in the iOS simulator in XCode 10, including the not-yet-released iphone XR - It's not possible to integrate new, iOS 12-only features using ANEs, such as Siri Shortcuts - Starting March 2019, submissions to the appstore of apps not built against iOS 12 platform SDK will be rejected. There is an issue in the tracker here Tracker ... View more

You can upgrade to Xcode 10 if you need to for other things, but you will need a copy of Xcode 9 to package with AIR. Can someone from Adobe please confirm, either here or in the tracker ticket for this, that you are aware of this issue and working on it? ... View more

There's some activity on the Gamua thread mentioned above, you might want to monitor that: https://github.com/Gamua/Adobe-Runtime-Support/issues/29#issuecomment-388067899 I agree it's a little strange to not see much communication from Adobe here on their own forum, but it appears they are indeed trying to solve the issue. ... View more

instructions here: Create app icons with Image Asset Studio  |  Android Developers you can just create a fake Android Studio project and copy the directories/files it creates. ... View more

For anyone who's wondering, this turns out to be not that hard - you can import your foreground and background in Android Studio, rename "ic_launcher" to "icon" wherever it appears as the default name,  and then include the files in the res/ folder it produces as android resources - if you're using ANEs, you can package the resources in one of them (if not I guess you can use aapt and resign the apk) and they'll show up in Android 8. ... View more

This bug has been logged already for months, 17 votes woohoo https://tracker.adobe.com/#/view/AIR-4198557 Tracker ... View more

It looks like this might be a deadlock in sound playback code? Developers are reporting success using ANEs to play all sounds on Android to get rid of the ANRs: https://github.com/Gamua/Adobe-Runtime-Support/issues/29#issuecomment-390884726 ... View more

The tracker link you posted is about the original issue with private APIs, this is different. If I had to guess, I'd say Apple is just getting pickier about code included in the exe that's referencing APIs like this, even if that code is never called. As far as privacy issues, Adobe couldn't be sneakily looking at location info because if they did, either users would see a popup asking for the permission, or if the permission string didn't exist the app would crash. Just in case, the permission string we included assures users that clicking "Don't allow" is fine and that our app doesn't use or ask for these permissions, but they're unlikely to ever see it. ... View more

No, I was talking about the location permission string. Apple accepted our latest build, but we had to add the location permission strings described above. Since we're not doing anything that's going to ask for this, and don't see these popups ever in testing, it's not a big deal given the ask-as-you-go permissions model to just add them to satisfy Apple (for the moment anyway). ... View more

This could be an Apple thing too - we submitted a build with the new v29 sdk and it got approved, then another that didn't because of this. Nothing changed between the two builds that would have affected anything to do with location permissions. Since it's impossible to submit builds with any other version of the SDK now, it's hard to really verify if this is about an SDK change, appstore review policy change or both, but it must be at least in part due to appstore review policy. ... View more

It looks like you guys released this on the main download site, this means we can consider this production-ready? https://www.adobe.com/devnet/air/air-sdk-download.html ... View more

They are being inconsistent about this. We had a submission approved yesterday - after apparently some here had already been rejected for this - but we had to submit an update because of a problem with a language xml file. Today we were rejected for this, and now we're stuck. So it's not anything we're doing, any functions we're calling or not calling, or any ANEs we're including. It's clear that this is an AIR SDK issue that Apple has decided to reject apps for, which they didn't before and maybe aren't consistent about doing even now. ... View more

If you are using the -platformsdk compiler flag with a value like: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk and the app is exiting when it goes to background, try a value like this instead for the -platformsdk flag: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.2.sdk If you are not defining this flag then this probably doesn't apply to your situation ... View more

For now it appears that you do need to do this step in XCode unless there is some other way to make an Assets.car file. Since you are using Animate CC maybe you can get some help in this thread: iOS 11 Application has blank icon with Air 28 ... View more

Did you follow the instructions for the new way of packaging icons with AIR SDK v28 using the Assets.car file? For the screen resolutions it sounds like an issue with splash images. We had previously been using <key>UILaunchImageFile</key> in the iOS portion of the app xml, and we had to comment that out and name them all starting with "Default" which solved a similar issue for us. ... View more

Tracker <= this bug on the tracker ... View more

We've run into this issue too and it's a pain because this is starting to appear in 3rd party library code. Have you made a bug report? if so I'll vote on it. ... View more

Tried AIR 28 today, looks promising.. Tracker This, or something similar, has meant we've been stuck using AIR 22 since AIR 23 came out; we use a preloader with a main SWF which would throw errors starting with AIR 23, but it seems to work again now. It would be a really big deal for us if we can finally be up to date, and it would simplify our build process a bit since it's handling the newly required way of packaging icons so we wouldn't have to. The rendering of anything using cacheAsBitmap is messed up, but you mention that as a known issue, so we'll be checking for a fix for that. Anyway, awesome! ... View more

Do they have iPhone X devices available? ... View more