“build disappears”

Hi Michael, Thank you for looking into this. To clarify, this issue is not reproducible when running locally (Debug or Release). It only occurs in TestFlight distribution builds. In our production app as well as the minimal sample project, the behavior is consistent — the bug only appears when installed via TestFlight, not when run directly from Xcode. Regarding the video - at 0:31 you can see the cube briefly disappears after Lock In Place. That is the moment we are referring to. Could you please try the following: Archive the sample project Upload to TestFlight Install via TestFlight on the device Reproduce the Lock In Place steps I am confident it will be reproducible in that configuration. I am happy to provide another screen recording specifically showing this if that would help. Please let me know if you need anything else. Thanks, Kunal

Thanks for the post, in this page you'll find a sample for AppClips as well as the first note will provide you the 101 of App Clips. I always recommend developers to go over all those videos and documentation liked on that note. Then download the app, look at every single configuration from that app including the Clip target! https://developer.apple.com/documentation/appclip/fruta-building-a-feature-rich-app-with-swiftui In my opinion and without going deep in your solution, the reason your AASA endpoint is never getting called when you scan the QR code is due to a common misconception about how iOS handles App Clips and Universal Links, the iOS device does not fetch the AASA file at the moment you scan a QR code. Downloads the file at app installation time and there is also a delay. When you scan a QR code, iOS checks its local cache and Apple's CDN records to see if that URL is registered to an App Clip. If Apple's CDN hasn't validated your AASA file, or if the TestFlight configuration is incomplet

@michelbechelani-aya Yes, if you distribute the app using the Apple Developer Enterprise Program or TestFlight there is no need to resign the app, therefore everything will work on the app. Now the most robust way to handle OAuth/Sign-in flows in automated cloud testing does not need Universal Links entirely for your test builds. Create a specific build configuration for your cloud tests. In this build, configure your app to use a Custom URL scheme for its callback. Configure your staging/testing Auth Server to accept and redirect to this Custom URL scheme instead of the Universal Link (https://...). When the test runner triggers the login, the browser will redirect to myapp-test://, which the OS will route back to your app, regardless of who signed it. Not trying to side track you. Follow your architecture, but I want to make sure to show there are other options. Albert Pascual
  Worldwide Developer Relations.

Hey @Kunal07, Thank you for filing your Bug Report (FB22290781) and including a sample project and a video, however, I'm unable to reproduce this bug. Whenever I was in the immersive space the red cube was there. I tried running the app in the Release and Debug configurations. In the video I see the following: at 00:10, you lock the window and the cube does not disappear. at 00:18, you close the immersive space and the cube disappears with the immersive space. at 00:27, you reopen the immersive space and the cube appears. Your sample app provides a fully immersive space. You are in the immersive space when you no longer see passthrough. It might be more clear if you replace the static Open Immersive Space button with ToggleImmersiveSpaceButton(). Can you do this and reproduce the issue with a video? If you're able to reproduce this, a video and a visionOS Sysdiagnose would be very helpful. Thanks, Michael

Has anyone experienced an app disappearing from App Store Connect? Any advice on escalation would be appreciated. There have been a couple of cases where the app was automatically removed from the store after a software update even though the status said it was ready for distribution. It happened in March 5th. I've asked Apple, Inc. But there has been no explanation.

I uploaded the update build, edited the screenshots, and clicked submit for review, but a warning message saying Screenshot upload is still in progress appeared, and it hasn't progressed for several days.

[quote='820155021, alex_strong, /thread/820155, /profile/alex_strong'] I've had issues getting the dmg signed by the Apple notary service [/quote] That text suggests that you’ve misunderstood how notary works. The notary service doesn’t sign your product. Rather, you present it with a distribution-ready product, one that’s already signed, and the notary service checks it and, if all is well, issues a signed ticket. See Notarisation Fundamentals for more about how this process works. As to why the notary service is refusing to notarise your product, it’s hard to say without more info. It sounds like you were able to submit the product and get a response, but the status is Invalid, indicating a problem with your submission. In that case the next step is to look at the notary log. What does it say? See Fetching the Notary Log for info on how to get the log. [quote='820155021, alex_strong, /thread/820155, /profile/alex_strong'] The only big change we made this time was switching to Maven [/quote] Ah, Java. Notari