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
flutter build ios-framework --xcframework incorrectly copies Flutter.framework.dSYM into App.xcframework #157359
Add-to-app xcframework generation in release mode produces App.xcframework/ios-arm64/dSYMs/Flutter.framework.dSYM and Flutter.xcframework/ios-arm64/dSYMs/Flutter.framework.dSYM. App.xcframework should not contain this dSYM.
This causes the IPA error:
error: Multiple commands produce '......./BuildProductsPath/Release-iphoneos/Flutter.framework.dSYM/Contents'
Observe ios_using_prebuilt_module/Flutter/Release/App.xcframework/ios-arm64/dSYMs/Flutter.framework.dSYM and ios_using_prebuilt_module/Flutter/Release/Flutter.xcframework/ios-arm64/dSYMs/Flutter.framework.dSYM.
The workaround is to delete App.xcframework/ios-arm64/dSYMs/Flutter.framework.dSYM.
And also the unit test add something like parentA.childFile('Flutter.framework.dSYM')..createSync(); and confirm the command doesn't change (also confirm it fails before the fix because I didn't actually try this 😅)
We are encountering the following issue with our iOS framework builds in release mode. Previously, the size of the framework was around 100MB, but now it has increased to over 1GB. We are removing the dSYM files and their references from the Info.plist files via a script during the release build. However, after doing this, we are now facing the following signature error. Could you please assist us?
SignatureCollection /Users/runner/Library/Developer/Xcode/DerivedData/ProjectName-edzqkohwcavlbfdkjtskcbnbjloe/Build/Intermediates.noindex/ArchiveIntermediates/QA/BuildProductsPath/QA-iphoneos/Flutter.xcframework-ios.signature
cd /Users/runner/work/1/s/ProjectName.xcodeproj
builtin-collectSignature --input /Users/runner/work/1/s/Flutter/QA/Flutter.xcframework --output /Users/runner/Library/Developer/Xcode/DerivedData/ProjectName-edzqkohwcavlbfdkjtskcbnbjloe/Build/Intermediates.noindex/ArchiveIntermediates/QA/BuildProductsPath/QA-iphoneos/Flutter.xcframework-ios.signature --info platform ios --info library Flutter.framework
error: signature-collection failed: The operation couldn’t be completed. (XCBUtil.CodeSignatureInfo.Error error 0.)
The solution fixed my previous problem. It's not showing duplicate anymore. Instead, it is giving me no No such module 'Flutter' erro in compile time. Note: I am using a framework built in flutter inside my native iOS project.
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 Oct 22, 2024
Logic is here:
flutter/packages/flutter_tools/lib/src/commands/build_ios_framework.dart
Lines 153 to 155 in 5fa5a64
Don't regress #80065
jmagman commentedon Oct 22, 2024
Test to be updated is here:
flutter/dev/devicelab/bin/tasks/build_ios_framework_module_test.dart
Lines 191 to 199 in 5fa5a64
jmagman commentedon Oct 22, 2024
And also the unit test add something like
parentA.childFile('Flutter.framework.dSYM')..createSync();and confirm the command doesn't change (also confirm it fails before the fix because I didn't actually try this 😅)flutter/packages/flutter_tools/test/commands.shard/hermetic/build_darwin_framework_test.dart
Line 559 in e9fb545
dorukbasaran commentedon Oct 23, 2024
We are encountering the following issue with our iOS framework builds in release mode. Previously, the size of the framework was around 100MB, but now it has increased to over 1GB. We are removing the dSYM files and their references from the Info.plist files via a script during the release build. However, after doing this, we are now facing the following signature error. Could you please assist us?
SignatureCollection /Users/runner/Library/Developer/Xcode/DerivedData/ProjectName-edzqkohwcavlbfdkjtskcbnbjloe/Build/Intermediates.noindex/ArchiveIntermediates/QA/BuildProductsPath/QA-iphoneos/Flutter.xcframework-ios.signature
cd /Users/runner/work/1/s/ProjectName.xcodeproj
builtin-collectSignature --input /Users/runner/work/1/s/Flutter/QA/Flutter.xcframework --output /Users/runner/Library/Developer/Xcode/DerivedData/ProjectName-edzqkohwcavlbfdkjtskcbnbjloe/Build/Intermediates.noindex/ArchiveIntermediates/QA/BuildProductsPath/QA-iphoneos/Flutter.xcframework-ios.signature --info platform ios --info library Flutter.framework
error: signature-collection failed: The operation couldn’t be completed. (XCBUtil.CodeSignatureInfo.Error error 0.)
sulaimankhan7 commentedon Oct 23, 2024
The solution fixed my previous problem. It's not showing duplicate anymore. Instead, it is giving me no
No such module 'Flutter'erro in compile time. Note: I am using a framework built in flutter inside my native iOS project.Prevent `flutter build ios-framework --xcframework` from copying `Flu…
jmagman commentedon Oct 24, 2024
@dorukbasaran The fix just merged, would you be willing to test it on the master channel?
jmagman commentedon Oct 30, 2024
@dorukbasaran or @sulaimansust can you confirm the fix? I'd like to hotfix to stable if it's working.
jmagman commentedon Oct 30, 2024
Or anyone else hitting this, maybe 👍 @goncg007 @farukarslan?
Prevent `flutter build ios-framework --xcframework` from copying `Flu…
jogboms commentedon Nov 4, 2024
Hey @jmagman I can verify this works as expected on master
Prevent `flutter build ios-framework --xcframework` from copying `Flu…
jmagman commentedon Nov 4, 2024
Stable channel cherry pick request at #158125
Prevent `flutter build ios-framework --xcframework` from copying `Flu…
[CP-stable]Prevent `flutter build ios-framework --xcframework` from c…
Jeanno commentedon Nov 5, 2024
@jmagman It also works for me. Thanks
[CP-beta]Prevent `flutter build ios-framework --xcframework` from cop…
github-actions commentedon Nov 19, 2024
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.