https://medium.com/@timonus/low-hanging-fruit-for-ios-apps-running-on-visionos-08a85db0fb31

Same here on macOS Sonoma 14.4.1. =。=

FB13682631

Well, it seems I've completely missed the point.

Update Selecting specific app version instead of "All Version" solved the problem.

Solved.

Thank you for the response! However, after trying, I still haven't been able to retrieve the crash logs from visionOS, including after upgrading to yesterday's Xcode 15.2. I will continue to monitor this issue, and if it persists, I will submit a FB. Thanks again!

Although I have the same question, don't ask Apple anything about the future. 😂

Till visionOS 1.0 beta 7, there is still no way to set the loading window size.

The reasons for needing to distinguish the runtime environment include: App's custom UI controls and gestures need to be optimized for interaction on visionOS, such as the size of the touch area. Some user guide texts related to interaction in the app need to be distinguished for different platforms. The app sometimes needs to present to the user its type of device. It is very confusing for users to display Vision Pro as an iPad. FB13465097

Hi, @Developer Tools Engineer Some of my users have encountered issues related to CloudKit in the past week, including myself frequently encountering CKError.Code.serviceUnavailable. The tricky part is that some devices will encounter data inconsistency issues, with no errors reported, making it very difficult to debug. (It seems that records created by another device cannot be queried through CKQuery, not 100% confirmed.) At present, I can only provide this information, but I can confirm that there have been some new issues with CloudKit's service in the past week. I don't know if it's useful to submit a FB in this situation. Do you have any suggestions?

@alex_taffe Hi:) In my app the value of @Environment(\.colorScheme) is correct. The system renders the live activity widget both in light and dark scheme since iOS 17.1 beta 2.

FB13258033

Fixed in iOS 17.1 beta 2.

Also reported: FB13213919