@B347 Perfect, thank you. Nice to know I'm not alone. I might have to revert to beta 2 as well.

@DTS Engineer I don't think it's just noise (because I was indeed doing something that might be questionable), but okay.

Yeah, reverting to beta 2 fixed it. Instantly. It feels like someone built a huge concrete wall around the UIKit docs in beta 3, and poor old Xcode was just endlessly hammering at it with all its might (i.e. 100% CPU usage but no progress in building the docs cache).

@Engineer My app delegate does not implement any methods, and I am not using any third-party libraries. There is no push notification code of any kind in my app. The warning is completely mistaken.

Submitted as FB16995686.

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

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

FB16995686

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

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

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.

@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!

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.

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.

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.