Remove bitcode=NO from add-to-app flows#39503
Conversation
|
@dnfield When I turn off bitcode I get this new failure in module_test_ios: It passes on master. Landed this change so you can check it out and take a look and to see if any other tests fail. |
There was a problem hiding this comment.
This makes me so happy. I believe we have some open issues around making this less painful for people right? Or were those already resolved by moving it here instead of into the podhelper.rb?
There was a problem hiding this comment.
You're maybe thinking of issues like #24342. I removed the post_install from the helper script with https://github.com/flutter/flutter/pull/36793/files#diff-b528f954e369c153bb31a631a8033be3L64, so I don't think it's painful anymore. This one only runs for the ephemeral module, so no one should be editing it.
There was a problem hiding this comment.
It makes me happy too, though!
|
We're not providing debug symbols with the profile build after the changes. I think we could, because profile is still bitcode-marker - but I'm not entirely sure that it's valuable to do so since they're symbols for assembly files. @xster, you added this requirement to the test a month ago - is there something I'm missing here about why it's improtant for App.framework in particular? |
|
Ok, I see in #37065 the rationale for this - I'll see if I can add them back for profile. |
|
#39530 puts the symbols back for profile bitcode builds. |
dnfield
left a comment
There was a problem hiding this comment.
LGTM. Change to keep symbols in profile framework has landed, so hopefully this is good now.
Description
Enable bitcode on add-to-app flows.
Related Issues
Code-half of #39359.
Fixes #24366.
Tests
Make sure add-to-app and module_test_ios still pass.
Checklist
///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change