Draft: Resolve "Fix changing CP deployment in developer options when production and staging are identical."
Ticket(s) / Related Merge Requests
Summary
When both production and staging codepush environments are identical, the deployment target cannot be change in the developer options. (Summarize the bug encountered concisely)
Steps to reproduce
Ensure that there's no pending code-pushes between staging and production. Try to change the deployment in developer options from production to staging or vice-versa. (How one can reproduce the issue - this is very important)
What is the current bug behavior?
When trying to change the target deployment env from production to staging or vice-versa it won't change. (What actually happens)
What is the expected correct behavior?
When trying to change the target deployment env from production to staging or vice-versa it should change. (What you should see instead)
(Any issue cards for the merge request, and related merge requests/dependencies)
Summary of Changes
(Summarize the changes made concisely)
-
Changelog file updated with this template (one or more) -
Added for new features. -
Changed for changes in existing functionality. -
Deprecated for soon-to-be removed features. -
Removed for now removed features. -
Fixed for any bug fixes. -
Security in case of vulnerabilities.
-
Testing Considerations
(Share which areas to focus on while testing this MR)
Regression Scope
(Can this change cause another regression issue? Which areas to focus on for regression testing?)
Platform Affected (web, mobile, etc)
(Which platforms are affected by this change? Web, Mobile, or Both?)
Developer Testing Completed
(What has been tested already?)
Screenshots
(Any extra UI screens that can be shared)
Does this impact
-
Localization -
Dark/light mode -
Guest mode
Related to #4753 (closed)