Open FliplineStudios opened 9 months ago
Ah, there are two different things at play here:
It would probably make sense to keep these in sync! particularly given the build machine update should mean that the stub files we generate are based on those newer SDKs. Although if you then build on a mac, with the -platformsdk
option, it would ignore those and just pick up whatever SDK you had installed at the time....
So it's a bit of a mixture of values. Agree though, we should do some better coordination of these, and likely we'll be switching to just using the Apple SDK which would mean as long as we keep our build machines up to date, the generated IPAs should identify a little better too...
thanks
Hmm I did try building with -platformsdk pointing to the 17.2 SDK from Xcode, but it's showing the same older values for that version too -- should those be changing when I use the platformsdk flag? I'm assuming I set the path correctly, with this at the end of the adt -package call...
-platformsdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS17.2.sdk
The release notes for AIR SDK 50.2.4.3 mention switching to Xcode 15.2 and iPhone SDK Version 17.2 for builds.
When packaging an iOS app, the Info.plist is still showing the information for Xcode 15.0.1 and iPhoneOS 17.0 from the earlier 50.2.4.1 SDK:
DTXcode 1501 DTXcodeBuild 15A507 DTPlatformBuild 21A326 DTPlatformVersion 17.0 DTSDKName iphoneos17.0
The same older 15.0.1 information is shown when packaged on either Windows (LLVM) or MacOS (ld64)