Failed to compile bundle: /var/folders/8y/63_hr4hj31b0tw1gm_l5h32m0000gn/T/FBSDKCoreKit_Basicsepsmbe7q/FBSDKCoreKit_Basics.arm64.xar
Stderr:
/Applications/Xcode-13.2.1.app/Contents/Developer/usr/bin/ipatool:372:in `run'
/Applications/Xcode-13.2.1.app/Contents/Developer/usr/bin/ipatool:2886:in `block in CompileOrStripBitcodeInBundle'
/Applications/Xcode-13.2.1.app/Contents/Developer/usr/bin/ipatool:2825:in `each'
/Applications/Xcode-13.2.1.app/Contents/Developer/usr/bin/ipatool:2825:in `CompileOrStripBitcodeInBundle'
/Applications/Xcode-13.2.1.app/Contents/Developer/usr/bin/ipatool:3112:in `block in ProcessIPA'
/Applications/Xcode-13.2.1.app/Contents/Developer/usr/bin/ipatool:3073:in `each'
/Applications/Xcode-13.2.1.app/Contents/Developer/usr/bin/ipatool:3073:in `ProcessIPA'
/Applications/Xcode-13.2.1.app/Contents/Developer/usr/bin/ipatool:4035:in `<main>'}
Steps to reproduce
I tried to archive my project using Travis and Xcode 13.2.1. I already update pods to latest version.
When used Xcode on my local mac (Mac OS 12.3.1 and Xcode 13.3) it's archived successfully.
I'm using development for export_method
Code samples & details
Same here:AdHoc export fails. Debug and Appstore builds are OK.
Error I've got for ad-hoc build (from Fastlane gym):
error: exportArchive: ipatool failed with an exception: #<CmdSpec::NonZeroExitException: $ /Applications/Xcode_13.2.1.app/Contents/Developer/usr/bin/python3 /Applications/Xcode_13.2.1.app/Contents/Developer/usr/bin/bitcode-build-tool -v -t /Applications/Xcode_13.2.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin --sdk /Applications/Xcode_13.2.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.2.sdk -o /var/folders/n2/310d7l4x01n95190_r3prgf00000gn/T/ipatool20220418-99158-19cd3pw/thinned-out/arm64/Payload/PdfEdit.app/Frameworks/FBSDKCoreKit_Basics.framework/FBSDKCoreKit_Basics --generate-dsym /var/folders/n2/310d7l4x01n95190_r3prgf00000gn/T/ipatool20220418-99158-19cd3pw/thinned-out/arm64/Payload/PdfEdit.app/Frameworks/FBSDKCoreKit_Basics.framework/FBSDKCoreKit_Basics.dSYM --strip-swift-symbols /var/folders/n2/310d7l4x01n95190_r3prgf00000gn/T/ipatool20220418-99158-19cd3pw/thinned-in/arm64/Payload/PdfEdit.app/Frameworks/FBSDKCoreKit_Basics.framework/FBSDKCoreKit_Basics
Status: pid 99536 exit 1
Appcenter builds failing to archive ios w/Xcode 13.2 [Solution: Use v8.0.2 here or Xcode 13.3]
thebergamo/react-native-fbsdk-next#244
I wonder if it is this commit? 7c5e956
Came here from react-native-fbsdk-next via @caiorrsdeg - it's important to note that Xcode 13.2 is the latest version available from a lot of CI providers, as well as lots of dev machines that are admittedly older but cannot upgrade to macOS 12 because of Apple planned obsolescence policy. Specifically I've got two otherwise serviceable older machines I use in a build farm that are stuck on macOS 11, and they won't upgrade past Xcode 13.2 unfortunately.
@mikehardy I would only expect that to be an issue if RN is building from source -- if then, since the LastUpgradeCheck value seems to just be what determines whether you see an upgrade warning while in Xcode. The reason I proposed using the new version of the SDK is that it was built with Xcode 13.0 and should avoid this particular issue when archiving an app -- with any version of Xcode 13+.
Hmm - we integrate the cocoapods, which do build from source I believe, but it is unclear to me whether something like last upgrade check value should cause an archive fail. Honestly the Xcode toolchain is a bit mystifying/opaque to me as a mostly-android person so I recognize your hypothesis as likely (if I understand it as "should only affect Xcode warnings, not archive") but it was all I could see in the commit log here so I grasped at the straw.
Hypotheses aside we've definitely got an experimental result of archive failure with Xcode 13.2.1 and facebook-ios-sdk with version 13.1.0 here (https://github.com/thebergamo/react-native-fbsdk-next/blob/a9ed2ccdb873663df26831bdfe5cd652e2028a51/react-native-fbsdk-next.podspec#L16-L30) and we're just not sure what it is, but the user is apparently on the macos-11 AppCenter CI runner so does not currently have access to Xcode 13.3+
@caiorrsdeg - I notice that v13.2.0 of facebook-ios-sdk is released here and we haven't ingested it yet downstream, do you still see the problem if you use https://github.com/ds300/patch-package/ in combination with a local change to the node_modules/react-native-fbsdk-next/
podspec file that brings in 13.2.0? Perhaps this issue is fixed / not relevant anymore, and we wouldn't want to chase ghosts from an old version
Hypotheses aside we've definitely got an experimental result of archive failure with Xcode 13.2.1 and facebook-ios-sdk with version 13.1.0 here (https://github.com/thebergamo/react-native-fbsdk-next/blob/a9ed2ccdb873663df26831bdfe5cd652e2028a51/react-native-fbsdk-next.podspec#L16-L30) and we're just not sure what it is, but the user is apparently on the macos-11 AppCenter CI runner so does not currently have access to Xcode 13.3+
We've also verified this issue and are pretty sure it's due to the product that later versions of Xcode is producing. SDK version 13.2.0 should work with any version of Xcode 13 and later. If you find differently, please let us know.
### Bug Fixes
* **ios:** use facebook-ios-sdk 13.2.0 / archive with Xcode < 13.3 ([#246](#246)) ([d149b66](d149b66)), closes [/github.com/facebook/facebook-ios-sdk/issues/2062#issuecomment-1117736024](https://github.com/thebergamo//github.com/facebook/facebook-ios-sdk/issues/2062/issues/issuecomment-1117736024) [#244](#244)
Hmm - we integrate the cocoapods, which do build from source I believe, but it is unclear to me whether something like last upgrade check value should cause an archive fail. Honestly the Xcode toolchain is a bit mystifying/opaque to me as a mostly-android person so I recognize your hypothesis as likely (if I understand it as "should only affect Xcode warnings, not archive") but it was all I could see in the commit log here so I grasped at the straw.
Hypotheses aside we've definitely got an experimental result of archive failure with Xcode 13.2.1 and facebook-ios-sdk with version 13.1.0 here (https://github.com/thebergamo/react-native-fbsdk-next/blob/a9ed2ccdb873663df26831bdfe5cd652e2028a51/react-native-fbsdk-next.podspec#L16-L30) and we're just not sure what it is, but the user is apparently on the macos-11 AppCenter CI runner so does not currently have access to Xcode 13.3+
@caiorrsdeg - I notice that v13.2.0 of facebook-ios-sdk is released here and we haven't ingested it yet downstream, do you still see the problem if you use https://github.com/ds300/patch-package/ in combination with a local change to the node_modules/react-native-fbsdk-next/
podspec file that brings in 13.2.0? Perhaps this issue is fixed / not relevant anymore, and we wouldn't want to chase ghosts from an old version
should I update 13.1.0 to 13.2.0 in these lines?
s.subspec 'Core' do |ss|
ss.dependency 'FBSDKCoreKit', '~> 13.1.0'
ss.source_files = 'ios/RCTFBSDK/core/*.{h,m}'
s.subspec 'Login' do |ss|
ss.dependency 'FBSDKLoginKit', '~> 13.1.0'
ss.source_files = 'ios/RCTFBSDK/login/*.{h,m}'
s.subspec 'Share' do |ss|
ss.dependency 'FBSDKShareKit', '~> 13.1.0'
ss.dependency 'FBSDKGamingServicesKit', '~> 13.1.0'
ss.source_files = 'ios/RCTFBSDK/share/*.{h,m}'