Reproducible in Xcode 16 beta. It seems that AppIntentsSSUTraining emits warnings for locales that don't support flexible matching. The thing is broken. So I disabled flexible matching in the build settings, and the warnings are gone.
Gong
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
@simonfromhelix iOS 18 and watchOS 11 are comming! Looking forward to the new features and new bugs π
Hope is a good thing. π
WWDC24, letβs wait and see!
https://medium.com/@timonus/low-hanging-fruit-for-ios-apps-running-on-visionos-08a85db0fb31
Same here on macOS Sonoma 14.4.1.
=γ=
Well, it seems I've completely missed the point.
Update
Selecting specific app version instead of "All Version" solved the problem.
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.