Apple Maps Guides

As explained in doc, Changing a component’s value often will require higher or coupled components to change as well… The exact behavior of this method is implementation-defined: Changing a component’s value often will require higher or coupled components to change as well. For example, setting the Weekday to Thursday usually will require the Day component to change its value, and possibly the Month and Year as well. If no such time exists, the next available time is returned (which could, for example, be in a different day, week, month, … than the nominal target date). Setting a component to something which would be inconsistent forces other components to change; for example, setting the Weekday to Thursday probably shifts the Day and possibly Month and Year. The exact behavior of this method is implementation-defined. For example, if changing the weekday to Thursday, does that move forward to the next, backward to the previous, or to the nearest Thursday? The algorithm will try to produce a result which is i

I'll explain what I experienced and how I solved it. iPhone was not detectable in any way (nor was the apple watch), I tried getting latest beta of Xcode, I tried latest stable release, nothing seemed to work. I waited for final release which came up shortly and still no luck. What ended up working was a thunderbolt cable. I went to an Apple Store and they told me to wipe the phone completely because I still had the beta installed, which attending to build number was wrong, but something was off so I wiped the phone. That fixed the issue, although I lost a couple of pictures and some minor data for apps that didn't save it in cloud. Hope this helps someone in the future :) As a side note, debugging on an Apple Watch is becoming really really difficult... sometimes it just does not want to connect

The error occurs in the following Apple library: https://github.com/apple/app-store-server-library-java/blob/main/src/main/java/com/apple/itunes/storekit/verification/SignedDataVerifier.java#L172

Your post is extremely interesting and definitely requires more thought on my part. It seems that what you're doing is to build a FocusCoordinator, conceptually similar to a Navigation Coordinator (although I think that there may be some missing APIs preventing a comprehensive solution. My immediate interest is on tab-navigation and I have some new information to offer about it. It turns out that in most cases, sending a to a focueed TextField will cause focus to change, BUT if the TextField is instantiated with the axis: AXIS parameter, the is added to the TextField body instead. I don't know how Apple will classify it, but I'm calling this a bug and have reported it. (FB20505919).

Thanks for the guidance. I added screenshots just to show the situation more clearly: On iOS devices the app builds and runs fine with import DeclaredAgeRange. On Mac (Catalyst) the same code fails with an import error. I also looked into filing a Feedback report, but honestly the procedure felt quite complex, and I stopped midway. I understand that Apple wants to filter out low-quality reports, but from the perspective of a busy app developer it’s hard to dedicate that much time to reporting SDK issues. So please consider this thread as a reference. For now, I’ll conditionally compile the feature with #if canImport(DeclaredAgeRange) and ship the app that way.

In this situation, you might contact your users who can reproduce the issue and are willing to help, ask them to install the file provider profile, follow the guide to reproduce the issue and capture a sysdiagnose, and then provide sysdiagnose to you. From there, you can look into the system logs, and try to figure how the system behaves differently from the workable case (your case). The debugging process may take time, but given that you don't have a reproducible case, that's probably the way you can move forward. Best, —— Ziqiao Chen  Worldwide Developer Relations.

I did a sanity check and looked in Xcode, in the templates for a new target, I don't see 'Quick Look Preview Extension' in the visionOS' list (I do see 'thumbnails'). Could it not be possible yet? That would explain why no issues when making the app 'designed for iPad'. I suppose the issue disappears if you remove vision as a target for the quick look extension.. but maybe you want the extension in visionOS as well. I read some more and I came to the conclusion that the Quick Look preview extensions are not yet for visionOS, but only someone from Apple can confirm that.

Thanks for your post, you mentioned you do not want to provide that information publicly. I suggest you continue this conversation with one of our DTS Engineers privately. If you have a focused sample you can share. To do so, please submit a code-level support request. When you create the request, indicate that you were referred by someone at Apple and make sure to include a link to this thread. Albert Pascual
  Worldwide Developer Relations.

We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to a consumer feature and is better suited for the Apple Support Communities https://discussions.apple.com/welcome Albert Pascual
  Worldwide Developer Relations.