Search Issue Tracker
Fixed in 1.0.10-preview.1
Votes
1
Found in [Package]
2019.3
2020.1
2020.1.0b1
2020.2
Issue ID
1225451
Regression
Yes
[RemoteConfig] Null Reference Exceptions are thrown when Remote Config window is closed without assigning a project id
If a project hasn't been connected to Unity cloud services and remote config window is closed after opening, null reference exceptions are thrown in console. Refer the attached video
Steps to repro:
1) Create a new project
2) Window > Package manager > Install Remote Config
3) Window > Remote Config
4) Close the Remote Config window
Actual result: Null Reference Exceptions are thrown in the console when Remote Config window is closed
Occurring on Unity version: 2020.2.0a2, 2020.1.0b1, 2019.3.4f1, 2019.2.11f1
Occurring on RemoteConfig Package version: 1.0.9, 1.0.8
Working fine on RemoteConfig Package version: 1.0.6
Environment: Both Windows and Mac
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
- Standalone profiler process is hidden in macOS dock
- Shader warnings are being thrown after building Mixed Reality Template
- Error is thrown when entering play mode with build profiles docked and standalone profiler open
- The Player hangs when activating another maximized application
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
Resolution Note (fix version 1.0.10-preview.1):
Determined to be a minor Edge Case of incomplete implementation of the onboarding steps, user can complete the integration or remove the package without issue.