airsdk
Which AIR SDK version is most stable for now ?
i haven't published my apk for a while... I am working on window with animate (2023)
which AIR SDK is considered to be most stable for now ?
Thanks
As for me (Windows + Idea): IOS - AIR SDK 50.2.4.3 (only now I can build without errors, deploy and get approve from Apple) Android - still AIR SDK 33.1.1.935 (prefer use this stable version)
I agree that after each release you need to monitor issues and decide about use new version (separately for each platform Android, IOS, Windows). It is not convenient(
UPD... Oh... I see https://github.com/airsdk/Adobe-Runtime-Support/issues/3047 so may be I was in a hurry with IOS...
Android - still AIR SDK 33.1.1.935 (prefer use this stable version)
but this old version only supports target sdk 31. and google is demanding to upgrade to target sdk 33. so how do you handle this on the android version ?
I change target in descriptor, for my project there are no problems. I want to use AIR50 but what version is most stable for Android now?)
I have been interested by this thread to see what people think!
Our goal would be that for each milestone release (33.1.1, 50.2.3, 50.2.4 etc) the builds get progressively more mature as the build number increases. So there may be bugs introduced going from 50.2.3 to 50.2.4, but not between 50.2.4.1 and 50.2.4.2 etc.
In practice, this hasn't really worked out... there are still too many technical issues where we're having to change code to work around environmental issues or third party tools, which are presented as bugs but are actually resulting in changes that can cause regression. So we need to get a little better at this...
As mentioned, there are also the considerations where you need to have the correct support for the iPhoneOS or Android SDK and build tools in order to satisfy the Play/App Store requirements. We're trying to move away from having these as hard dependencies within the AIR SDK, so e.g. you could stick with a version of AIR SDK and just build this against newer iPhone/Android SDKs in order to create the appropriate APK/AAB files, without having any functional updates in the AIR runtime.
Answering the original question .. would it be tempting fate to say "the next one"? I am hopeful that all the major issues that have been reported with packaging/signing/etc will be fixed in this. There are still bugs aplenty I'm afraid but the key process for building and deploying should be better.
thanks
