Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COThank you. But i sporadically get an error with this. `Serious application error. Exception was caught during Core Data change processing. This is usually a bug within an observer of NSManagedObjectContextObjectsDidChangeNotification. -[UITableView scrollToRowAtIndexPath:atScrollPosition:animated:]: row (1) beyond bounds (1) for section (3). with userInfo (null)`. It also sometimes selects the wrong row. Is there another way maybe?
      singulars
    2. COdo you use sections that can be collapsed (hide rows)? if yes then you must check if section to that you insert new row is showing rows, if not then don't execute anything in `case NSFetchedResultsChangeInsert:` or you will get this error, other thing: check if you have insertRowsAtIndexPaths before scrollToRowAtIndexPath, if I call scroll before insert then I get this error too
      singulars
    3. COThis works beautifully, except when the table doesn't actually need to scroll. For example, if the table is scrolled to the top already, and the new row inserted is at the top, then scrollViewDidEndScrollingAnimation is never called. Telling the tableview to select the row in controller:didChangeObject:atIndexPath:forChangeType:newIndexPath: doesn't work either, because the tableview hasn't actually updated yet. A possible workaround may be checking in tableView:cellForRowAtIndexPath to see if the cell being displayed should be selected, but isn't.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload