Is the camera supposed to show up on the simulator?


#1

I don’t see the camera on the detail view on the simulator, yet on the phone I see it and it works. I am using 5s so the phone should be big enough. There doesn’t seem to be a way to add an attachment, but the bottom of the detail screen is empty. Nada. Just wondering if this is correct for the simulator? If not, any ideas what’s wrong?

thanks


#2

I found out if a drag the toolbar off the bottom of the screen it will display properly on the simulator in that the toolbar hugs the bottom of the screen. But then when it displays on the phone the tool bar is hight up the screen, which makes sense, because that’s what it looks like in IB. Here’s what it looks like: farm6.staticflickr.com/5551/150 … 47cc_o.png.

Any ideas?

thanks


#3

For starters, the toolbar should not be moved off the bottom. It’s more important to display properly on the phone.

I see that first behaviour (proper on the 5, camera hidden in the simulator) only after removing the vertical constraint for the toolbar, then simulating the smaller, 3.5" phone.

So…move the toolbar back to the bottom in IB, and add the missing vertical constraint (0 from the bottom of the screen) for the toolbar.


#4

Agreed, the phone is most important. I have absolutely no constraints, but I still get constraint errors. It’s possibly related to the problem I’m seeing, but I really can’t figure it out. The debug output:

2014-09-18 21:30:39.072 Homepwner[36578] imageForKey: key=62CF12B3-7A02-4B14-9A3D-268EDC0B247C
2014-09-18 21:30:39.086 Homepwner[36578] Unable to simultaneously satisfy constraints.
Probably at least one of the constraints in the following list is one you don’t want. Try this: (1) look at each constraint and try to figure out which you don’t expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you’re seeing NSAutoresizingMaskLayoutConstraints that you don’t understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
"<NSLayoutConstraint:0x7c710a20 V:[UILabel:0x7c710910’ff’(21)]>",
"<NSLayoutConstraint:0x7c710ea0 V:[UILabel:0x7c710910’ff’]-(1)-| (Names: ‘|’:UITableViewCellContentView:0x7c70ff00 )>",
"<NSLayoutConstraint:0x7c710f00 V:|-(20)-[UILabel:0x7c710910’ff’] (Names: ‘|’:UITableViewCellContentView:0x7c70ff00 )>",
"<NSLayoutConstraint:0x7c71b710 ‘UIView-Encapsulated-Layout-Height’ V:[UITableViewCellContentView:0x7c70ff00(43.5)]>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x7c710a20 V:[UILabel:0x7c710910’ff’(21)]>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful.

But there aren’t any constraints. And hitting the breakpoint didn’t tell me a lot.