Since starting to compile my app with iOS 6 (and since also iOS 7) I\'ve started seeing this message. I know that the way that UITableViews go about managing cells is diffe
I had the same problem and it took me few hours to hunt down the issue. Turns out I was calling [textField becomeFirstResponder]
while setting up cells (here the textField was part of a custom tableviewcell); [textField becomeFirstResponder]
in turns posts keyboardWillShow notification which in turn caused the tableview to prematurely load itself thus causing the infamous "no index path for table cell being reused” message. Once I removed that call, problem disappeared.