Beginning Table Views · Conclusion | Ray Wenderlich

This is a companion discussion topic for the original entry at

Hi Brian,
thank you for this great journey together: I got this warning in the console:

[Warning] Warning once only: Detected a case where constraints ambiguously suggest a height of zero for a tableview cell’s content view. We’re considering the collapse unintentional and using standard height instead.

Could you please tell me what may be causing it?
And possibly how to fix it?

Thank you so much!

@bdmoakley Can you please help with this when you get a chance? Thank you - much appreciated! :]

Sometimes different devices will cause issues with constraints. This is where adaptive layout comes into play. I’m guessing that’s the kind of issue you are running into. The way to fix it is to test the app on a variety of different sized devices and create size classes for specific issues. You may want to check out our course on auto layout if you aren’t familiar with size classes. You can find it here:

thank you Brian.
The main point of my question was: “What caused this if I just followed your instructions from beginning to end?”
Until now I have only built interfaces for iPhone XS (or XR or XS Max) and never had this issue before.

Thank you.
PS: I will check that course for sure!

I focused on developing the app on just one advice so as to not get in the weeds with auto layout. That issue probably exists at the start of the tutorial, and you switched devices in the simulator. That’s my guess, anyhow. In any case, I’ll do some research to see how we can work around it in the future.