anatomybook

Thanks for considering my proposal.

Sadly enough, I'm also still seeing it. At this point, I don't have a way to reproduce it, but users have complained about the syncing going bad. I've determined the...

@atierian Ok. Thanks for your answer! Here it is: ``` Thread 1 Queue : com.apple.main-thread (serial) #0 0x00007fff6faac0ea in __ulock_wait () #1 0x00007fff6fafa27e in _os_unfair_lock_lock_slow () #2 0x00007fff6f711eb8 in gcd_queue_item_enqueue_hook...

I'd like to add, that it takes precisely the same dataset, that is needed to trigger https://github.com/aws-amplify/amplify-ios/issues/1864. So somehow this seems to be related.

Something I just noticed and to avoid confusion when you follow the trace above: In ModelSyncedEventEmitter.swift, there's an offset of 6 lines, since my commented hack was in there. For...

Hello @lawmicha , sorry for my delayed reply. Here's my schema - slightly edited: ``` type ActorZ @model @auth(rules: [{ allow: owner }]) { id: ID! . . . myContents:...

> Could you try and reproduce the deadlock again using `fix/modelsynced-sync-finished` branch? I just tried. Everything works - no more deadlock! It'd be awesome if that made it into main....

> Keeping this issue open to look into the schema you've provided @lawmicha - thanks for the inclusion of my suggestion. Please let me know if you have any questions...

@lawmicha , any hint is appreciated. Thank you!

@chrisbonifacio Thanks for your answer and sorry also for the delay on my side. The data, that's being synced isn't all that much. All in all, it's only a few...