show when run

@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

I am also running into this error. (Jan 2026) Xcode v26.2. Icon Composer 1.2 (76) Looking at the release notes above, the issue has not been resolved. Error message I get: Invalid large app icon. The app icon in the asset catalog -app name- can't be transparent or contain an alpha channel. My two cents, it might be due to the automated compiler for the apple App Store distribution SDK they use to review apps quickly before it goes to a real person. This might be due to the new Liquid Glass UX/UI update. I was really excited to try it, but until it gets fixed, I don't think we will get app icons being Liquid Glass anytime soon. Might be due to the fact that, I have the lowest version of iOS 17, which might not recognize it yet. I wonder if it is only for iOS 26 uploads? no idea.

What is the problem with my code? If you showed the code, maybe we could tell. Could you also show how it looks like on simulator (which device simulator) and which physical device ?

The developer documentation for Icon Composer: Add your Icon Composer file to an Xcode project If you create your Icon Composer file outside of Xcode, you can add it to your Xcode project anytime to view your icon in Simulator and on real devices. Just drag the Icon Composer file from Finder to the Project navigator, and Xcode provides feedback on where to drop it in a target folder. No, it doesn’t - it asks how to add it and it adds it at the top level of the navigator but it won’t change how OS 26 displays your app icon in the finder. Alternatively, choose Add Files from the Add button at the bottom of the Project navigator and select your Icon Composer file in the dialog that appears. It asks how to add it and it adds it at the top level of the project but it won’t change how OS 26 displays your app icon in the finder. In the project editor, select the target and the General tab. Under App Icons and Launch Screen, ensure that the name in the App Icon text field matches the name of the Icon Composer file wi

Update: Found a possible reproduction pattern correlated with plugging the device into power. Reproduced again on a device with no other Screen Time/blocker apps installed besides my own. Attached a second sysdiagnose in my feedback: FB21450954. Observed behavior: DeviceActivityMonitor.eventDidReachThreshold fires even though iOS Screen Time shows 0 minutes for the selected app that day (verified in Settings > Screen Time), and my extension applies ManagedSettings shielding immediately after the callback. Possible repro pattern: iOS 26.2 (23C55). Daily schedule 00:00–23:59. Do not open the selected app(s); leave device idle/locked for hours (0 usage). Plug the device into power while it remains locked/idle. Within minutes, eventDidReachThreshold fires despite 0 Screen Time minutes.

Update: Found a possible reproduction pattern correlated with plugging the device into power. Reproduced again on a device with no other Screen Time/blocker apps installed besides my own. Attached a second sysdiagnose in my feedback: FB21450954. Observed behavior: DeviceActivityMonitor.eventDidReachThreshold fires even though iOS Screen Time shows 0 minutes for the selected app that day (verified in Settings > Screen Time), and my extension applies ManagedSettings shielding immediately after the callback. Possible repro pattern: iOS 26.2 (23C55). Daily schedule 00:00–23:59. Threshold: 30 minutes. Selected app: NHL. Do not open the selected app(s); leave device idle/locked for hours (0 usage). Plug the device into power while it remains locked/idle. Within minutes, eventDidReachThreshold fires despite 0 Screen Time minutes. Related thread that seems similar: https://developer.apple.com/forums/thread/809410