is it possible to use com.apple.CoreData.ConcurrencyDebug but only log the errors

if it set com.apple.CoreData.ConcurrencyDebug 1 as launch arg the app always crashes and i cant proceed into the app. is there a way to only raise a warning for these issues so that i can go into the app and check every place in one session for coredata errors?

Answered by DTS Engineer in 828678022

I don't see any way to change the behavior of com.apple.CoreData.ConcurrencyDebug. The current behavior crashes at the point where a Core Data concurrency violation is detected, and from there, you can analyze this specific violation by looking into the frames in the stack trace. That is the intentional use of the launch argument.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

I don't see any way to change the behavior of com.apple.CoreData.ConcurrencyDebug. The current behavior crashes at the point where a Core Data concurrency violation is detected, and from there, you can analyze this specific violation by looking into the frames in the stack trace. That is the intentional use of the launch argument.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

is there any way to find violations without crashing the app.

is it possible to use com.apple.CoreData.ConcurrencyDebug but only log the errors
 
 
Q