Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.3.X
Votes
9
Found in
2018.2.0f2
Issue ID
1059752
Regression
No
Burst files are not found when running android build
Reproduction steps:
1. Download user's project and open in Unity
2. Go to File -> Build Settings... -> Build
3. Install the built apk to a device
4. Start Logcat at the same time as running the apk on device
Expected: Burst package works fine
Actual: messages appear in logcat
Reproduced on: 2018.1.9f1; 2018.2.1f1
Reproduced with:
Google Pixel, Android: 8.1.0
Note:
messages:
"Unable to lookup library path for 'lib_burst_generated', native render plugin support disabled.
Unable to find lib_burst_generated
Unable to lookup library path for '_burst_generated', native render plugin support disabled.
Unable to find _burst_generated"
If you see only the first two messages, then you can safely ignore this error, it will be removed in an upcoming version.
If you are seeing all four messages then it indicates that burst is not being used (it will fall back to the non burst version)
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
MarcelArioli
Jun 29, 2020 10:31
i have a very similar issue in 2020.1.0b13 but with lib_burst_0_0 / _burst_0_0
neec12
Dec 30, 2018 01:18
i'm seeing also on 2018.3.0f2
Lee_Hammerton
Nov 22, 2018 08:45
the second sentence should have read :
"If you are seeing all four messages, then it indicates that burst is not being used (it will fall back to the non burst version), this was a bug, though it should not occur on the latest unity release."
Lee_Hammerton
Nov 22, 2018 08:42
If you see only the first two messages, then you can safely ignore this error, it will be removed in an upcoming version.
If you are seeing both messages then it indicates that burst is not being used (it will fall back to the non burst version), this was a bug, though it should not occur on latest unity release.
worldiscomplicated
Nov 21, 2018 16:49
I'm seeing this with 2018.3.0b11. Is this error message something to be concerned about, or can it be safely ignored? A comment here would help with debugging ECS because it would help avoid wasting time going down rabbit holes.