-
Notifications
You must be signed in to change notification settings - Fork 147
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
fix: shorebird
hangs when run under fastlane
#1705
Comments
I think the right thing here is for us (or mason_logger) to detect that it's running headless and never hang in confirm. |
Got another report of this just now with #1841. Does anyone know of an example project using fastlane with Flutter that we should work from? Otherwise I guess we can build one from https://docs.flutter.dev/deployment/cd#fastlane |
A workaround for now could be to run:
since yes will send "y" any time prompted. |
Any update on this ? |
A fix has been merged to our main branch and will go out in the next release (today or tomorrow) |
Thanks for the update! can you confirm what steps we need to take to auto confirm ? |
None, you will just need to update to the latest version when we release. |
In the meantime, you can set |
Hi, Have you deployed the new release, if yes what exactly i have to pass now ? |
This has been deployed. It should just work with no changes on your side |
"""
I included the shorebird command in my fastlane pipeline for ease of use and this is where it never continues after it packages everything up. I then tried running the command outside of fastlane (thinking it might be some directory issue, it occured in the past with different tools), and that's when I found out why it never finished via fastlane. Shorebird asks you if you want to create a new release ("Would you like to continue?"), and that question is not visible if you run the command via fastlane. So just had to add the --force command for the release build that I was doing via fastlane and everything works. 😂
"""
The text was updated successfully, but these errors were encountered: