Repository navigation
Always build iOS Archive builds in release mode - #12773
Conversation
There was a problem hiding this comment.
Is this to prevent local engine overrides and then archive?
There was a problem hiding this comment.
It's because Xcode builds always pick up the previous build mode.
Currently, it's necessary to run flutter build ios --release in order to produce a Generated.xcconfig with the correct build mode and framework directory for an archive build.
bc564c4 to
d605451
Compare
|
There's a bit more work here to support this properly. Most importantly, even with an override of For now, I've updated to just emit an error with instructions and exit with a build failure. Long-term, I think the right thing to do is make the Xcode build more hermetic and reduce the dependency on a previous command-line run. |
Archive builds for upload to iTunes Connect should always be built in release mode, not doing so results in crash on startup. Bug: flutter#12086
d605451 to
3c9ed01
Compare
|
Still LG |
Archive builds for upload to iTunes Connect should always be built in release mode, not doing so results in crash on startup. Bug: flutter#12086
4 participants
Archive builds for upload to iTunes Connect should always be built in
release mode, not doing so results in crash on startup.
Bug: #12086