Same issue for us on iOS 12.1 as well

Apple Developer Relations Jul 18 2017 Please verify this issue with the macOS 10.13 beta and update your bug report at https://bugreport.apple.com/ with your results.

Apple Developer Relations Jul 24 2017 We believe this issue is resolved in the latest Xcode 9 beta.

Please test with the latest Xcode beta. If you still have issues, please update your bug report with any relevant logs or information that could help us investigate.

Apple Developer Relations Aug 22 2017 Please verify this issue with the Xcode 9 beta and update your bug report at https://bugreport.apple.com/ with your results.

Xcode 9 beta 6 (9M214v) https://developer.apple.com/download/ Posted Date: Aug 21st, 2017

Apple Developer Relations Jul 13 2017 Thanks, we are working on the new information you provided. We appreciate your help!

Rob Mayoff Jul 13 2017 I'm not 100% sure your last update was intended for me. I suspect it was intended for an Apple developer. But I'll do my best.

Regarding glcValidateSender and glcIsEntitlementEnabledForProcessWithAuditToken, those are Apple private API that I'm not calling, so I don't have anything to say about them. SecTaskCopyValueForEntitlement is public but I'm not calling that either.

I discussed this problem with Chris Niederauer at WWDC 2017 and we discovered that you can reproduce the problem using Chess.app. Here are the steps:

1. Launch Chess.app.
2. Attach to the running Chess.app with OpenGL Profiler.
3. Chess.app immediately crashes.

I've attached a crash report from Chess.app.

Do you need anything else from me? I'm not sure I can provide any more details.

Apple Developer Relations Jul 13 2017 Could you provide more details on the failure? Specifically, it looks like the glcValidateSender() function is failing, but that could fail for several reasons. One of those reasons is that glcIsEntitlementEnabledForProcessWithAuditToken() fails which ultimately could mean that SecTaskCopyValueForEntitlement() is failing.

We would need to know exactly what part of this code is failing before diagnosing.

Please provide your response or results by updating your bug report. If uploading files, please compress first.

Rob Mayoff Jun 9 2017 The OpenGL Profiler that is included in Additional Tools for Xcode 9 beta 1 works (doesn't crash my app) in macOS 10.12.5 but still fails (crashes my app) in macOS 10.13 beta 1.

Apple Developer Relations Aug 14 2017 We believe this issue has been resolved in the latest macOS 10.13 beta.

Please test with the latest beta. If you still have issues, please update your bug report with any relevant logs or information that could help us investigate.

macOS https://developer.apple.com/download/

Apple Developer Relations Aug 8 There are no plans to address this based on the following:

We don't plan on exposing these colors. the correct fix is just to support custom height headers.

We are now closing this report.

If you have questions about the resolution, or if this is still a critical issue for you, then please update your bug report with that information.

Please be sure to regularly check new Apple releases for any updates that might affect this issue.

Apple Developer Relations Oct 22 We’ve made a number of changes in this area in 10.14 as all AppKit controls are now using NSTypesetterBehavior_10_4 by default. For compatibility purposes, the baselines of controls using the previous default setting, NSTypesetterBehavior_10_2_WithCompatibility, will not change.

Additionally, it’s not really expected that the visual baseline of all text field configurations are in the same place:

• Bezeled NSTextFields are using specific artwork and the baseline will be visually aligned within the boundaries of the bezel artwork. This may not be the same as the “raw” baseline value as determined by the text measurement.
• Bordered NSTextFields have historically had a different baseline. In 10.14, stock bordered NSTextFields will have baselines that are visually aligned with square bezeled NSTextFields, but subclasses of NSTextField will continue to use the historical baseline for compatibility purposes.
• Un-bezeled and un-bordered NSTextFields have no visual boundaries and will use the “raw” baseline value as determined by the text measurement.

In an attempt to bump up the priority on this (since it sounds like it's as simple as a missing recalculation of visible content), I've also filed https://bugs.webkit.org/show_bug.cgi?id=192564

This seems to have been solved/improved in iOS 12.1.1

I suggested sending the CSSearchableItem instead or in addition to the uniqueIdentifier in preparePreviewOfSearchableItem. Spotlight already has this information and I don't see any reason why it shouldn't pass it on to the QLPreviewingController. Passing just the uniqueIdentifier means in most cases that a network request has to be made to fetch the details, worsening the UX.

Engineering has provided the following feedback regarding this issue:

Queries on uniqueIdentifier are explicitly not supported.

Adding CFNetwork to your linked frameworks should fix this issue.

I'm sorry but this is not "intended behaviour" - if you don't want to change the behaviour of @encode, then you should fix the implementation of CLLocationCoordinate2D so that it also has a tag name which is the same as it's typedef name. Because of this problem, CLLocationCoordinate2D breaks when you try to use NSKeyedArchiver. I can workaround the issue by manually wrapping up the values manually, but I shouldn't have to. Somebody else came across the same problem here: http://stackoverflow.com/questions/12291279/nskeyedarchiver-fails-with-cllocationcoordinate2d-structs-why

Engineering has determined that this issue behaves as intended based on the following information: symbol before '=' is the tag name and not the typedef name (which happen to be the same in your test). And '?' encodes that there is no tag name. In other words, encoding should be identical to: @encode(struct { double aDouble; double anotherDouble; }); Any change to encoding to include typedef name will break ABI compatibility. If you have questions regarding this resolution, please update your bug report with that information. We are now closing this bug report. Please be sure to regularly check new Apple releases for any updates that might affect this issue.

https://openradar.appspot.com/46487252

https://openradar.appspot.com/46465917