TLDR, no need to manage provisioning profile: Share your project folder with the virtual machine Open the project in xcode 15.4 in the virtual machine, do not change anything Click Product->Archive Once done, copy the archive to your physical machine Open the project in your physical machine, and click Window->Organizer, and distribute your app. If your project doesn't require additional build configurations, you can also use xcode cloud build to simplifiy things.

You can directly load the scene using a URL, no need to set up model: let scene = try SCNScene(url: url) let renderer = SCNRenderer(device:MTLCreateSystemDefaultDevice()) renderer.scene = scene let image = renderer.snapshot(atTime: 0, with: AppStyle.ImageSize.thumbnail.size, antialiasingMode: .multisampling4X) Meanwhile, as for now, the QuickLookThumbnailing framework can't generate thumbnails for usdz files on visionOS, we should wait for it to be available.

Hi @Vision Pro Engineer Thanks for the info. I have an app on the app store that allows users to create and share spatial content, and one of which is 3D model. Currently I'm using a RealityView wrapped in a Volumetric Window to display 3D models in the user's space, scaled and repositioned in the centre of the volume according to their bounding boxes. However, there are a few limitations, such as: For animated models, the animation might cause the model to go out of the bounds of the volume. Window management issues, e.g. when the user opens a volumetric window, and closes the app in the order of closing the main window first and then closing the volumetric window, when they reopens the app, it's always shows the volumetric window and they'll never be able to open the main window again(unless add additional logic). I'm now migrating the app to set visionOS 2.0 as the minimum deployment target. And the Quicklook preview application has many nice built-in features, such as snapping to surface, free scaling, gesture handling, etc.

Typo there, the rate is 48000(aka 48kHz).

It seems like the issues is with this line: audioEngine.connect(audioPlayerNode, to: audioEngine.mainMixerNode, format: nil) For some reason, if I specifically set the format to be the format of the PCM buffer, then the memory leak issue is gone.

Still stuck in "In Review" status in late 2024 for over an week. It's a new app submitted to visionOS app store. The first submission was rejected because they need me to upload a video walkthrough to demonstrate the app. I submitted the video and then the app went into the "In Review" status ever since. I didn't see any trace of the reviewer opened the app according to my backend logs. Tried to contact customer service several times, but got the same copy-paste reply everyone has mentioned above. This situation happened before to my other app's update patch. It took them 10+ days to finish the "In Review" status. And that happed in August 2024. While this app review took place during the U.S. Thanksgiving holidays. So my assumption is, when your app reviewer is on holiday, your app will be stuck in the "In Review" status until they actually come back from holiday and do the job. The "In Review" status doesn't mean your app is actually being reviewed, but only means the review task has been assigned to someone. They couldn't care less about your releasing plans or how urgent it is. Paying £99 a year to get such service, SHAME ON YOU APPLE!

Same request here!

Update: I did receive a call from a representative, who guaranteed the app review will be expedited. However, after an entire day's "work" from App Review Team, there is still no sign of anyone picking up the review task. This situation has gone beyond frustrating. It is now a serious failure on Apple's part.

I just don't understand, it's just a feature update and should only take 5 minutes at most. But even the review is in the expedited queue, still nobody picks up the task. I'm losing my mind here!

11 days, and still need "additional time", given the fact that nobody has ever picked up the ticket? What an awful excuse.

This happens to my app all the time, because the reviewer don't want to take any responsibility of anything that's unclear to them, otherwise they'll risk losing their job. So essentially, anything that they don't understand, they'll just escalate it tho the app review board, which holds meetings every Tuesday. So technically speaking, the app's status is "Waiting for Board Meeting, because the reviewer can't decide anything". We need more companies like Epic Games to sue Apple so that the review process is more transparent!

This happens to my app all the time, because the reviewer don't want to take any responsibility of anything that's unclear to them, otherwise they'll risk losing their job. So essentially, anything that they don't understand, they'll just escalate it tho the app review board, which holds meetings every Tuesday. So technically speaking, the app's status is "Waiting for Board Meeting, because the reviewer can't decide anything". We need more companies like Epic Games to sue Apple so that the review process is more transparent!

We should sue Apple together. Every feature of my app update has to go to board review because the reviewer can't decide anything and won't take responsibility, despite there is a complete reviewing history available on their end. This entire review mechanism is slow and opaque, we need more companies like Epic Games to make Apple change!