It appears that the rewrite of TableView to use RecyclerView has left a few loose ends. We were shocked to see code that had run for years and years broken. The problem is that the new TableView (and probably ListView) implementations don't handle TableViewRows with child views properly. In particular, say you start by creating TableViewRows which are composed of multiple child views like images and labels and push those TableViewRows into an array. Then you create a TableView and then TableView.setData(TableViewRows). Everything is fine.
Then later you use TableView.setData(TableViewRows) to set new information into the rows. When you do that, [theory] the attributes of the child views of the TableViewRows are zeroed [/theory] so it looks as though the child views have disappeared when the TableView is shown after the setData. But the bottom line is that the child views of the TableViewRow disappear after the setData with SDK 9.3 and above, and the child views continue to be displayed after the setData with SDK 9.2.2 and prior.
I've attached a test program where it creates a TableView with several composite rows with a colored label and image. Then if you click on any row, the TableView has setData applied with the same TableViewRow data array and (voila) the label and image disappear replaced by the title field - they are still children, but they have zero dimensions. Sounds crazy but it is really happening. I won't speculate as to whether this is a deep copy vs shallow copy bug or some other mischief but this really disrupted our release schedule.