You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Object._getProperties() and EmbeddedObject._getProperties() are annotated with @MainActor, but if you initialize Realm from a background thread. For example, using DispatchQueue.global().async. These methods will be called from the same thread that was used to initialize Realm.
It happens only if you build Realm as a debug build via Carthage, because you set SWIFT_STRICT_CONCURRENCY to complete.
I would either expect Realm.init to be on the main actor too or the methods not requiring the main actor.
Can you reproduce the bug?
Always
Version
v10.38.3
What Atlas Services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
iOS 16.4
Build environment
Xcode version: 14.3
Dependency manager and version: Carthage - Locally built Debug build
The text was updated successfully, but these errors were encountered:
How frequently does the bug occur?
Always
Description
Object._getProperties()
andEmbeddedObject._getProperties()
are annotated with@MainActor
, but if you initialize Realm from a background thread. For example, usingDispatchQueue.global().async
. These methods will be called from the same thread that was used to initialize Realm.It happens only if you build Realm as a debug build via Carthage, because you set
SWIFT_STRICT_CONCURRENCY
tocomplete
.I would either expect
Realm.init
to be on the main actor too or the methods not requiring the main actor.Can you reproduce the bug?
Always
Version
v10.38.3
What Atlas Services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
iOS 16.4
Build environment
Xcode version: 14.3
Dependency manager and version: Carthage - Locally built Debug build
The text was updated successfully, but these errors were encountered: