Bryan Jones

@leemaguire I originally thought the crash was related to the new property wrapper syntax, so I rolled my project back to a commit before I switched to @Persisted. The same...

@leemaguire I assume you're adding the objects to a Realm before deleting them? In further testing, it appears this issue manifests only once a substantial number of objects are being...

Confirming that this remains an issue in Realm 10.17.0. I ran into it again today because I added a new collection property called "groupedCues" and forgot to nuke that collection...

The crash message has changed slightly. It was something like: `no key of 31 found on masterCue_class`. I'd reproduce it again to get the exact message, but this crash corrupts...

I can try, once I get some free time. This crash occurred in an app I built for a client and their data scaled to millions of relationships. If I...

Again, the REST of the app works 100% fine. It's **only** the SwiftUI-driven part that is crashing with this exception.

I've tried opening the realm separately using `@asyncOpen` (rather than passing in the realm I've already opened on `ModelController`) and I get the exact same crash: What am I missing?

I *do* see this block in the documentation, but it's unclear if it applies to synced Realms: https://www.mongodb.com/docs/realm/sdk/swift/examples/swiftui-guide/#swiftui-realm-migrations I was under the impression that migrations were **not** required for synced...

Adding a `schemaVersion` to my config had no effect. Same crash. ``` var config = self.realmApp.currentUser!.configuration(partitionValue: self.globalPartitionKey, clientResetMode: .discardLocal(nil, nil)) config.schemaVersion = 2 ``` This config is used to open...

Okay, so if I store the **configuration** that I use to open my synced realm in `modelController` (the AppKit-based controller), ensure there's a `schemaVersion` in that configuration, then pass that...