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
When a Flutter app depends on a package with a cocoapods plugin that does not contain support for running on the arm64 version of the iOS simulator, we get an error. For example:
Swift Compiler Error (Xcode): Could not find module 'awesome_notifications_fcm' for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator, at: /Users/username/myapp/build/ios/Debug-dev-iphonesimulator/awesome_notifications_fcm/awesome_notifications_fcm.framework/Modules/awesome_notifications_fcm.swiftmodule
/Users/username/myapp/ios/Runner/AppDelegate.swift:1:7
Whilst ultimately this requires the package author to add support for the arm64 architecture, it would be very helpful if we could launch the iOS simulator from Android Studio in "Rosetta" mode. This is possible from within Xcode 15 using menu Product > Destination > Destination Architectures > Show Rosetta Destinations.
Is it possible to launch the iOS simulator in this mode? Starting the simulator via Xcode and then running the Flutter app from Android Studio doesn't seem to work.
The text was updated successfully, but these errors were encountered:
When a Flutter app depends on a package with a cocoapods plugin that does not contain support for running on the arm64 version of the iOS simulator, we get an error. For example:
Whilst ultimately this requires the package author to add support for the arm64 architecture, it would be very helpful if we could launch the iOS simulator from Android Studio in "Rosetta" mode. This is possible from within Xcode 15 using menu
Product
>Destination
>Destination Architectures
>Show Rosetta Destinations
.Is it possible to launch the iOS simulator in this mode? Starting the simulator via Xcode and then running the Flutter app from Android Studio doesn't seem to work.
The text was updated successfully, but these errors were encountered: