So I can make the search bar and scope bar look reasonable by setting UISearchBar's backgroundImage and scopeBarBackgroundImage properties to a image of just a solid color, but my app also sets navigationItem.prompt when the UISearchController is active, and the background color of that view _UINavigationBarModernPromptView is white... Edit: setting UINavigationBarAppearance's backgroundColor allows me to get override the white background.

Also not sure why focus moves to the first row (0,0) when another row is collapsed with the selected and focused row. If the collapsed parent (just clicked) isn't selectable but is focusable the focus should move to the clicked row. IMO it shouldn't jump to index path 0,0. Overriding this behavior is not as straightforward since the focus API gives developer's limited control. I have to hold the clicked index path in a property and return it from -indexPathForPreferredFocusedViewInCollectionView:

Actually I get the behavior I expect by default as long as the selected row isn't also focused (the collection view is configured to have the selection follow focus, which is something I want). Only thing I can think of is to manually implement the expandable row's UICellAccessoryOutlineDisclosure actionHandler, set selectionFollowsFocus to NO before I collapse the row, then set selectionFollowsFocus to YES after the animation finishes. Feels like this is way more work then it should be though.

So I deleted the "Push Notifications" entry in "Signing and Capabilities" then added it back. Remote notifications are working again. 🤷‍♂️

I duped this thread in a feedback: FB11689969

Maybe it's not possible? I just tried to do it in the "Developer" app which I believe is a Catalyst app and it won't collapse the sidebar via drag. Notes, Mail, Xcode, Finder, etc. all allow you to collapse the sidebar by dragging the split.

I did open a feedback on this: FB11681351 duplicating the information I provided in this thread.

I think if figured out what's going on. On launch my app needs to determine whether or not it should show onboarding UI based on a few conditions. While my app is making this determination, I overlay a separate UIWindow in the UIWindowScene that shows a UIActivityIndicatorView. Then if I do in fact have to show the onboarding UI, this overlayed window shows the onboarding view controller by presenting it modally. Underneath this overlayed window is my standard UIWindow. In that window hierarchy underneath there is a UINavigationController with navigation bar. It appears UIKit on macOS draws this separator line underneath the navigation bar when the window is in certain states...but the separator is bleeding through from the UIWindow that's offscreen. That UIWindow should be completely offscreen while the overlay window is the key window (and it is, except for the line separator bleeding through and causing this glitch). So if I do this: #if TARGET_OS_MACCATALYST     [self setNavigationBarHidden:YES animated:NO];     #endif The line separator issue goes away.

The separator snaps into place after I resize the window....anyway I can programmatically force the window to relayout the separator? The request geometry update method isn't released yet (I guess it will be released when iPadOS 16 comes out?)

Whaaat I can't delete a keyword. It's 2022 this thread was created six years ago? Thanks for caring Apple.

How is Basic going for you? Did it get any better? I started a Basic campaign recently. After the first day it seems Apple just stopped serving the ads for my Basic campaign. I also tried increasing the CPI but that hasn't been successful yet (I'm going to give it a little more time). What's weird is I can only find the Ad in the App Store on a direct search of my app name. My concern of course with that is Apple charging me for installs on a direct search of my app by name (since they place the Ad over the organic result). If the ad is being served as a result of other search queries, I haven't been able to find it. Of course if Search Ads starts getting my app valuable installs all is forgiven but I haven't really seen Basic do anything so far.

Attempting to use Catalyst for the first time. I just switched on "Optimize for Mac" and got this on launch. Some compiler warnings for this would be nice.... I'm supposed to just run the app and find forbidden objects for the "Mac idiom" by trial and error?

I opened a thread on this issue here: https://developer.apple.com/forums/thread/716151 Still haven't been able to find a workaround (or even reproduce the issue on my iPad running iOS 15.7). But I'm def. getting loads of crashes for this.

https://developer.apple.com/forums/thread/670068 This answers my question. A new "Xcode Extension" project right out of the box does not have "XcodeKit" set to Embed and Sign, which seems like a bug to me.

I decided to just live with the safeAreaInset bottom value of 20.0 even when the external window scene is presented like this. Adjusted a few things to make it look better in my UI but not worth comparing the frame of the window vs the frame of the screen to detect this state, as that code is too fragile. I still think the safeAreaInset bottom should be 0 when the window scene is presented in this style.