Key '413' not found in 'ClassName' when nullifying incoming links

[chenyanping01]

How frequently does the bug occur?

Sometimes

Description

When the App starts, we need to delete the expired data in the database asynchronously. Then this issue happens sometimes. What's the cause of this issue?
How do I debug this problem?
There is a similar ticket: realm/realm-kotlin#1537

Stacktrace & log output

Fatal Exception: RLMException
0  CoreFoundation                 0xecb28 __exceptionPreprocess
1  libobjc.A.dylib                0x2af78 objc_exception_throw
2  Email                          0x1b3e618 RLMThrowCollectionException(NSString*) + 101 (RLMResults.mm:101)
3  Email                          0x1b40718 -[RLMResults deleteObjectsFromRealm] + 63 (RLMResults_Private.hpp:63)
4  Email                          0x1b391c8 -[RLMRealm deleteObjects:] + 928 (RLMRealm.mm:928)
5  Email                          0x8a0efc specialized closure realm/realm-swift#1 in DB.delete<A>(_:)

Can you reproduce the bug?

No

Reproduction Steps

No response

Version

10.49.1

What Atlas Services are you using?

Local Database only

Are you using encryption?

No

Platform OS and version(s)

iOS

Build environment

Xcode version: Xcode 15.3
Dependency manager and version: Cocoapods 1.15.2

[sync-by-unito]

➤ PM Bot commented:

Jira ticket: RCOCOA-2335

[Jaycyn]

The question states we need to delete the expired data - does that mean the app is attempting to delete data and then a crash occurs? Can you provide the code that replicates that issue?

[chenyanping01]

Thanks.
Yes. the app is attempting to delete data and then a crash occurs.
The Crash log is from production release from Firebase. We can't reproduce it locally.

[sync-by-unito]

➤ PM Bot commented:

Jira ticket: RCORE-2088

[Jaycyn]

It's going to be challenging to track this down without some kind of duplicatable example.

There have been numerous issues reported with Realm which were actually caused by other third party libraries, outdated SDK's or even environmental issues. The only way to narrow that down is with code that produces the issue.

Can you please update your report with the code you're running that's causing the crash along with a bit more info in the stack trace as what's in the question doesn't really provide enough details.