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
engine gn updates required for simulator on macOS arm #66926
Finally, the target arch needs to be included in either the output folder or bundle path, so that the tool can select the appropriate version.
Or, we can do #60109. That will create one bundle with all the architectures (layout details at #36204 (comment)), and Xcode will know how to link on the right pieces.
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 Sep 29, 2020
Or, we can do #60109. That will create one bundle with all the architectures (layout details at #36204 (comment)), and Xcode will know how to link on the right pieces.
jonahwilliams commentedon Sep 29, 2020
That sounds like it would simplify distribution. The output folder still needs to be changed so the builds don't clobber eachother on the build bots
jmagman commentedon Sep 29, 2020
Ah, you're right. Plus, to build an xcframework you need all the individual frameworks, then you run a command that smooshes them all together.
jeco1996 commentedon Jan 23, 2021
any ETA?
jmagman commentedon Jan 29, 2021
I believe @gw280 tracked down relevant issues and was able to land flutter-team-archive/buildroot#422.
jmagman commentedon Jan 29, 2021
Next step is #73066.
github-actions commentedon Aug 6, 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.