@amanhimself Thanks, we’re already following the guidance however, when we load a build that was created via the example github action which uses eas update, what releaseChannel is that using?
Is there a way to select a profile/release channel with the update command via the Github Action?
The issue I’m seeing is that we have an env var switcher which loads an env var based on releaseChannel which is not picking anything up and falling back to ___DEV___ for builds generated via PRs