Repository navigation
iOS and Android are failing to deploy every version #4758
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
- Deploy a new build for Android and iOS
Expected Result:
Deploy should not fail
Actual Result:
Deploy is failing on every version now https://github.com/Expensify/App/commit/ead4b67a93e86aa6f1d83d9b144222b475eb81f5/checks
Workaround:
Unknown
Platform:
Where is this issue occurring?
- iOS
- Android
Version Number: 1.0.86-2
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Expensify/Expensify Issue URL:
From @AndrewGable https://expensify.slack.com/archives/C01GTK53T8Q/p1629314685016900
iOS and Android are failing to deploy every version now
Activity
MelvinBot commentedon Aug 19, 2021
Triggered auto assignment to @TomatoToaster (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.[-]iOS and Android are failing to deploy every version now[/-][+]iOS and Android are failing to deploy every version[/+]TomatoToaster commentedon Aug 19, 2021
doesn't make sense for this to be external, posting elsewhere so this gets visibility.
roryabraham commentedon Aug 24, 2021
I think it has just been android failures today, and I believe they're related to this issue. A PR that allegedly fixes the issue was merged earlier today 🎉
Trying to figure out how we can start taking advantage of the fix ASAP. Ruby + Gems are still pretty foreign to me 😬
roryabraham commentedon Aug 24, 2021
So we are using fastlane version
~> 2, which means that we'd get this fix automatically as soon as fastlane publishes a new version that includes the PR, provided that it's not part of a major release.Need to look into how we can use a specific ref in the repo or something.
roryabraham commentedon Aug 24, 2021
Okay, I'll put up a PR.
roryabraham commentedon Aug 24, 2021
Let's hope it works 🤞
Julesssss commentedon Aug 24, 2021
I believe we can fix this manually while we await the new Fastlane release. We simply need to 'Send for Release' the latest build, this is necessary every time a release is rejected by Google.
The Fastlane PR will also fix this by manually setting the flag linked to 'Send for Release', so we can simply await that release.
Julesssss commentedon Aug 24, 2021
I marked the internal release as ready for review, which should allow the next Android deployment to succeed.
botify commentedon Aug 30, 2021
🚀 Deployed to production by @roryabraham in version: 1.0.88-2 🚀