Use case
From the add-to-app instruction: https://docs.flutter.dev/add-to-app/ios/project-setup, under "Use frameworks" section, one of the step is to build the xcframeworks:
flutter build ios-framework --output=/path/to/MyApp/Flutter/
This caused validation failure (#148300) since Apple requires these xcframeworks to be signed.
Our latest effort (#183399) is to sign them using developer's own certs (rather than Flutter LLC) during flutter build ios-framework. However, this seems to defeat the purpose of this new validation - Apple's intention is to ensure these binaries are indeed from trusted sources (i.e. signed by Flutter LLC).
Proposal
Find ways to provide officially code-signed xcframeworks (Flutter.xcframework & plugins), signed by Flutter LLC cert, to add-to-app users.
Use case
From the add-to-app instruction: https://docs.flutter.dev/add-to-app/ios/project-setup, under "Use frameworks" section, one of the step is to build the xcframeworks:
This caused validation failure (#148300) since Apple requires these xcframeworks to be signed.
Our latest effort (#183399) is to sign them using developer's own certs (rather than Flutter LLC) during
flutter build ios-framework. However, this seems to defeat the purpose of this new validation - Apple's intention is to ensure these binaries are indeed from trusted sources (i.e. signed by Flutter LLC).Proposal
Find ways to provide officially code-signed xcframeworks (
Flutter.xcframework& plugins), signed by Flutter LLC cert, to add-to-app users.