Search Issue Tracker
Fixed
Votes
0
Found in [Package]
Issue ID
1268172
Regression
Yes
[Android] "Unable to find lib_burst_0_0 and _burst_0_0" message logged when Burst is enabled
This does not have any effect on the actual Burst functionality, just an effort to load split libraries.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
IMPORTANT: the actual issue is the log entry; it doesn't affect burst functionality, burst still works as expected! The log print is also not present in release builds, only in development.
I'm resolving this as "fixed" but only 3/4 log lines were removed. (one line is still logged)
Unfortunately it's the way how plugin lookup works on Android - using Java load API and try to catch exceptions.
Unfortunately I can't change the way how plugin lookup/loading works on Android because it will likely break millions of projects, so this fix is the best I could do.