-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to load 'libmain.so', the application will terminate. #173
Comments
same problem. i tried on unity 2019.4.5f1 & 2019.3.5f1 and flutter 1.17.5 & 1.12.13 + hotfix.5 |
solved. make sure you have .so libraries. be attention when connecting aar to the project |
Where is the .so file supposed to be? |
compile app via unity and cut the .so from /libs |
where is it supposed to be kept? |
when building a project in a unity, the path is indicated where the apk will be located |
Let me try and get back to you, thanks for the help. |
Please can you explain better, am having same problem. Thanks. |
facing the same issue, could you please explain more about it |
i don't think this is related to .so files missing, cause I see them in the release apk-file for the correct architecture (arm64-v8a) |
@juicycleff any idea what could be the issue here? i analyzed the apk, it has all the libs |
@ToddBrawn are you trying to run the app in the android emulator, cause this wont work out of the box afaik the default one is based on x86, maybe try to install an arm based emulator in android studio |
Same problem : I tried to cut .so files from apk/lib/arm64-v8a and past into Myproject/android/unityLibrary/libs But this did not solve the problem Any Help, please? |
@subjectdenied Sorry for the delay, sidetracked with other work. Ok, I tried an arm based simulator, it is unusable on my MacBook Pro because of simulator performance. I sent it off to a friend that has an actual device and it appeared to work for him. Thanks! So, @waheed11 I suggest a real android device if you have one. I think that solved my immediate problem at least, but will be an issue for testing. |
Thank you @ToddBrawn , I tried with a real device , it works for a few seconds and then crashed. below the out log: |
Has this issue been solved for anyone yet? |
i think this is caused by the NDK version used when building the flutter app, as it seems that unity doesnt even support anything higher than NDK 19.x. however i didn't look into this really |
@waheed11 I have exactly the same issue as yours. The stacktrace that you posted above is same as mine. Did you find any solution for this? |
I have the a similar issue. Is there a solution? |
I have same issue to, anyone solution or advice ? |
Was this issue solved? |
Yes, if I do not remember wrong. I took the .so files from unity and replaced them with the ones in the project. |
Upgrading to Unity 2020.3.24f1 fixed this issue for me shrug |
I'm having this issue using Unity 2021.3.3f1.
|
First thing to try is to use the latest version of the package and the currently supported version of Unity (at the time of writing, Unity 2022.1.0 but check the readme). Also, be aware that building to the simulator isn't supported in case you are trying to do that. Can anyone who has this issue please report what kind of device you encounter the error on? Also, if you have a different device available, please try it and see if you get the same error. I suspect this may be a device-specific thing, and maybe we can narrow the problem down (iPhone or Android, what make and model) |
Try Unity 2020.3.24f1 |
I ended up finding out that if I enabled x86-64 in the player settings that it worked on the emulator as well as the physical device. |
This issue show when you try to run App with Flutter Unity Package on Virtual Device to run each project with this package you haven't use Physical device. If this trouble still exist pleas reopen issue or create new with template which be there. |
Getting this issue. Not using any AR features. The error is coming even if I build a Unity project with just one text element. Please help out!
The text was updated successfully, but these errors were encountered: