Forum Discussion
Unable to upload to AppLab. Error This APK contains libInteractionSdk.so and targets Android SDK 31
I am trying to upload a build to AppLab and getting error "This APK contains libInteractionSdk.so and targets Android SDK 31. This is currently unsupported; please set the target Android SDK to 29 or 30, or remove the Interaction SDK and try again."
I am using Unity 2022.2.6f1 and Oculus Integration v50 (also tried with v49 with same error).
Anyone else having the same issue with Unity 2022.2?
Will try an earlier version of Unity but can't find out which Unity versions that uses Android SDK 29 or 30.
6 Replies
I have the same problem with Unity 2021.3.22f1
Downgraded Unity version to 2022.1.24f1 and did a build. Upload to AppLab worked without any issues.
Will now try with Unity 2022.2.6f1 again but adding Android SDK 29 and setting maximum Android SDK target to 29.
Guide for adding Android SDK versions: https://www.youtube.com/watch?v=fP1moOOWhrY
Adding Android SDK 29 to Unity 2022.2.6f1 and changing Target API Level to Android 10.0 (API Level 29) is the first steps. Unity 2022.2.x has problems with "android:installLocation" in AndroidManifest. (https://forum.unity.com/threads/install-location-in-player-settings-not-working-in-unity-2022-2-2.1389366/)
Solution here: https://gist.github.com/vpfrimmer/49f9eb68db937c37cfea4de8afdab2df
Now it works to publish from Unity 2022.2.6f1 to AppLab.
I am also having this issue. Using a lower API level as suggested only seems to be a temporary solution though. There is a news article from Meta that apps will be required to use API 31 starting in june so if its a new game being released on app lab we wont be able to use 29 if releasing after the new cutoff. Though anything existing will continue to work in that lower level. I'm trying to find another solution considering my game is new and will be released around them, im almost wondering if I need to completely remove the interaction folder from my project. might try that and report back
https://developer.oculus.com/blog/meta-quest-apps-android-12l-june-30/
TriplePete to follow up from my previous message, I deleted the entire interaction folder in my unity project and rebuilt the project using api 31. In the Meta Quest Developer Hub I was able to upload my .apk and obb file to the developer dashboard so its cleared out the error from your initial message. The thing is though if you are actually using the interaction sdk in any form than this wont be a viable solution considering the entirety of metas interaction sdk is deleted. But if you are using a different VR interaction framework like VRIF or the other frameworks available in the unity asset store than it shouldnt be an issue
Yes, I did think that would work. My issue though is that I am using the Interaction SDK and for now using Android 29 works. But as you mentioned we need to make it work with Android 31 before June.
