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
macOS xcode project should move Framework linking to tool #56581
not because of the simulator thing (no macOS simulator) but instead so the tool script as total control of where the Flutter.framework is and doesn't need to copy it to a specific spot
I think it may be a good idea to do the same pattern for macOS for the future-proofing xcframework / App.framework rename reasons I mentioned in the "Observations" section, and to remove the disable_input_output_paths hack in the macOS Podfile. However there's no immediate need to do this since Mac won't hit #50568 (there is no simulator, frameworks always have the x86 architectures, no thinning happens). I would defer to @stuartmorgan on the necessity and/or timing of that change.
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 7, 2020
#51453 (comment)
jmagman commentedon Jun 23, 2020
This will make arm macOS support easier.
github-actions commentedon Aug 8, 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.