10.12 Regression: QLPreviewPanel always logs about AutoLayout issues

Originator:jonathan
Number:rdar://28466021 Date Originated:9/25/2016
Status:Open Resolved:
Product:macOS Product Version:10.12
Classification:Other Bug Reproducible:Always
 
Summary:
QLPreviewPanel on macOS 10.12 Sierra will always log about AutoLayout issues when it is invoked.  It does not appear as a developer there is anything we can do about this.

Steps to Reproduce:
1. @import Quartz; and then call [QLPreviewPanel sharedPreviewPanel]

Expected Results:
The sound of silence.

Actual Results:
There is always this log:

"2016-09-25 10:07:33.341804 QLPreviewPanelBug[9792:528062] [Layout] Detected missing constraints for <private>.  It cannot be placed because there are not enough constraints to fully define the size and origin. Add the missing constraints, or set translatesAutoresizingMaskIntoConstraints=YES and constraints will be generated for you. If this view is laid out manually on macOS 10.12 and later, you may choose to not call [super layout] from your override. Set a breakpoint on DETECTED_MISSING_CONSTRAINTS to debug. This error will only be logged once."

Because our app checks to see if the preview panel is visible as part of an event chain override, this message is logged immediately when our app launches on every single launch.  Having unnecessary logging makes it hard to identify legitimate problems/debug/deal with xcode popping stuff up/etc.

Version:
10.12 GM and 10.12.1 beta (16B2327e)

Notes:
This affects Tumult Hype (http://tumult.com/hype/).

Comments

Related issue when calling NSAlert.layout()

See my radar http://www.openradar.me/28700495 which describes another case when the system generates this message.

By rsfinn at Oct. 25, 2016, 8:31 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!