Hello

This is typical of a syntax error in the Windows command interpreter.

The most common cause is that either the command line is too long, or it contains forbidden characters. This can happen if you use very long file/directory access paths.

Have you located your Xcode project in a directory close enough to the drive root, and are the static libraries located on a local (non-network) drive, close enough to the drive root too ?

That's an unusual case. Can you share your C:\iOS directory with me so that I reproduce the problem ? Confidentiality is guaranteed.

I'm reviewing what you sent me. On my side, the builder starts normally, without showing the behavior you describe.

One preliminary remark : you specify additional frameworks, but don't specify the path where the linker should look for them. If you want them to have any effect, your flags shouldn't be just

% Extra linker flags 
-framework FBSDKCoreKit -framework FBSDKGamingServicesKit -framework FBSDKLoginKit -framework FBSDKShareKit
%

But

% Extra linker flags
-FC:\iOS\Facebook920staticlibs -framework FBSDKCoreKit -framework FBSDKGamingServicesKit -framework FBSDKLoginKit -framework FBSDKShareKit
%

Anyway, it doesn't explain why the builder doesn't start correctly on your computer. It might be because of an invalid/forbidden character in your private key passphrase. Have you checked that ?

What do you mean by "I have moved the Facebook SDK to the frameworks folder" ? Which frameworks folder are you talking about here ?

And would you please post here the name and contents of the .txt file that I put in that directory, precisely for that purpose ?

Missing symbols mean either a library or framework is missing, *or* an API mismatch.

You say:

“I updated to FBSDK to 11.0.0 and static libs to 11.2.1.”

The version of the Facebook static libraries that you use does not match the version your game code expects. How can you expect that to link without problems ?

:: @Pierre-Marie Baty added on 08 Nov ’21 · 12:04

I'm making this addition because I realize it might not be obvious.

To all readers. When it comes to code, and unless explicitly stated otherwise by their(s) author(s), *libraries and frameworks are not guaranteed to be backwards compatible*. The safest path is to assume they won't be. This is not only true for iOS but for every programming domain in general. For example, the well-known TLS library OpenSSL 3.0 is not API-compatible with OpenSSL 1.x.

That is why it is crucially important, if you supply extra libraries and frameworks to the linker, that they be 100% API-compatible with your code, and the first thing to verify is that they're at the same version level. If you can't find the exact same version of the library you need available to download, at least pick one that has the same major/minor version number. It is generally (but not always) safe to assume that revision changes are API-compatible. For example, a library version 1.2.5 can be reasonably expected to be compatible with API calls that were written for version 1.2.0. On the other hand, using a library version 1.3.0 with API calls that expect version 1.2.0 is more risky. You understand why using the version 3.4.5 of that library thinking "the higher the better" is not only wrong but asking for trouble...

Unfortunately I haven't kept what you sent me. The initial diagnosis was to reproduce a case where the builder wouldn't start, and I couldn't reproduce that.

Please send me your files again if you want me to diagnose further, but do make sure the project can be built with Xcode without problems before sending them to me, to make sure the problem is with the builder and not with the project.

I did.

First try: renamed Podfile, hit Build. GoogleMobileAds header not found. Added GoogleMobileAds-8.8.0 (as required by the Podfile), hit Build again.

Second try: compiler error: "unknown type name GADNativeCustomTemplateAd". This error should not happen on a properly constructed project, because I supplied exactly the SDK requested by the Podfile.

A Google search on this error immediately yielded something that doesn't smell good for you : https://answers.unity.com/questions/1342236/unknown-type-name-gadnativecustomtemplatead-did-yo.html - as it looks like Xcode has the same problem, it tends to indicate it's not a problem with the builder but with the project. I had to check that, and so I did.

Third try: took the fresh zip again, and this time I built it with Xcode + CocoaPods on Mac. Guess what ? Totally consistently, it doesn't build with Xcode and CocoaPods on Mac. Demonstration is made that it's not a problem with the builder.

I asked you to rule out that case specifically before requiring me to spend time on your case. As you're obviously the kind of person who doesn't *want* to follow my guidance and expects me to do *their* work, the next time for you will be paid support.