Closed KillianSmith0 closed 2 months ago
➤ PM Bot commented:
Jira ticket: RCOCOA-2426
This generally means that you've managed to link two different copies of Realm into your app, which results in two different RealmSwiftObject classes which aren't compatible with each other.
Thank you for the response!
That is interesting, considering its fine in Xcode 15.x We are leveraging tuist so maybe its an Xcode 16 issue with their tooling 🤔
I'll try look into it further, thank you
This seems to be a non-issue on Xcode 16 RC1. Will close, thanks for support!
How frequently does the bug occur?
Always
Description
I am running Xcode 16 beta 6, and have not been able to get the latest release to compile with this Xcode version. As a result I am building the package from source through SPM
The problem
We are providing a list of
objectTypes
to theRealm.Configuration
initializerAll these objects conform to
RealmSwift.Object
, even while outputting in the terminalpo (BodyParts.self is RLMObjectBase.Type)
, the result is trueHowever, the compiler crashes when the
objectTypes
are accessed with the following errorI have also tried using defaultConfig without providing
objectTypes
explicitly, but the SDK doesn't automatically pick up the objects as mentioned here.Stacktrace & log output
Can you reproduce the bug?
Always
Reproduction Steps
Version
10.53.1
What Atlas Services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
iOS 18
Build environment
ProductName: macOS ProductVersion: 15.0 BuildVersion: 24A5327a
/Applications/Xcode-beta.app/Contents/Developer Xcode 16.0 (beta 6) Build version 16A5230g
pod not found (not in use here)
/bin/bash GNU bash, version 3.2.57(1)-release (arm64-apple-darwin24)
carthage not found (not in use here)
/usr/bin/git git version 2.39.5 (Apple Git-154)