Hello

Sure. This is accomplished by telling the linker this framework is optional, by using the -weak_framework keyword instead of the -framework one.

See https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/WeakLinking.html (bottom of page)

And the -weak_framework option here: http://www.manpagez.com/man/1/ld64/Xcode-5.0.php

I believe that's all you need, but let me know if it wasn't enough.

Embedded binaries are a different thing, they're used in mechanisms that belong and are controlled 100% by the app.

Here, that weak linking thing is rather a feature of the OS's program loader's dynamic linker.

OK I see. This sequence of -framework flags is set by the .pbxproj file parser. So it won't take your change because the Xcode project file tells it that this framework isn't optional at all ! Kind of a chicken and egg problem.

I could tell you to modify your Xcode project file by hand with notepad, but beware, that's some dirty business :-/

Another option would be to use otool or install_name_tool in a pre-packaging script, to "correct" what the linker did. The idea would be to delete the "strong linking" load command reference to AppTrackingTransparency in your app's binary, then add it again but under a "weak linking" one.

Which option would you like me to help you with ?

Oh, yes, the post-processing way in Unity would definitely be the cleanest of all !

Basically, you need to flag that framework as optional in the Xcode project file that Unity generates. I believe Unity has some API to manipulate Xcode project files, but I never used them.

Basically, you need to locate the framework you want to flag in the file and set it an attribute. E.g. in this example taken from the wild wild web :

%
		018D55E216605FBC005DE12D /* StoreKit.framework in Frameworks */ = {isa = PBXBuildFile; fileRef = 018D55E116605FBC005DE12D /* StoreKit.framework */; settings = {ATTRIBUTES = (Weak, ); }; };
%

Of course on your machine the framework reference will have a different GUID, but that's just so that you see where to change and what.

Congratulations !

Did you do a thorough rebuild ?

Normally when you call pbxprojparse this way:

% in cmd.exe
"%IOSUNITYBUILDER_PATH%\Toolchain\pbxprojparse.exe" "path\to\Unity-iPhone.xcodeproj\project.pbxproj" -frameworks
%

you should get the list of framework-related linker flags, in the form:

%
-framework XXXXX
-weak_framework YYYYY
%

Do you get something different ? If yes, probably your modification was done at the wrong place.

Well, that's possible. Pods are usually community-contributed addons, of very variable quality.

Nonetheless, I'm certain a proper modification to the project.pbxproj file done at the right place would have solved it. You might have modified a framework's PBXFileReference that was affected to either the wrong build target, or the wrong build configuration.