Just to be clear, this has nothing to do with NSStatusItem or LSUIElement. Simply make a new Mac project in Xcode, in Swift, with Storyboard. Run it. You will see the console fill with these warnings.

If you don't want the overflow menu, set the navigation item's style as .browser.

I'm having the exact same issue. I complained about this when this requirement was first promulgated, and here it is happening again. I do not have a new version of any of my apps to submit at this time; does this mean that I cannot update my age ratings now, and that therefore I will never be allowed to update any of my apps ever again??? What in the blue-eyed tunket is going on here????

Sorry for the noise — it turns out that the task ID must begin with the app's bundle ID exactly.

Sorry to barge in on this thread, but I am completely unable to get BGContinuedProcessingTask to work in a UIKit app (the task never starts, the heads-up progress never appears), even though the very same code in a SwiftUI app works just fine. Is this by design? It wasn't mentioned in the video.

I have sent a complaint about this to Apple. The email and the App Store Connect banners specifically say that action is required now, but the new questions, though visible, are not editable so no answers can be provided.

This incident neatly embodies everything that is wrong with feedback reporting to Apple. As a programmer, I regard bug reports from users as a precious gift! Users who provide good bug reports are a valuable resource, to be harbored and treasured. Apple's default response to feedback, on the other hand, is to deny the existence of the issue and to blame and belittle the user who reports it. The user has to repeat the same information many times in order to get Apple to listen at all. When the problem is finally solved, there is no acknowledgment, thanks, or explanation from Apple. The entire process is insulting to the user. This is why I mostly just don't bother any more with the feedback assistant.

@Engineer So far, the "engineering teams" have merely repeated the claim that the app is calling application:didRegisterForRemoteNotificationsWithDeviceToken:. It doesn't. If it did, this would not be a bug!

If you are seeing it, report it to Apple! They aren't going to believe me without support. You can mention FB16995686 in your report but having your own report is what makes the difference.

The 16e is too new. You must update to Xcode 16.3 in order to build to the 16e.

So the "solution", according to the release notes, is just to turn off this feature: defaults write com.apple.dt.Xcode IDEDocumentationSpotlightIndexDisable -bool YES

FB16995686

I agree with the assessment of @B347 — the RC is spinning its wheels, unable to index the documentation and using 100% of CPU.

@B347 But Xcode is still spinning its CPU wheels violently, and makes no progress on indexing the documentation.

Submitted as FB16995686.