You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Allow Xcode archive builds to be run in Debug and Profile build mode for testing #57557
We connected the Flutter module in native iOS App, and entered the test phase after the completion of development.
In the test phase, we provide the archive debug App for the tester with continuous integration, and provide some unique functions.
However, we found an error "Flutter archive builds must be run in Release mode".
We want to know the reason .
Obviously editing Flutter out from under it isn't ideal. I can't think of a good way from within Xcode to confirm "Are you SURE you want to archive in Debug?!"
changed the title [-] Flutter archive builds must be run in Release mode[/-][+]Allow Xcode archive builds to be run in Debug and Profile build mode for testing[/+]on May 19, 2020
@jmagman
Developers often use debug for develop. In my opinion, apps should not crash in debug with either Build or archive , we should find the crash reason, rather than close archive in debug. so we should Allow Xcode archive builds to be run in Debug and Profile build mode for testing.
@mumenma I agree there should be a way. I'm hoping we've fixed enough bugs related to the "accidental" debug archives that we can remove that check and -1 exit.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
jmagman commentedon May 19, 2020
Developers archiving for App Store submission hit SO many issues with accidentally submitting a Debug version, which crashes on launch:
#12086
#37850
https://github.com/flutter/flutter/issues?q=label%3Aplatform-ios+label%3Atool+white+screen+is%3Aclosed
Which of course means your legitimate QA use case isn't possible, even though you know what you're doing.
I believe if you delete these lines from
<Flutter-SDJ>/packages/flutter_tools/bin/xcode_backend.shit may just work?flutter/packages/flutter_tools/bin/xcode_backend.sh
Lines 90 to 101 in bcc4290
Obviously editing Flutter out from under it isn't ideal. I can't think of a good way from within Xcode to confirm "Are you SURE you want to archive in Debug?!"
[-] Flutter archive builds must be run in Release mode[/-][+]Allow Xcode archive builds to be run in Debug and Profile build mode for testing[/+]mumenma commentedon May 20, 2020
@jmagman
Developers often use debug for develop. In my opinion, apps should not crash in debug with either Build or archive , we should find the crash reason, rather than close archive in debug. so we should Allow Xcode archive builds to be run in Debug and Profile build mode for testing.
jmagman commentedon May 20, 2020
@mumenma I agree there should be a way. I'm hoping we've fixed enough bugs related to the "accidental" debug archives that we can remove that check and
-1exit.github-actions commentedon Aug 20, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.