“iPhone 16 pro”

Thanks for the response, for context it was around 15 submissions over a few months and 30ish messages. I get your example, but I think my situation’s a bit different. The updates weren’t just micro changes trying to slip something through, there was a mix of both small tweaks and broader changes. The issue was the feedback stayed very generic (“overtly sexual”) without pointing to specific elements, so each update was essentially a best guess at what might be triggering it. Especially early on, when only metadata was flagged, I assumed the issue was relatively minor. By the end, I actually went in the opposite direction of evasion & submitted a build with everything unlocked and included screenshots showing all content upfront, so review had full visibility, as requested during a phone call. It’s possible I missed a couple of screenshots in earlier messages, but nothing was intentional. That’s why the 3.2(f) decision caught me off guard, there was no intent to hide or mislead, just trying to int

I’ve also spent some time investigating this. While monitor mode works, setting the channel using CoreWLAN’s [CWInterface setWLANChannel:error:] API does not behave as expected. As a result, capturing isn’t reliable for third-party apps on Macs with the Apple N1 Wi-Fi chip or the MacBook Neo. I've identified and submitted two issues: FB22295165: [CWInterface setWLANChannel:error:] does not work on a disassociated interface, even though the documentation indicates it should, and it behaves correctly on older Macs. FB22295685: Once in monitor mode, [CWInterface setWLANChannel:error:] reports a successful channel change and the interface reflects the requested channel, but capturing continues on a different channel (usually the channel the interface was operating on previously to being placed in monitor mode). There also appears to be a race condition between entering monitor mode and macOS attempting to rejoin a network shortly after calling [CWInterface disassociate]. While I can’t confirm this definitively, t

Thanks Albert. The AASA is publicly accessible with no blocking, no IP filtering, and no user agent restrictions: https://fanarchy.fans/.well-known/apple-app-site-association Apple's own CDN already has the current version synced: https://app-site-association.cdn-apple.com/a/v1/fanarchy.fans So the AASA sync is working — the issue is the experiences stuck in Received and not transitioning to Published. We're also seeing inconsistent behavior across devices. QR code scans for the same URL work on some devices but show App Clip not available on others. For example, it works on an iPhone but fails on an iPad — same URL, same network, both fresh devices that have never had our app installed. Interestingly, when we removed /next-game from the App Clip entry in our AASA, QR codes started falling through to Safari where our Smart App Banner meta tag (apple-itunes-app with app-clip-bundle-id) successfully triggers the App Clip card. This workaround is functional but shouldn't be necessary. We have other App

Hey @THeberlein, This is unexpected behavior. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. I'd greatly appreciate it if you could open a bug report; please include a link to your webpage and a sysdiagnose from your Vision Pro captured after this occurred, and post the FB number here once you do. Instructions on capturing a visionOS Sysdiagnose can be found on the Profiles and Logs webpage. Bug Reporting: How and Why? has tips on creating your bug report. Thanks for your help, Michael

Hi Michael, As requested, I updated the sample app to use ToggleImmersiveSpaceButton instead of a manual open/close button. I rebuilt the app, distributed it via TestFlight, and reproduced the issue on Apple Vision Pro. The issue still occurs consistently. Attachments: Screen recording demonstrating the issue - TestFlight distributed Build. Sysdiagnose captured after reproduction of the issue. Updated sample project. Steps to reproduce: Archive and upload a build to TestFlight. Install the application via TestFlight. Tap Show Immersive Space. Lock the window. Tap Hide Immersive Space. Tap Show Immersive Space. The red cube is missing and even immersive space and window disappears for a brief moment and then appears. Device: Apple Vision Pro visionOS 26.0 Xcode: Version 26.3