Paul, I haven’t heard anything back but I did take a deeper look in here because the code in the app was extremely messy and was telling me that there’s probably an issue regarding app design and UX occurring here to result in code output such as your app has currently on build. I wanted to know why so I dug in more myself. A big issue here is when you begin to nest tableviews into the cells of other tableview’s, you’re going to get yourself into trouble and that’s what is happening here. The big issue in your case is that you’re breaking this rule on a pretty extreme level in your current design.
When you try to navigate to new pages from within nested tableviews, the code we’re writing on the backside is going to begin to fail. It has to do with what ViewController is considered the parent view controller within a very deep element hierarchy. Your pages are beautiful but they are failing to follow mobile UX design guidelines. The moment you have dynamic data elements inside dynamic data elements, our platform will quickly become ill-equipped to handle this as it’s not a standard norm unfortunately.
A telltale sign that you’re going down a non-recommended and/or highly customized path is when you begin to see “same direction scrolling elements” within and atop each other. You have tableviews that fill the screen of the phone but then within them are cells that nest other tableviews that scroll the same direction. The phone and the user will have a difficult time differentiating what the user wants to do when the user scrolls with a finger atop nested scrolling items and this is why it becomes a bad practice, an unrecommended ux pattern, and against standard mobile design guidelines. it’s not to say it’s “wrong” because design is subjective, but it is moving into a much more “custom design” and that’s where our platform is going to begin to fail you and increasingly so if you stay the course.
The correct answer here is not an easy one to accept, especially as far along as you are but a heavy adjustment in your app’s design is actually the recommended action here. I highly recommend pausing for a moment to replan your implementation and make a large course correction. You should implement a strategy that doesn’t involve tableviews inside of other tableviews and I recommend breaking out the logic and exploration to either having more pages with single tableviews within each page, or perhaps a design from a higher level that sets the user down a path to get to the end information in a more efficient manner by having them first pick from a high level “route” like putting them into a “My News”, or “My Documents” or “My Apps” page by themself so that digging into the content is a more direct route from that point forward.
Again, not a tough pill to swallow as your app seems quite mature but I’m actually pretty shocked you made it as far as you have without issues. The nesting and tableviews within tableviews you’ve created here in the quantity that you have is not going to be manageable and we’re not going to be able to help you very much either as our platform simply isn’t prepared to break mobile design guidelines to this extent.