Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2018.2.2f1
Issue ID
1087347
Regression
No
LoadAssetAsync returns a prefab without components
Steps to reproduce:
1. Open user attached project
2. Build & Run on Android device
3. Observe the logcat and notice that an object behavior is outputted. Debug.LogError (prefab.GetComponent<Algorythm> ()); for example
4. Press the "back" button on your Android device
5. Notice that logcat outputs " The referenced script on this Behaviour (Game Object 'CubyCube') is missing!"
Expected result: LoadAssetAsync should return a prefab with components
Reproduced in: 2019.1.0a3, 2018.3.0b4, 2018.2.2f1, 2017.4.12f1, 2017.2.3p4
Reproduced with:
VLNQA00051, Xiaomi MI MAX (MI MAX), Android 6.0.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00134, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
N/A, Sony Xperia Z2 (D6503), Android 6.0.1, CPU: Snapdragon 801 MSM8974PRO-AB, GPU: Adreno (TM) 330
No repro with:
VLNQA00124, Google Pixel 2 XL (Pixel 2 XL), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Add comment