Apple Maps Guides

@vsmedia Be sure that you file a bug report. The more people that let Apple know of this issue, the better chance it will get fixed some day.

I read this with interest. I'm not an Apple / XCode developer. I downloaded and used XCode now for a week and struggling to get my Web Extension on the Apple Web Extension store for Safari. I did it so easily with Google Chrome and Firefox, and they are already out there being used. With Safari, it just seems like over kill with XCode, right now stumbling because it says I do not have a 512 x 512 png in icons.icn when I do - I followed all the steps. So, is there a way I can just not use XCode at all and get my Extension (it's just one single content.js and manifest.json file and nothing else!). Where is this Safari Web Extension Packager and does it allow me to send it up to Apple Store for end-users to use without me having to use a 2GB application XCode to do it? Thank you.

I did a few more tests and RT[:3, 3] works correctly while RT[..., :3, 3] does not. Check this minimal repro: import tensorflow as tf RT = tf.constant( [ [-0.25497323, -0.81989247, -0.5126062, 0.3136883], [-0.32365915, 0.57191426, -0.75376326, 0.36354592], [0.9111716, -0.02627973, -0.41118845, 0.511739], [0.0, 0.0, 0.0, 1.0], ] ) with tf.device(/GPU:0): T1 = RT[..., :3,3] T2 = RT[:3,3] print(fRT[..., :3,3]: {T1}) print(fRT[:3,3]: {T2}) output: 2025-10-04 15:16:12.602764: I metal_plugin/src/device/metal_device.cc:1154] Metal device set to: Apple M4 Max 2025-10-04 15:16:12.602789: I metal_plugin/src/device/metal_device.cc:296] systemMemory: 128.00 GB 2025-10-04 15:16:12.602794: I metal_plugin/src/device/metal_device.cc:313] maxCacheSize: 53.76 GB WARNING: All log messages before absl::InitializeLog() is called are written to STDERR I0000 00:00:1759583772.602803 5120482 pluggable_device_factory.cc:305] Could not identify NUMA node of platform GPU ID 0, defaulting to 0. Your kernel may not have been buil

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.