Not sure if this is a known issue. I tried creating a TableView where each row contains a label and a ScrollView of images.
It works fine initially, though I do get the "looks like we have a different table cell layout…" warning even though I've verified my table rows all have unique className's.
Once I have more than 2 entries in the table and I scroll to the bottom the app crashes with this error:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[UIScrollView transferProxy:]: unrecognized selector sent to instance 0x527cc50'
When I remove the ScrollView from the table rows it no longer crashes. Seems has if the className isn't being respected when the row contains a ScrollView.
I've got crashes too when I use scrollview and add invalid objects to it.
scrollview.add( object );
where object is invalid or undefined.
Check that every argument you pass is valid and defined.
Thanks for getting back to me Peter. The objects passed in definitely have valid data, everything works fine and all elements are clickable until I start scrolling.
Invalid data also wouldn't explain the "different table cell layout" warning either I don't think.
I was able to reproduce this with a trivial case based off of a completely new project. It didn't crash but it produced the "different table cell layout" warning as well.