Is standardAppearance deprecated? Why do those APIs have no effect on the new tab bar UI?

I'm curious about this as well. We have a CAD-like interface that is very dense and not conducive to multitasking. The documentation for the plist key doesn't mention anything about its deprecation, but it does not prevent windowing in the latest iPadOS beta. The related WWDC video says "Every app that supports multitasking now shows a handle in the bottom right corner." But in reality, it appears that there is no way to opt out of this.

@QuantumByte43 - Boosting this; I agree that neither of those other threads (including mine) have addressed our questions about the nature and timing of the deprecations. In particular, I haven't been able to find any information about the interim non-resizable window behavior.

It looks like they added a technical note with a little more information since this was posted: TN3192: Migrating your iPad app from the deprecated UIRequiresFullScreen key | Apple Developer Documentation

We have observed similar issues recently. Any guidance is appreciated.

@Vision Pro Engineer Thanks for the reply, Michael Is the following based off what you've heard or do you have videos and files that show the behavior? Mostly based off user testimonial. I think we have recorded a couple instances of this during onboarding sessions, but in those cases, we suspected that screen sharing itself could be contributing to the issue. Do you have any logging in place that is capturing any RoomCaptureSession.CaptureError errors in production? Yes - we track all "fatal" scanning errors. We haven't noticed an uptick in those. It seems like another developer was able to improve performance by resolving a memory leak. Have you profiled the application when performing multiple scans in a row? We have done some profiling over the years, but it's difficult because the act of profiling itself severely degrades scanning performance. We have noticed that RoomPlan itself seems to cache/retain resources after scanning even if we have no active references to it. I believe we reproduced this with the RoomPlan example app a couple years back. Do you have any advice for logging we could add beyond the RoomCaptureViewDelegate method errors? We have been reluctant to change even our logging implementation because of how difficult it is to test for regressions.