Closed PippoApps closed 8 months ago
I think this may just be terminology/mis-understanding ... there are two different things involved in building for Android: 1) the build tools 2) the Android target platform/API level
If you look under your Android SDK folder, you'll see:
1) build-tools
-> multiple folders, the highest one there is probably "32.0.0"; this is where we find things like apksigner and the older aapt/d8 compilation tools
2) platforms
-> at least "android-34" will be there I guess, but the actual target/compile SDK will be whatever our defaults are in the AIR SDK unless you override them with the XML descriptor manifest additions - which I see you have..
Those logs look fine btw.. You can probably open the resulting APK using Android Studio to check the values in there for target SDK, compile SDK etc. I would guess at them both being 34 though, based on this and what I get here..
thanks
@ajwfrost thank you for the explanation, it's all clear now.
I cannot find a way to set the correct SDK to compile for Android. Although I have android studio installed with only API 34 installed, it keeps saying that there are several build folders and compiles for 32. It maybe grabs it from the Unity installation folder.
I have setup the correct SDK folder in adt.cfg![image](https://github.com/airsdk/Adobe-Runtime-Support/assets/29799572/0903b143-9eeb-419e-a83c-c5b86a3b5cfa)
I have targeted the sdk version in manifest file:![image](https://github.com/airsdk/Adobe-Runtime-Support/assets/29799572/4278b9dc-1e9c-4d9a-b0fe-f48625d83592)
Is there a way to know which one of the "multiple build folders" is using?
Here is the log: