ObjectMonitor no longer sending didUpdateObject: changedPersistentKeys: #9

Closed
opened 2025-12-29 15:21:58 +01:00 by adam · 4 comments
Owner

Originally created by @PaulWoodIII on GitHub (Aug 20, 2015).

I'm on the xcode7 alpha branch and following you while you work, so I understand if you are going to get to it but my ObjectMonitor is no longer receiving this callback.

I looked into the NSFetchedResultsController used for the ObjectMonitor and instead of .Update its sending a .Move NSFetchedResultsChangeType. I think thats where I'll start in my debugging of this

Originally created by @PaulWoodIII on GitHub (Aug 20, 2015). I'm on the xcode7 alpha branch and following you while you work, so I understand if you are going to get to it but my ObjectMonitor is no longer receiving this callback. I looked into the NSFetchedResultsController used for the ObjectMonitor and instead of .Update its sending a .Move NSFetchedResultsChangeType. I think thats where I'll start in my debugging of this
adam added the corestore bug label 2025-12-29 15:21:58 +01:00
adam closed this issue 2025-12-29 15:21:59 +01:00
Author
Owner

@JohnEstropia commented on GitHub (Aug 21, 2015):

I'm currently fighting with this as well, but this is not just a problem in the ios7_support_alpha branch. This also happens on any branch built with the iOS 9 SDK and only on iOS 9 devices/simulators, so it's either a bug on iOS 9, a bug on the latest XCode, or an inteded behavior change we may need to handle with if #available()'s.

@JohnEstropia commented on GitHub (Aug 21, 2015): I'm currently fighting with this as well, but this is not just a problem in the ios7_support_alpha branch. This also happens on any branch built with the iOS 9 SDK and _only on iOS 9 devices/simulators_, so it's either a bug on iOS 9, a bug on the latest XCode, or an inteded behavior change we may need to handle with `if #available()`'s.
Author
Owner

@JohnEstropia commented on GitHub (Aug 21, 2015):

Seems related: https://forums.developer.apple.com/thread/4999

@JohnEstropia commented on GitHub (Aug 21, 2015): Seems related: https://forums.developer.apple.com/thread/4999
Author
Owner

@JohnEstropia commented on GitHub (Aug 23, 2015):

@PaulWoodIII I pushed a temporary fix for ObjectMonitor so that it will somehow still be usable. A couple of problem still persists:

  1. ObjectMonitor may send update events even if no updates actually occurred
  2. ListMonitor may send willChange and didChange events even if no updates actually occurred. This will cause UITableView.endUpdates() to fire an assertion failure if no other UITableViewCell updates were made after UITableView.beginUpdates().

We'll need to wait how Apple fixes this bug on the next XCode build. You can follow updates from this thread: https://forums.developer.apple.com/thread/4999

@JohnEstropia commented on GitHub (Aug 23, 2015): @PaulWoodIII I pushed a **temporary** fix for ObjectMonitor so that it will somehow still be usable. A couple of problem still persists: 1. ObjectMonitor may send update events even if no updates actually occurred 2. ListMonitor may send willChange and didChange events even if no updates actually occurred. This will cause `UITableView.endUpdates()` to fire an assertion failure if no other UITableViewCell updates were made after `UITableView.beginUpdates()`. We'll need to wait how Apple fixes this bug on the next XCode build. You can follow updates from this thread: https://forums.developer.apple.com/thread/4999
Author
Owner

@PaulWoodIII commented on GitHub (Aug 23, 2015):

thanks @JohnEstropia I'll test things out this afternoon myself

@PaulWoodIII commented on GitHub (Aug 23, 2015): thanks @JohnEstropia I'll test things out this afternoon myself
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/CoreStore#9