For reasons that I cannot explain, RemoteConfig is throwing an error INSIDE of the RemoteConfig code:
NullReferenceException: Object reference not set to an instance of an object
Unity.RemoteConfig.Editor.RemoteConfigWindow.OnDisable () (at Library/PackageCache/com.unity.remote-config@1.0.9/Editor/RemoteConfigWindow.cs:112)
The only way to resolve this was to undock the RemoteConfigWindow from the Unity environment and reopen it and re-dock it.
Not sure why it is happening so I’m not sure how to reproduce that.
One thing I can saw that went weird was that I created a new environment called “Testing” in the cloud environment. I had created another “Production” that I had deleted.
Can you share the code that you are using? Does this happen when you run your game in the Editor? And can you elaborate on ‘went weird’, did you get the same error when you created an environment?
From a UX perspective, mentally those breadcrumbs just beg to be clicked because that’s the way they are everywhere else. That’s not a defect, but definitely a UX improvement that would be welcome.
I’m still getting that NullReferenceException. Not sure what’s causing that, but assuming that it’s somehow related to this as that would be the only thing different from my situation and the demos that I see online.
Please show your code that is returning the NullReferenceException, I didn’t see it in the video. Apologies if I missed it. Is this in the Unity Editor when you run your game, or on the online Remote Config Dashboard? Please attach a screenshot of the NRE
I understand now that you are looking at crash reports, I was trying to understand where you were seeing the NRE, perhaps in the Console window. You mentioned docking and undocking the RC dialog in the Editor is what creates this error, can you avoid it for now by keeping it docked? This would be in editor code only, and would not affect game play.
Yep. Absolutely. It’s more just reporting a defect than something that is causing debilitating problems (outside of the Environment purgatory since there is no way to delete them in either the editor or the dashboard ).
Hi @gregorypierce ,
We are sorry you are experiencing issues when deleting environments via dashboard.
Dashboard team is working to resolve that issue.
I see you are using editor package version 1.0.9 where there is no way to delete an environment.
At that point in time, two environments (Development and Release) were automatically created for you on the backend.
However, from the version 1.1.0 and above, we introduced CRUD for environments in the editor,
so, you can delete an environment by:
Click on Edit button next to environment dropdown
Click Delete (delete button will be enabled only if that environment is not default)
So in your case, at this point the only way to delete an environment is to upgrade your package version, and remove unwanted environment(s) from the editor (see attachments)
It could be that you got in this awkward state because you somehow deleted ‘Production’ environment which was created for you in 1.0.9 by default, so if you can upgrade the package version, and delete unwanted environment(s), we would like to know if that would alleviate your issue. By deleting environment you will lose your corresponding config. Once again, we are very sorry for the confusion that happened.