Avoid thinning frameworks in iOS extensions#64674
Avoid thinning frameworks in iOS extensions#64674fluttergithubbot merged 2 commits intoflutter:masterfrom
Conversation
There was a problem hiding this comment.
This is the new check that these plugin frameworks haven't been lipod to the iOS ARCHS.
There was a problem hiding this comment.
This wasn't actually building for the simulator (it's missing --simulator) even with the -d flag. flutter build ios with a watch companion doesn't actually work. Anyway the next thing this does is run on the simulator, which does work.
There was a problem hiding this comment.
This adds a framework to the watch extension. Previous this failed because xcode_backend lipod all .frameworks, even the ones in the watch extension with a different expected architecture.
There was a problem hiding this comment.
Bitcode should be off for Runner.
There was a problem hiding this comment.
Why should bitcode be off? Bitcode is a requirement when you have a watch extension.
There was a problem hiding this comment.
Because this is an integration test that will never be submitted to the App Store and I didn't want to track down issues related to the pods building before the correct bitcode-embedded version of Flutter gets copied around. I'll set it back to YES and see if this particular integration test triggers that case.
There was a problem hiding this comment.
Adding (any) plugin is what kicks the tool into running pod install, which we need to embed the watch framework.
There was a problem hiding this comment.
This is the actual fix.
Instead of finding and thinning all *.frameworks in Runner.app, it now only does so in the Runner.app/Frameworks directory.
There was a problem hiding this comment.
Add a comment for what this is? It came from a pod?
There was a problem hiding this comment.
never mind, the answer's here. Still good to comment in the other file.
|
This pull request is not suitable for automatic merging in its current state.
|
@xster would you mind approving it? |
|
GitHub needs an approve button on the main tab instead of the files tab. |
|
It looks like this might have broken |
|
Error: |
…lutter#64829) This reverts commit ce9cde8.
Description
Watch extensions are embedded in iOS apps. Avoid lipo'ing those frameworks to iOS architectures. Stick to the app frameworks.
Related Issues
Fixes #60351
Tests
Updated
ios_app_with_extensions_testto include a watch framework. Check the build succeeds, and that the watch extension frameworks have the expected watch architectures.Checklist
///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change