Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.13f1
Issue ID
1099052
Regression
No
[Android] Spurious "Unable to find libaudioplugingvrunity" error in `adb logcat` output
Steps to reproduce:
1. Open user attached project
2. Build & Run to an Android device
3. Check the logcat and observe the "Unable to find libaudioplugingvrunity" error
Expected result: "Unable to find libaudioplugingvrunity" should not be outputted in the logcat
Reproduced in: 2019.1.0a11, 2018.3.0b12, 2018.2.18f1, 2017.4.16f1, 2017.3.2f1
Tested devices:
VLNQA00096, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
N/A, Sony Xperia Z2, Android 8.1.0, CPU: Snapdragon 801 MSM8974PRO-AB, GPU: Adreno (TM) 330
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2019.1.X):
This pathway has been deprecated from Unity.