iOS Build Environment Help Center
Hi,
An error occurred in the iOS builder after importing Facebook sdk to Unity. So I downloaded pre-compiled sdk according to the manual and added 7 .xcframework folders one by one through the 'add extra framework' button.
Then, the following error occurred during the build.
Is it the right way I did it? What should I do?
window version : windows 10 version 21H1(OS build 19043.1586)
builder version : 3.40
iOS SDK version : 15.0
Hello
You did it right but you're using an outdated builder toolchain.
Please start by updating the builder to the latest version. Always being up to date is *critical* when you want to compile recent code.
Then once you're on the latest version, migrate the iOS SDK again because version 3.44's migration assistant had an important fix for the Facebook SDK.
Post again if it doesn't solve the problem.
Best regards,
I thought it was built in the same way after the builder update, but it came back with swift error.
After downloading a zip file 'FacebookSDK-Static_XCFramework.zip' from Facebook sdk GitHub and decompressing it, is it correct to add all .xcframework directories one by one through the 'add framework' button except for FBSDKTVOSKit.xcframework?
+ Should SDK update be done again using macOS that was done in the early stages of installation? Or the SDK.zip file that was previously made through macOS is ok?
Yes, you do need to migrate the iOS SDK from Mac again using the updated assistant. See the change log at version 3.41 for the reason.
If you still get errors after that even after a thorough rebuild, please post your full build log on PasteBin.
*edit* 3.41 or 3.44, I don’t remember which one exactly, but you can’t miss the change log entry about Swift and the Facebook SDK.
My builder has been updated to version 3.46 and I have done SDK migration again, but the same error occurs. The full log is as follows.
I'd appreciate your help.
You are trying to build the project using CocoaPods but the Facebook SDK has parts written in Swift and you should use the pre-compiled binaries instead.
Your first attempt when you used the pre-compiled binaries was good, it's just that you hadn't the suitable builder and SDK. Please try again without CocoaPods (i.e. rename Podfile to Podfile.bak) and inject the Facebook precompiled binaries as needed.
The previous error has been removed. However, the following error occurs:
Did you do a thorough rebuild ?
If yes, it means that either the builder doesn't pick up the include files in the right order, or that the precompiled (binary) Facebook SDK that you downloaded doesn't match the one used in your Unity project. The latter being, IMO, the most probable cause.
For example, your Unity project would rely on Facebook SDK version X and you downloaded the precompiled Facebook SDK version Y.
Have you checked the version numbers match, or at least are API/ABI-compatible ?
The downloaded unity SDK version was 11.00.00, so I set precompiled Facebook SDK to 11.00.00 too, and the previous error disappeared, but the following error occurs.
I found some related posts on the forum and tried them, but they didn't work for me.
I'm sorry to bother you with repeated questions.
Don't feel sorry. I do feel sorry that this whole process is difficult to you, it means I have to find ways to simplify it further.
We're making a great deal of progress. It looks like you solved the Facebook part : everything now compiles correctly. The error comes at the linking phase. And the GAdXXX missing symbols here don't come from the Facebook SDK but from the Google Ads one.
It means your project also relies on the Google Ads SDK (in addition to the Facebook one), so just pick the appropriate Google SDK and do the same thing with it that you did for Facebook.
*edit* in case you wonder how I know that these symbols are from the Google SDK, the troubleshooting section in the documentation (which I invite you to read) explains what to do in case of "undefined symbols" errors. Basically, you take each symbol name one after the other and you paste them in your favorite web search engine. This promptly tells you where they come from, be it from an Apple framework or to which third-party SDK they belong.
In the end, the build was successful. Thank you so much!!
Glad to hear that, but make sure the app works. Some third-pary SDKs require that you build your app with the -ObjC extra linker flag, which in turn possibly requires that other frameworks be added. If you haven't added that linker flag like their documentation says, you'll very likely experience app crashes.
As you said, the built app caused a crash.
But I was able to solve the problem by referring to other posts on the forum, and my build works successfully.
Thank you for your help!
Glad to hear it.
You’re welcome.
Moderators: Pierre-Marie Baty