Hello, since visionOS does not allow the camera to be called, you can only use the advanced API provided in ARKit, Scene reconstruction's MeshAnchor (https://developer.apple.co M/documentation/arkit/meshanchor) generates the grid of the user environment. However, please note that this function cannot draw a grid of any human, nor can it draw a table of real-time moving objects, and you cannot draw a grid of a human in the case of non-enterprise API. You can use feedback to tell Apple about your needs.

You can feedback this bug to apple, look here: https://feedbackassistant.apple.com

@Engineer Thank you for your reply. I prefer to achieve it through code rather than change it in the audio file. In this way, when users experience AR when wearing Vision Pro (or iOS devices), the audio sound source will also move in the opposite direction during the process of turning their heads and moving (or moving with iOS devices), so as to achieve a real experience and achieve the effect of spatial audio (https://developer.apple.com/documentation/visionos/playing-spatial-audio-in-visionos) . Do you have any suggestions? Thank you!

Hello @Vision Pro Engineer , Thank you for your response. I would like to inquire further about the matter. Given that Metal is primarily utilized for graphics processing, it lacks the capabilities to play sound. In this context, I am curious to know if Compositor Services can fulfill the requirements for playing spatial audio. Additionally, I would like to understand whether the ARKit function, which is designed to perceive the user’s surroundings, such as Plane detection, will be subject to any limitations (For example, the geometry of PlanAnchor cannot be accessed). I eagerly anticipate your response. Thank you for your attention to this matter.

Hello @DTS Engineer I have submitted the Swift Student Challenge work, but there are the following two points: My program is close to a complete app. Although I have tried my best to reduce the code, the experience time of the work may exceed 3 minutes. In order to ensure that the auditor can experience the core content of the work within 3 minutes, I have put the important part at the beginning. After submission, an error (only some non-core functions) was found that did not affect the normal operation of the program but may cause some functions to be unrealized. Excuse me, will the above situation lead to the direct rejection of the work? Will it reduce competitiveness but still have a chance to be considered? Is the regulation of "within 3 minutes a rigid regulation or a recommendation? Will the auditor extend the experience time under the premise of maintaining fairness? Although the competition has ended, I still want to know the relevant information. Thank you!

When you submit it, you will automatically receive a letter titled "We got it!" The confirmation email. If you haven't received it, it may mean that the submission was unsuccessful. But please don't give up immediately, because not receiving the email does not exactly mean that the submission failed. It may be a problem with the Gmail system (although this is extremely rare). If you want to finally confirm your submission status, it is recommended that you first adjust your mentality, and then visit https://developer.apple.com/swift-student-challenge/apply/ and log in to your Apple ID account. After logging in, you will enter a new interface: If the page title is "We've received your submission.", then congratulations, your submission has been successfully received, and you can rest assured. If the content displayed on the page shows that you have not submitted it yet, then unfortunately, it is almost certain that your submission was unsuccessful. If you confirm that you have failed to submit successfully, don't give up completely. You can try to contact Apple's official support (swiftstudentchallenge@apple.com) for help. However, it should be noted that the possibility of approval is low, because Apple needs to maintain fairness to all participants, and the official agreement has clearly stated that they are not responsible for damage or failure caused by technical problems in the submission process. Finally, adjust your mentality. You may feel regretful or regretful, but please believe that this experience will be a part of your growth. Even if you fail to submit it successfully, don't be discouraged. There will be more opportunities in the future. I have encountered a similar situation and been troubled, but I still choose to continue to work hard to meet the next challenge. I understand your feelings and sincerely wish you good luck!

错误的潜在原因可能是过期的证书或配置文件，或Xcode使用的测试证书或配置文件的临时有效期。此外，iOS系统更新可能会使之前安装的软件包不兼容。最有效的解决方案是重新从Xcode安装程序。 The potential reasons for the error could be an expired certificate or configuration file, or a temporary validity period for the testing certificate or configuration file used by Xcode. Additionally, an iOS system update may have rendered the previously installed software packages incompatible. The most effective solution would be to execute the application from the actual Xcode machine.

Hello, The age standard in China is also 14 years old, and I am also 13 years old. Therefore, I contacted swiftstudentchallenge@apple.com for assistance. They informed me that I could request my guardian to send an email to s wiftstudentchallenge@apple.com to apply for individuals under the age of 14 to participate in the competition. Consequently, you do not need to wait. You can request your guardian to submit an application to swiftstudentchallenge@apple.com. However, you mentioned that the age rule in South Korea has been synchronized with the international one, which is 13 years old. If you believe that Apple has made an error, you can contact swiftstudentchallenge@apple.com to request that they rectify the rule. I hope this will be helpful to you!

Certainly, you can utilize the features and technologies associated with Metal. However, I would like to emphasize that while I am not proficient in Metal, I possess a certain level of understanding of the technology. To the best of my knowledge, Metal appears to be incompatible with virtual machines(Simulator) and necessitates the execution on a physical machine. Nevertheless, I am uncertain about this assertion. If this is indeed the case, please ensure that you request the reviewer to utilize Playground for the execution of your application (there is a specific option available in the form). This option should be chosen instead of Xcode, as the execution of your application using Xcode will result in the utilization of a virtual machine. However, if Metal is indeed compatible with virtual machines, please disregard this paragraph. I trust that this information will be beneficial to you.

As mentioned in the rules, you can use third-party code and resources, but you must meet the following three requirements: When submitting, you must declare where and why you used other people's code and resources. You can't infringe. You must make sure that the code and resources you use are available to everyone. ( The two points you mentioned are likely not to infringe) Most of your content and core content should be developed by yourself, and third-party code and resources can only be used as an auxiliary. But I can't completely make sure that it's right, but it's probably right because I've summarized it based on complete terms and experience. I also decided to do so when I submitted it. I hope it can help you.

Due to the regulatory framework and policies of China, the introduction of CallKit to the Chinese market presents significant challenges. CallKit offers functionalities akin to caller ID and Voice over Internet Protocol (VoIP), which involve the management of sensitive data such as user call records and caller ID. Such functionalities require approval from relevant Chinese government departments. Consequently, CallKit is currently inaccessible in China due to legal restrictions. However, I have recently received information that some WeChat users have received notifications for CallKit. I anticipate that CallKit will be made available to the general public in the near future. 由于中国的监管框架和政策，将CallKit引入中国市场带来了重大挑战。CallKit提供类似于呼叫者ID和互联网语音协议（VoIP）的功能，这些功能涉及用户呼叫记录和呼叫者ID等敏感数据的管理。此类功能需要中国政府相关部门的批准。因此，由于法律限制，CallKit目前在中国无法访问。 然而，我最近收到的信息是，一些微信用户收到了CallKit的通知。我预计CallKit将在不久的将来向公众提供。

您可以在 反馈（https://www.apple.com/feedback/) 中报告此问题，我相信Apple会解决和纠正它。 You can report this issue in Feedback (https://www.apple.com/feedback/), and I am confident that Apple will address and rectify it.

The potential issue lies within the chip. Kindly verify whether the chip of your Mac is an M2 or a higher-end chip. It is possible that you have an M1 chip. The M1 chip may not undergo comprehensive training, but a progress bar will still be displayed.

RealityView, a high-level framework specifically designed for visionOS, can also be utilized on iOS. However, RealityView offers a simpler and more aligned approach to visionOS. While ARView may present some challenges and is not compatible with visionOS, it still holds advantages for iOS app development. Notably, ARView provides access to functions that are exclusive to it, such as face tracking, body tracking, geotracking with anchor placement based on latitude and longitude, object detection, app clip code detection, and video frame post-processing. In summary, for iOS app development, I recommend utilizing ARView due to its broader content support. However, if you intend to develop visionOS apps, RealityView is the preferred choice. At the same time, you can also refer to here

Take a look at this. I hope it will be helpful to you! https://developer.apple.com/documentation/xcode/running-your-app-in-simulator-or-on-a-device#Connect-real-devices-to-your-Mac