Hello

I received the Xcode project and I'm looking at it right now.

One of the Pods involved in the operation is built (in compliance with the informations from the pod itself !) in a directory that doesn't match the library and framework search directory that's passed by the pod to the linker.

I'm still investigating why it's able to work with Xcode. That's still a mystery to me. It looks like Xcode may decide for a build directory that would contradict the pod's instructions. If I can't find the right reason, the workaround will be to pass more directories to the linker than those explicitly given by the pod.

That would be something like adding the following linker flags:

%
-Fbuild/Release-iphoneos/FBLPromises -framework Security
%

The first one to "fix" the framework path to the Promises pod build directory, the second one to bring in the Security framework from the iOS SDK that is implicitly linked.

I haven't tested, so let me know if it helps.

@Oneday : same issue indeed.

I'm still looking at it. Can't find *why* Xcode can build this, as required frameworks are missing from the project files. It's as if Xcode added framework specifications by its own will.

:: @Pierre-Marie Baty added on 23 Feb ’23 · 10:19

@all: another workaround is to remove the Firebase pods from the Podfile and inject the Firebase frameworks from the Firebase binary release manually:

https://github.com/firebase/firebase-ios-sdk/releases

Make sure to fetch a version that's compatible with what the Podfile says. e.g. if you have

%Podfile
target 'UnityFramework' do
  pod 'Firebase/Core', '10.4.0'
  pod 'Firebase/Messaging', '10.4.0'
end
%

then get the binary release labeled *Firebase Apple 10.4.0*.

Yes, you're doing it wrong.

It doesn't work that way. Please *read the documentation* on how to integrate third-party frameworks. Basically, you need to use the "Add extra framework" button for that - and of course, follow Google's integration guidelines.

@Oneday - the error happens when building the GoogleUtilities pod. Probably part of either Firebase or Google Mobile Ads. Remove these Pods from your Podfile and add them manually.

@Raad: your error looks like this one : https://www.pmbaty.com/iosbuildenv/help/thread.php?path=Problem%20solving/&file=errors-compiling-an-admob-project
Please follow the same procedure to ascertain that your project is buildable first.

Maybe you downloaded the Appodeal SDK for macOS and there is a different download for iOS ? If you give me the link to their download page I can perhaps locate it for you.

@Oneday: this specific issue should be handled by the build script. It means something needs to be fixed on my side. Could you please send me your Xcode project to my email address (pm at this domain) so that I reproduce the problem ? Thanks in advance.

About Appodeal, your 2nd link was the right one, but it looks like they goofed on their side and swapped the iOS Appodeal SDK with the Mac Appodeal SDK (since the builder couldn't find any iOS frameworks in it).

I'm not saying they did (someone would have to verify the binaries), I'm just saying it looks like so. I'll look at your project now.

@Oneday: I could build your project with minor fixes.

Step 1: edit build.cmd around line 2385 and change the line that says:

% build.cmd circa line 2385
				set LDFLAGS_DEFAULTLIBS=!LDFLAGS_DEFAULTLIBS! -L/usr/lib/swift -L"!SDK_PATH!/../Toolchain/extra" -lswiftCompatibilityMissingSymbols
%

into

% build.cmd circa line 2385
				set LDFLAGS_DEFAULTLIBS=!LDFLAGS_DEFAULTLIBS! -L/usr/lib/swift
				if not exist "!SDK_PATH!\libswiftCompatibility51.a" set LDFLAGS_DEFAULTLIBS=!LDFLAGS_DEFAULTLIBS! -L"!SDK_PATH!/../Toolchain/extra" -lswiftCompatibilityMissingSymbols
%

Step 2: add "-framework GoogleMobileAds" in the extra linker flags field of the *main application* (Main app) tab (NOT the UnityFramework tab).

After these fixes your project builds successfully. I haven't tested it on a real device though.

@Raad: Are you sure your project is error-free first ? Can Xcode build it ?

@RobReijnen: some of the Pods your project uses (e.g. FirebaseCoreInternal, part of the FirebaseCore framework) are at least partly written in Swift and not in C/C++/Objective-C. This builder doesn't compile Swift code (at least at the moment). To work this around and build your project, you need to use the precompiled version of these frameworks, which can usually be downloaded from their vendor's website or GitHub. For Google Firebase, the builder's HTML documentation gives detailed directions, with download links. Have you followed these instructions ? If so, on what specific part do you need help ?

The warnings you have means something must be fixed on my side in dsymutil. They affect the debug database only. If you uncheck the dSYM checkbox in the builder UI they’ll go away.

The error you get in the debug console means some necessary frameworks aren’t included by the build script in your app. This happens because these frameworks are loaded explicitly at runtime by a call to dlopen() in the code and not at loading time, so they haven’t been detected by the build script. To fix this you need to copy them yourself in the Frameworks directory of your app using a pre-packaging script. The error mentions the FBLPromises framework, but there might be others.

Glad to hear you got it working. You’re welcome.

@Raad:

You have 2 different build contexts here.

1. Your problem with ES mobile ads : the LLVM linker (LLD) doesn't allow duplicate symbols, whereas the Apple one does - see https://github.com/llvm/llvm-project/issues/55893 . Use the Apple linker to link with ES mobile ads (or tell the ES mobile ads developers that they have duplicate symbols and that it's a mistake that should be fixed anyway.)

2. Your problem with MobileTools : well, what does the remote debug console say for the reason of the crash ?

Are you sure you signed the app you’re trying to upload with a *distribution* certificate and a provisioning profile suitable for App Store uploads ?

Then it is possible that you tried to upload an app signed with a revoked certificate.

To make sure your certificates and profiles are the right ones, delete them from the Keychain tool and download them all again from the iOS provisioning portal.

You’re welcome. Happy testing !