“Apple Maps Guides”

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

[quote='820277021, Great_Om, /thread/820277, /profile/Great_Om'] Since it was not possible using the UserDefaults class [/quote] What’s not possible? Reading a user default from a specific domain, like com.apple.Finder? You are correct that UserDefaults can’t do that, but running the defaults tool is not the best alternative. Rather, use CFPreferences. For example: import Foundation func main() { guard let obj = CFPreferencesCopyAppValue(ShowHardDrivesOnDesktop as NSString, com.apple.Finder as NSString), CFGetTypeID(obj) == CFBooleanGetTypeID(), let showHardDrivesOnDesktop = obj as? Bool else { fatalError() } print(showHardDrivesOnDesktop) } main() WARNING Unless otherwise documented, system preferences like this are an implementation detail. It might be OK to use them in a limited scope — like in a managed environment where you control all the copies of the code — but you should not rely on implementation details in a product that you deploy widely. The code above won’t work if your app is sandboxed. Then ag

You are definitely breaking new ground here, so I’m gonna to do some research and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Error code 69 is EX_UNAVAILABLE, which isn’t something I’d expect from notarytool. Are you sure you’re not hitting an xcrun problem? What does this report: % xcrun -f notarytool /Applications/Xcode.app/Contents/Developer/usr/bin/notarytool Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Dear Support, We would greatly appreciate your assistance with the error received in Apple Pay In-App Provisioning process, as described in FB22280049. Thank you.

@AJAS_M_M My app, which was stuck in Apple's review process as mentioned. After that my App rejected multiple times due to the complex login procedure of my app requiring additional further explanation. However, it was finally approved on February 18, 2026. Regarding Apple's comment on January 26th: Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us. I actually followed the link provided there and requested an expedited app review by navigating to contact us > Get help with a new issue > App Review > request an expedited app review. Based on my experience, I believe this is the only thing we can do on our end in such situations. I hope your review process concludes successfully as well.