Exporting to iOS project failed to build

[shunia]

Environment

How do you use Sentry?
Sentry SaaS (sentry.io) or self-hosted/on-premise (which version?)

SaaS

Which version of the SDK?

0.19.0

How did you install the package? (Git-URL, Assetstore)

Git-URL

Which version of Unity?

2021.1.25f1

Is this happening in Unity (editor) or on a player like Android, iOS, Windows?

Error only occurs in iOS project, we can not build the exported project, if remove Sentry, everything works fine;
Unity editor works as expected, exported Android Project works too. We are not aiming for other platforms.

Steps to Reproduce

1. Setup Sentry followed by documentation;
2. Export iOS project to an existing iOS project (replace);
3. Build the iOS project in xCode as usual;

Expected Result

Build pass and everything works.

Actual Result

Failed when build iOS project:

ld: warning: object file (/Users/Clover/Desktop/_/ios_exported/Libraries/lib_burst_generated.a(lib_burst_generated_part_0_merged.o)) was built for newer iOS version (15.2) than being linked (11.0)
ld: warning: object file (/Users/Clover/Desktop/_/ios_exported/Libraries/lib_burst_generated.a(lib_burst_generated_part_4.o)) was built for newer iOS version (15.2) than being linked (11.0)
ld: warning: object file (/Users/Clover/Desktop/_/ios_exported/Libraries/lib_burst_generated.a(lib_burst_generated_part_1.o)) was built for newer iOS version (15.2) than being linked (11.0)
ld: warning: object file (/Users/Clover/Desktop/_/ios_exported/Libraries/lib_burst_generated.a(lib_burst_generated_part_3.o)) was built for newer iOS version (15.2) than being linked (11.0)
ld: warning: object file (/Users/Clover/Desktop/_/ios_exported/Libraries/lib_burst_generated.a(lib_burst_generated_part_2.o)) was built for newer iOS version (15.2) than being linked (11.0)
ld: warning: object file (/Users/Clover/Desktop/_/ios_exported/Libraries/lib_burst_generated.a(lib_burst_generated_part_0.o)) was built for newer iOS version (15.2) than being linked (11.0)
Undefined symbols for architecture arm64:
  "__NSNumberOrNil", referenced from:
      ___SentryNativeBridgeWriteScope_block_invoke in SentryNativeBridge.o
  "__NSBoolOrNil", referenced from:
      ___SentryNativeBridgeWriteScope_block_invoke in SentryNativeBridge.o
  "__NSStringOrNil", referenced from:
      ___SentryNativeBridgeWriteScope_block_invoke in SentryNativeBridge.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

[bitsandfoxes]

Hey @shunia, thanks for raising this. I tried reproducing the issue with the versions you provided but had no luck. Even with the Burst package installed.
Could you provide us with a small repro so we can take a look?

[shunia]

It could be really hard to provide a minimal repro for you guys to look for, but I will try my best.

And btw my exported project is used as a library or a part of the real iOS project, is it possible that the exported project is conflicted with the original iOS project?

[bitsandfoxes]

Unfortunately, this is a use case we don't really support. But it could explain the issue: The SDK manipulates the generated Xcode project and copies that SentryNativeBridge over, to make it all work.

[bitsandfoxes]

Could you try to disable Tools -> Sentry -> Advanced -> iOS Native Support and then build again? This should leave you with only the C# layer.

[shunia]

Unfortunately, this is a use case we don't really support. But it could explain the issue: The SDK manipulates the generated Xcode project and copies that SentryNativeBridge over, to make it all work.

Yes it does, we just can not understand why it would cause compile time error(We are not so familiar with iOS codes though).

Could you try to disable Tools -> Sentry -> Advanced -> iOS Native Support and then build again? This should leave you with only the C# layer.

This will shutdown the objective-c error catching functionality right?
We will definitely try this, and I will be back with the result. Thank you for your help!

[bitsandfoxes]

Yes it does, we just can not understand why it would cause compile time error(We are not so familiar with iOS codes though).

The SentryNativeBridge.m is an additional file that the SDK copies from Unity to the generated Xcode project, allowing the C# layer to communicate with the Cocoa SDK. From your log, it looks like it can't find it.

This will shutdown the objective-c error catching functionality right?

Yes. I guess the surrounding iOS app brings its own Sentry setup?

[shunia]

Sorry it's been a while, we are busy getting stuff done. And it's time we go back to sort out how to integrate Sentry into our existing iOS code base.

Yes. I guess the surrounding iOS app brings its own Sentry setup?

No, never. The iOS project haven't implemented Sentry.

And we have made a little bit change to the file SentryNativeBridge.m to make it pass the compilation:

But it's annoying to have to modify the file after exporting iOS project, how can we make this modification consistent when exporting project?