Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>This is pretty puzzling. Would you try removing the begin/endUpdates:</p> <pre><code>- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath { [self.tableView reloadSections:[NSIndexSet indexSetWithIndex:indexPath.section] withRowAnimation:UITableViewRowAnimationTop]; } </code></pre> <p>I see that the crash is happening in <code>endUpdates</code>, so all the rest that has been executed up to that point has gone flawlessly.</p> <p>Another thing you might try is reloading the whole table by calling <code>reloadData</code> instead of only reloading the sections through <code>reloadSections</code>. This is not as optimized, but since you have few rows it should not matter actually (if it works better)...</p> <p>OLD ANSWER:</p> <p>It seems that one of the objects in your table view is being deallocated and then accessed again. This is a typical "zombie" issue.</p> <p>You can get some clues at what is happening by enabling zombie detection in Xcode.</p> <p><a href="https://stackoverflow.com/questions/5386160/how-to-enable-nszombie-in-xcode">Here you can find out how to enable zombies</a>.</p> <p>If you do, then the error message you get in the console log will offer more information as to which object was deallocated prematurely.</p> <p>I understand that you are attaching a crash log because the crash happens in the field. In this case, you have two options: either reproducing the issue at your side (and fix it with the help of zombies detection); or inspect carefully your memory management to find out any issue with objects displayed in the table view.</p>
 

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