When building APK and trying to launch I get this error. Same plugins if working with older engine version 2022 but not with 2023.
Any toughts?
Hi,
Testing Unity 2023.1.0f1 and FMOD 2.02.19 I was not able to reproduce the issue. What version of FMOD are you using?
Hi!
Been having the same/similar issue on a school VR Project here with roughly same version (Unity 2023.2.3f), where we can’t seem to build the game on the Meta Quest 2, and we get this error on the splash screen:
AndroidJavaException: java.lang.UnsatisfiedLinkError: dlopen failed: library “libfmod.so” not found
We’re using FMOD 2.02 as far as I know.
If this thread finds a solution, me and the other 30+ students I’m working with would be happy to hear about it 
Hi,
Could you confirm the minor version of the FMOD integration in Unity:
What operating system are you on?
If you use Unity 2022 do find the issues goes away?
Hi again - see the above image for minor version of FMOD in Unity we have, and as for operating system, I’m currently on Windows 11.
As for testing, I’ll try testing the game with the Unity 2022.3.17f1 version hopefully by tomorrow, and let you know how it goes
Hi!
I tried moving our branch of our project to version 2022.3.171f, however due to a substantial amount of compile errors from going back to an old version (and it would take a while to fix these changes), it would be difficult to go back to this older version - requiring a whole new set-up of VR controls and configuration.
However, we discovered a lot of files from FMOD has disappeared / been corrupted during Github transfers (standard pulling and pushes using Github Desktop), even though all assets were present, so we’re currently amending the issue by manually going through code and fixing errors.
…We’re still unsure about the issue(s) we’re running up against, but will update when we figure more out 
Hi,
Thank you for the information.
An option may be removing the FMOD integration from Unity and trying to reinstall it.
\UnityProject\Assets\Plugins\FMODPlease make a copy of the Unity project before deleting the integration to ensure you have a backup.
Hope this helps, if you have any more information please let me know.
HI,
I have the same problem.
Starting with Unity 2023, the default Application Entry Point for Android builds is GameActivity. In our project, when Activity is checked, it builds fine, but when GameActivity is checked, the same error occurs.
note:
Our project manages FMOD for Unity under Packages/ directory.
environments;
OS: WIndows 11
Unity: 2023.2.10f1
FMOD for Unity: 2.02.20
Target Platform: Android (Quest2)
stack trace (sentry);
Hi,
Thank you for the information, I have been able to reproduce the issue with GameActivity. I have passed this on to our development team to look into further.
Hello,
Is there a fix for this issue ? This is currently blocking us from upgrading to Unity 6 (6000.0.12f1) . We are using FMOD Unity Integration version 2.02.22 and developing for Meta Quest devices. The workaround mentioned above unfortunately is not applicable to us since Meta Quest applications require the Application Entry Point to be GameActivity.
Let me know if you need any other information, thank you.
Hi,
The fix for this was released in 2.02.23. Fixes and patch notes can be found here: FMOD Engine | Detailed Revision History.
Please let me know if you encounter any issues.
Thank you. I am not seeing a 2.02.23 for the Unity integration, so would just updating FMOD Studio and FMOD Engine to 2.02.23 fix the issue ?
Thank you, that was very helpful! Upgrading to Unity integration 2.02.23 fixed the issue.
