Bug Failed to load libmain.so

1. I did "File > Build Settings..." in Unity and exported an Android project.
2. I loaded it to Android Studio.
3. I had to uncomment the following in both build.gradle (for launcher and unityLibrary) because it wouldn't build:

Code (CSharp):

1. ndk {
2. //            abiFilters 'armeabi-v7a', 'arm64-v8a'
3. }

4. Now it builds and opens but immediately I get this from Unity and it closes:


I want to include Unity as a library to my native Android App but is it possible to test it in Windows 11?

 

1. Does this mean I absolutely have to test all Unity exports on a real device connected to Android Studio if I want to use "Unity as a library"?

2. Would it work on Macbook (which is arm64)?

3. I enabled x86 and x86_64 in Player Settings and it works in Android Studio now. Thanks!

After this change Unity modified build.gradle to include these additional options:

Code (CSharp):

1. ndk {
2.             abiFilters 'armeabi-v7a', 'arm64-v8a', 'x86', 'x86_64'
3. }
4.  
5. packagingOptions {
6.     doNotStrip '*/armeabi-v7a/*.so'
7.     doNotStrip '*/arm64-v8a/*.so'
8.     doNotStrip '*/x86/*.so'
9.     doNotStrip '*/x86_64/*.so'
10. }
11.  

 

Thanks, but I think this may be actually a bug: Android Studio claims that it's possible to run Android apps on Windows 11 in Android Studio.

They explicitly say that "x86_64" emulator includes support for x86, x86_64, ARMv7 and ARM64 ABIs.

Source: https://developer.android.com/studi...rm_binaries_on_android_9_and_11_system_images

So, it seems that Unity could (and should) make it work (in Windows 11 emulators from Android Studio)?

Testing mobile phones, tables, foldables etc. is only possible via Android Studio emulators, so don't you think this is an important feature for Unity to have? (Unity's emulators are not as good as AS emulators, so no workarounds are available.)

Yes, I'm referring to installing Android Studio on Macbook and using their emulator (which would be ARM64). Ok, never mind, I'll test it myself.