Search Issue Tracker
Fixed in 2017.2.0f3
Votes
1
Found in
2017.1.0p2
Issue ID
938878
Regression
No
NullReferenceException with Unity Remote Settings
Reproduction steps:
1. Open "UnityRemoteSettingsTest.zip" project
2. "Window" -> "Unity Analytics" -> "Remote Settings"
3. Pin the "Remote Settings" window next to the "Inspector" window (like in "sc1.png")
4. Insert the Projects Secret Key -> "Next"
5. Select the "Inspector" window
6. Exit Unity
7. Open the project again
8. Enter Play mode
Expected Result: Play mode should start without any errors
Actual Result: "NullReferenceException ...RemoteSettings/RemoteSettingsManager.cs:339)" is thrown (like in "sc2.png")
Fixed in "Unity Analytics Remote Settings" version: 0.1.6
Reproduced with: 2017.3.0a3, 2017.2.0b7, 2017.1.0p3, 5.6.3f1, 5.5.4p2
Note:
Reproduced both with Mac OS 10.12.5 and Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment