I don’t know if I have done something stupid, but my project doesn’t have a development environment… This would be otherwise fine, but I need to test some stuff privately and I can’t use any other environment than that to test it in the editor. I cannot make a new development environment since it doesn’t allow me to make one.
Something weird I found was that my Unity Editor is currently just downloading the config from the default environment set in the dashboard.
I’m not clear what you are showing in the screenshot. Please show your Remote Config Editor settings from the Unity editor. Ensure you are using Remote Config and not Remote Settings.
We’re experiencing this too but assumed it was by (unfortunate) design.
In 2.x versions, development is a reserved environment name and has been documented as such but it seems unreasonable that the built-in development environment cannot be accessed at all.
If I’m reading the documentation right, downgrading to version 1.0 would provide legacy access to the development environment and this would persist even if upgrading back to 2.x versions?
Might be worth a try but this also seems like an unnecessary hoop to jump through.
We are using the newest version of Remote Config (2.0.1). What I meant to confirm is that toggling the Development Build button in build settings does not automatically toggle to any specific Remote Config environment in versions past 1.0.
If so, I don’t understand why accessing the (apparently always existing) Development environment requires downgrading to 1.0.x before upgrading back to 2.0.1 again.
Is there any way to access the Development environment without downgrading?
Can I link another environment to the “Development Build” button in the Build settings?
Hi @Damast , with newer package versions >1.0.x Remote Config allows for an EnvironmentID to be specified in the Remote Config Request so you can request any environment to be delivered to a given build.