Question posted in Xcode
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level
2
Answers
It turns out it was not the stack or containers but the constraints on a separate view itself that I embedded in the last container. The constraints on the containers and stack work great.
You have force-dictated the heights of the Container Views 2-5, so there is no reason why they would, taken together, fill the height of the device.
To see this, simply imagine that Container View 1 has a height of 10. Then the other views have a combined height of 67.5, for a grand total of 77.5, which obviously would be smaller than the height of any known device.
Basically this appears to be an incorrect use of a stack view. You don’t give any information about how the stack view is configured, so it’s impossible to say more at this point. I’m a little surprised, though, that you do not report getting some sort of constraint conflict message in the Xcode console.