use [RLMResults count] in Realm notification listener crash

[chenyanping01]

How frequently does the bug occur?

Sometimes

Description

Stacktrace & log output

No response

Can you reproduce the bug?

-- select --

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 17.4.1

Build environment

Xcode version: ...
Dependency manager and version: ...

[sync-by-unito]

➤ PM Bot commented:

Jira ticket: RCOCOA-2337

[chenyanping01]

The code:

let messagesList = getRealm(for: Message.self).objects(Message.self).filter(predicate) //get messages from realm db
if notificationToken == nil {
      notificationToken = messagesList.observe(keyPaths: [\Message.isRead]) { [weak self] (changes: RealmCollectionChange) in
         switch changes {
         case .initial:
              print("[notificationToken] initial")
          case .update(let results, _, _, _):
              print("[notificationToken] update")
              let count = results.count // **_Crash here!!!_**
              updateUI(count)
                    
          case .error(let error):
              print("[notificationToken] error")
                
          }
      }
}

deinit {
        notificationToken?.invalidate()
        notificationToken = nil
 }

[nirinchev]

Do you think you can extract a minimal repro that we can use to investigate? There's nothing obviously wrong with your code or the calls mentioned in the stacktrace, so it's not clear what could be causing the crash. If we had a repro we could debug, that would go a long way to fixing it.

[Jaycyn]

Can you include the code for this getRealm(for: Message.self)?

Is this a local or sync'd realm

Are you using any kind of threading, await/async or @Actor?

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.