-
Notifications
You must be signed in to change notification settings - Fork 3.2k
iOS Production Deploy Failure #4978
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
Comments
In the meantime, I've manually submitted |
Sorry, originally meant to assign this to you @AndrewGable |
I think this failed because the step didn't run, which I believe is a known issue with releases, the tag has to include the code merged. So we need to wait until we deploy production once more to fully test the new production fix. |
Reopening, we saw the same failure today: https://github.com/Expensify/App/runs/3490379202 |
Ok so this time the code did actually run, but it just didn't work. Progress! |
I can reproduce this locally with |
Really confusing error.. The build number does exist, but Fastlane cannot find it. I'm trying to debug the fastlane response right now. |
Ok so.. This is weird.. When I set the |
Now trying to fix this new error..
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @roryabraham in version: 1.0.92-1 🚀
|
🚀 Deployed to production by @roryabraham in version: 1.0.93-1 🚀
|
We need to investigate and fix this deploy failure: https://github.com/Expensify/App/runs/3479417738
The text was updated successfully, but these errors were encountered: