Yes, I think your scenario is correct. I think it is a bug that after sharing is stopped records are not moved back to the default CoreData zone and the zone is not removed. So the next time I try sharing it, the SDK most likely checks if it's already in a shared zone and tries to share the same zone with other objects as well.The workaround would be to delete shared objects once the sharing is stopped. Then we can recreate them back in the default zone using core data. It's seriously ALPHA ver!

I think users will blame me, not Apple for wiping out their data :D. That's the problem.

I can confirm the trick with recreating records after the sharing is stopped works well. But the error "Invalid Arguments" (12/2006); server message = "Only shared zones can be accessed in the shared DB"; op = EB5068F104AA2536; is generated always when the sharing is stopped (even without the workaround). Something is broken with the SDK.

Replied below

I'm referring iOS, but this happens on all platforms and projects. This is a well-known issue that incremental builds using xcodebuild are significantly slower than builds using Xcode. I can't share my projects, but you can easily reproduce it on any Xcode project. I already have a ticket for that: FB15478221. I put there all necessary details to reproduce the issue.

I found a similar issue: https://forums.developer.apple.com/forums/thread/756120 The full root cause and the workaround are described there... In my case also the problem is with xcodebuild command being stuck for 15-20s on "GatherProvisioningInputs" step.

I posted more details here: https://github.com/wojciech-kulik/xcodebuild.nvim/issues/201#issuecomment-2423828065

xcrun xccov view --archive --file filepath xctestresultPath

Devs experience is unfortunately their lowest priority, so I wouldn’t expect any fix in this matter. For sure not ASAP.