Link error with Xcode 12.3

[pfvernon2]

The following error is generated when building ObjectBox projects with Xcode 12.3. I do not see this error when building with previous releases of Xcode.

error: Building for iOS, but the linked and embedded framework 'ObjectBox.framework' was built for iOS + iOS Simulator. …

Basic info:

• ObjectBox version - 1.4.1 - Manual setup, no CocoaPods or Carthage
• Reproducibility - Always in Xcode 12.3, never in previous releases
• Device: iPad Pro 12.9 3rd Gen, x86 Simulator
• OS: iOS 14.3, macOS 11.1

Steps to reproduce the behavior:

1. Build project with Xcode 12.2
2. Note success
3. Build project with Xcode 12.3
4. Note error

Expected behavior:
Expect successful build (link) in Xcode 12.3 as with previous Xcode releases.

Logs, stack traces:

Showing All Messages

Prepare build
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Using build description from memory

Build target … with configuration Debug
error: Building for iOS, but the linked and embedded framework 'ObjectBox.framework' was built for iOS + iOS Simulator.…

Build failed    12/15/20, 8:51 AM    0.1 seconds

Additional context:

• I have reinstalled Xcode 12.2 under macOS 11.1 and confirmed that my project builds as expected. This appears to be specific to Xcode 12.3.
• Note that I am NOT using either CocoaPods or Carthage. This was a 'manual' setup of ObjectBox.

[krzyzanowskim]

How did you integrate the framework? The error message sounds like a missing strip frameworks phase for this kind of framework (something that is handled automatically by eg. CocoaPods machinery) but maybe it's something different.

Is it possible that you recreate this setup with a sample project and attach it here for further investigation?

[pfvernon2]

Thank you for looking into this.

See example project attached. This project builds and runs as expected under Xcode 12.2 but fails as above under 12.3.

The project was created with Xcode 12.2 on macOS 11.1 using your manual setup instructions.

Note that in addition to the documented manual setup process I was also required to disable 'Enable Bitcode' in Build Settings->Build Options. This is something I have always been required to do with manual setups that I have not found documented in your manual setup instructions.

The remainder of the example code was copy/pasted from your getting started tutorial. It can be found in AppDelegate::didFinishLaunchingWithOptions.

ObjectBox Test.zip

[krzyzanowskim]

Thanks! We're aware of the problem and will address that in one of the upcoming updates.

For now, you can use this xcframework solution I prepared manually for you:

ObjectBox-xcframework-1.4.1.zip

Link your project with ObjectBox.xcframework from the archive in the place of ObjectBox.framework

I updated a test project with this setup: ObjectBox xcframework Test.zip

[pfvernon2]

Thank you! This seems to be working well.

[greenrobot]

@pfvernon2 the just released 1.5.0-rc should fix this officially. Would be great if you could confirm.

[pfvernon2]

Thanks for the heads-up. This appears to be working fine in my manual install work flow.

One minor issue is that I no longer have the traditional framework icon in the file browser but this do not appear a problem.

[greenrobot]

Great, thanks for the feedback! So we can close this.