By any chance do we know if there are any known issues that might lead to false positive errors when using the ConcurrencyDebug argument with SwiftData? I am seeing some concurrency errors with a SwiftData stack… but I'm looking through how this stack is set up and I can't understand what could be leading to any kind of race condition.
Wrong comment thread… this was meant for the previous comment. Sorry about that!
vanvoorden
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
By any chance do we know if there are any known issues that might lead to false positive errors when using the ConcurrencyDebug argument with SwiftData? I am seeing some concurrency errors with a SwiftData stack… but I'm looking through how this stack is set up and I can't understand what could be leading to any kind of race condition.
FWIW… I am creating a ModelContext on an actor (and all queries and mutations go through that actor as serial operations). Is that ModelContext somehow "thinking" it belongs on main (which then throws an error later when the actor performs a serial operation)?
Sounds good. Thanks!
I am still a little unclear about some of these details… would I have the option to request a little more hands on support for this topic with DTS? My previous DTS request was 2023-10-27 and AFAIK I still have not heard back from Apple other than the automated replies. Is there any expected SLA estimate for a topic like this State question? If I requested a new DTS would I have the option for you specifically to be the engineer to help work on that request? Thanks!