The WWDC '17 session for core spotlight said QLSupportsSearchableItems is only for "shoebox" apps and explicitly said it's not for document-based apps, but when trying to upload my UIDocumentBrowserViewController-based MacCatalyst app with a quicklook extension (the view-controller-based quicklook preview works great) to App Store connect, it prevents me from uploading without a QLSupportsSearchableItems keys in my quicklook extension's info.plist, and it prevents me from uploading it if the value is false (0). Is the app store validator correct, and I must have this key and it must be true? Do I have to implement func preparePreviewOfSearchableItem(identifier, and if so, can I just have it always fail? If it can't fail, how would I get a sandbox url for the document from a searchable item identifier? Also, Xcode won't find anything when I search for QLSupportsSearchableItems, which is not so much ironic as it is face-palmy.

My UIDocumentBrowserViewController-based Mac Catalyst app shows the "open window" when launched; fine. but there is also a blank document window. Once I pick a document, and present my document view controller over my UIDocumentBrowserViewController subclass, the window is filled with the documents contents. How do I get it to hide the blank window behind it?

The documentation for SKTerminateForInvalidReceipt() says"Terminates an app if the license to use the app has expired."And I really didn't want to go to all the trouble to code up all that bit about mnaually verifying receipts, because I don't think pirating my app is that useful, so I just had the prod version of my app call the SKTerminateForInvalidReceipt().However, AppReview says they installed a valid receipt and my app always crashed.So... are the docs right, and SKTerminateForInvalidReceipt correctly detected that AppReview did not install a valid reciept, or is AppReview right, and SKTerminateForInvalidReceipt does not effectively correctly validate recipts, and crash "if the license to use the app has expired."?

In my iOS apps, I can get a list of the current UIScreens, but it seems in macOS 10.15.0 GM in macCatalyst, this never happens?UIScreen.main has the wrong sizes, for all properties related to the size of the screen.When I plug in an external screen, I don't get the did connect or did disconnect notifications, and UIScreen.screens still has only 1 screen.When I drag my window to the other screen, I get a did change mode notification.UIScreen was such a nice api on iOS, and so much cleaner than the api's on mac, that I thought it would be easy to port my app which uses a full-screen external screen feature, but now it appears there is no external screen support at all, other than the user can drag the windows there?I even tried adding a UIWindowSceneSessionRoleExternalDisplay scene, to see if that would unlock some kind of functionality, and though I'm able to trigger it manually in code, I don't see any other changed behaviors. No automatic initialization of the scene when the external display, no automatic placement of the window in the external screen.Identical results when useing SideCar.Am I seriously stuck using CGGetOnlineDisplayList ?