Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f3
Issue ID
1000584
Regression
No
Custom Editor causes "NullReferenceException" when entering Play mode for every Scene change
Reproduction steps:
1. Open "MinimalRepro.zip" project
2. Open "LoginDemoUGUI" scene
3. Select "Canvas" -> "WULoginPrefab"
4. In the "WP Server (Script)" components "Offline_url" field enter a WordPress website with at least 2 games*
5. Click "Refresh Games List"
6. In the "Select Game" drop-down, select "Demo Game"
7. Save scene and open "LoginDemoUGUI 1" scene
8. Go back to "LoginDemoUGUI" scene
9. Enter Play mode
10. See errors in the console
11. In the "Select Game" drop-down, select "Shadow Dragons: History"
12. Save scene and open "LoginDemoUGUI 1" scene
13. Go back to "LoginDemoUGUI" scene
14. Enter Play mode
15. See more errors in the console
Expected Result: No errors should appear / shouldn't increase the error count every time
Actual Result: "NullReferenceException: (null)" errors appear and increase in count with every loop of step 6-10
Reproduced with: 2018.2.0a1 (9dd3a0), 2018.1.0b7, 2017.3.1p1, 2017.2.1p4, 2017.1.3p1
Did not reproduce on: 5.6.5p2 (Required .NET 4.6, which was only implemented from 2017.1)
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
- Crash on CheckGameObjectsAndAddMissingRequiredComponents when opening a specific project
- Batch Mode and Cloud Build get stuck at 'Scanning for ADB Devices' when building for the Android or iOS platforms
- HDRP LightLateUpdate allocates every frame for each light in the scene when in Play Mode
- [IL2CPP] Custom attribute on delegate return value not present in IL2CPP builds
- Unexpected transformations occur when executing 2D Vertex Shaders
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.