-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preferences- Use staging server is not on by default. #10963
Comments
Triggered auto assignment to @MonilBhavsar ( |
Seems the changes are not updated. Unsure why? I believe that's the reason for this regression! |
This is a problem with our GH CD/CI which we encountered already once before. Discussing internally in Slack here |
@mountiny the code didn't get deploy properly and caused this issue? |
Correct, there is a problem in our deploy process so this did not cause the problem, it is just that the code which should have fix this was not part of the staging release (even though it should). You can read more in the Slack, it is quite weird thing |
I can confirm now this should be fixed now 🙇 |
Yes that's weird. Thanks for clarifying! |
No problemo |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Issue was found when executing #10935
Action Performed:
Expected Result:
Use staging server should be enabled by default
Actual Result:
Use staging server is not on by default
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: v1.2.0-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5729954_10935_mWeb.mp4
Bug5729954_10935_ios.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: