Search Issue Tracker
By Design
Votes
0
Found in
4.5.5f1
Issue ID
650866
Regression
No
[WSA] losing references inside prefabs
Related forum thread:
http://forum.unity3d.com/threads/possible-bug-losing-references-inside-prefabs-in-windows-store-apps.214952/
Reproducible on 4.5, 4.6 and 5.0 versions;
Repro steps:
1. open project "prefab references.zip". Also, Unity package is available in the mentioned forum thread;
2. build to WSA;
3. build and run generated VS solution;
4. Press "W" key, texture appears;
5. Now press "Enter" key two times (scenes switches);
6. Press "W" key, texture doesn't appear (null reference);
Repeat 4-6 steps to observe the behavior. Every second load of the first scene, texture loads normally;
---
This is by design. Windows Store and Windows Phone apps must keep references to MonoBehaviours and ScriptableObjects directly. To catch this error pass -enableWarningsIncorrectlyUnloadedAssets command line option (works on WSA but not WP8). Then you'll get a list of objects you need to fix.
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
- New animation clips are not imported correctly when re-importing a fbx file
- [PackMan] Extension in bottom bar disappears when using operations between UI generation and packman extension callbacks
- Editor freezes when recompiling scrips in Play Mode
- Shuriken particles depth offset is not working(has no affect) when 'Renderer Alignment' is set to 'View'
- [InputSystem] InputSystem is not initialized when run in `-batchmode`
Maus3rSR
Oct 23, 2018 08:07
Hello,
I have a similar issue on v 2018.3.0b5 but here is about through Unity Collab.
I have a prefab gameobject containing a script with references to others prefab (prefab child derived from a base prefab)
Any time I send modifications on the project, my partner always loose references of the child prefabs in the script. (NullReference Exception)
daisuke.suzuki
Jun 29, 2016 01:37
Didn't repro on 5.3.4p1.
I hit similar issue on 5.3.4p1 so I tried the repro to check if my issue is this one or not. Seems my issue is different one.