We need the --force flag.

[willbsoon]

We've been building local workflows for Flutter development and app deployment. Currently, we find that the --force flag is essential in our CI tasks running on a local server. It would be appreciated if we could reconsider re-enabling this option.

[felangel]

Hi @willbsoon 👋
Thanks for opening an issue!

We have removed the --force flag but have added:

• --allow-native-diffs to allow native file changes
• --allow-asset-diffs to allow asset changes

Let us know if that helps 👍

[willbsoon]

@felangel
Thank you for your response. It appears that you are discussing the use of the shorebird patch command with reference to those flags. However, it seems there's no option to suppress prompts even with those flags. Moreover, the necessity for the --force flag extends beyond just patch to also include release. In our current workflow, where we use flutter build followed by Fastlane for uploading files to the store, switching to shorebird release introduces prompts that halt subsequent operations. Therefore, we need a method to employ the --force option for releases as well to ensure our processes run uninterrupted.

[eseidel]

Ah yeah, we have an issue where we're still showing prompts under fastlane and shouldn't. We can look next week, thanks for reporting: #1705

[willbsoon]

@eseidel Thank you for the prompt response and for acknowledging the issue regarding prompts under Fastlane. Looking forward to seeing how issue #1705 progresses. Thanks again for your support!

[eseidel]

I'm going to dupe this against #1705 for now and we can open an new issue once we resolve that if it doesn't fix your issue, sound good?