Search Issue Tracker

Active

Fixed in 2018.3

Votes

10

Found in

2018.2.0f2

Issue ID

1059752

Regression

No

Burst files are not found when running android build

Themes

-

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)

Comments (4)

  1. 7e3a0b759aca30bd13d03851d00bec59?d=mm

    neec12

    Dec 30, 2018 01:18

    i'm seeing also on 2018.3.0f2

  2. Ad77602e9c7bc77fa965d886aab570f4?d=mm

    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."

  3. Ad77602e9c7bc77fa965d886aab570f4?d=mm

    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.

  4. 4afb5408b11fd0e816ed66538ffc9263?d=mm

    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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.