Search results for

Apple Maps Guides

149,502 results found

Post

Replies

Boosts

Views

Activity

Reply to Metal fails to create PSO on AMD based GPUs
Hello, Pre documentation Metal libraries built using Metal shader converter tools require a device that supports Argument Buffers Tier 2, running macOS 14 Sonoma, iOS 17 or later. If you build a Metal library for earlier OS versions, not all features will be supported. AMD GPUs lack many of the features offered by Apple Silicon and consequently PSOs won't compile (irrespective of Metal Shader Converter). Check the Metal Feature Set Tables for details.
Topic: Graphics & Games SubTopic: Metal Tags:
2w
Can’t change Primary Language — blocked by “for each version” even after deleting all CPPs (8 weeks, 10+ replies)
For ~8 weeks (10+ support replies) I’ve been unable to switch my app’s Primary Language from en-CA to en-US. App Store Connect shows: “Primary Locale couldn’t be saved because you must first provide all the required screenshots for each version in this language.” State: Default product page has complete iPhone + iPad screenshots for en-US and en-CA (live/approved). Issue began before any CPP existed; I have since removed all CPPs. Error persists, which suggests a stale/ghost CPP localization still being validated, or other issues. Questions: What does “for each version” precisely validate (live / in-prep / historical; default vs CPP)? Can deleted/never-approved CPPs still be validated, and how can they be purged? Anyone seen this after CPP removal—what fixed it? Happy to DM an Apple Staffer the case ID, a HAR of the failed save, and a short screen recording. Thanks! P.S. This has been open for ~8 weeks; I’m seeking an engineering-owned view to identify the specific unmet validator requirement or conf
1
0
108
2w
Custom USB Network Device Driver on iPhone
Hi, We are using the AX88772C as a USB->Ethernet bridge in a product we are developing. Due to the chip not following the NCM protocol, it is not supported by the default networking drivers on the iPhone. Initially, we intended on using DriverKit to develop a userspace driver for this device. However, we have been informed DriverKit is only available on iPad OS, not iOS. As such is the case, we have found two possible alternatives. First being IOkit, and the second being External Accessory Session (EASession). What are the limitations of each of these options? We need the ability to send and receive USB packets to Control and Bulk endpoints. Is this possible with either of the options defined above? Would either of these options require the device to be MFi certified? We have read that some APIs within IOkit require the apple device to be jailbroken. Is there a list of features that can be used without a jailbroken device? Documentation on these 2 options is limited, so any official documentation
5
0
126
2w
Reply to tvOS 26 file corruption issues?
Hi - thanks for asking. My app will download a JSON file which contains a list of image urls which are downloaded and stored in the NSCachesDirectory. I understand the NSCachesDirectory can get deleted by the OS when the app is not running, so on subsequent launch, the app will check for the presence of these files in NSCachesDirectory and will redownload them if they are not available. This has worked pretty reliably in production for nearly two years. With tvOS 26, there are now inconsistent and sporadic instances when the app exhibits behavior as if these files have been deleted. ie. the images are either missing from the playlist page, or the app uses an onboard backup failsafe JSON file to populate a playlist with temporary data if it cannot find or load the JSON file. I suspect something is getting corrupted because once this issue occurs, the only way to get the app to perform normally again is to delete and reinstall the app. Simply relaunching the app will not fix the issue, as programmed in my app l
Topic: App & System Services SubTopic: Core OS Tags:
2w
Reply to Instructions for debugging recent macos kernel versions?
Hello Kevin, uname -v on my local system shows: Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:30 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6020 so I've been using T6020 as the platform when building the kernel. The corresponding xnu source is this tag https://github.com/apple-oss-distributions/xnu/tree/xnu-11417.140.69 and the KDK is KDK_15.6_24G84.kdk. sw_vers shows me: sw_vers ProductName: macOS ProductVersion: 15.6 BuildVersion: 24G84 So I think that's the right KDK version for this system. I'm guessing the XCode version doesn't matter for these experiments (as long as the build succeeds), but for the record, I'm on XCode 16.4: xcodebuild -version Xcode 16.4 Build version 16F6 Apart from the other build instructions, the primary one I use to generate a DEVELOPMENT variant of the kernel is: export KDK=/Library/Developer/KDKs/KDK_15.6_24G84.kdk make SDKROOT=macosx KDKROOT=$KDK BUILD_WERROR=0 BUILD_JSON_COMPILATION_DATABASE=1 TARGET_CONFIGS=DEVELOPMENT ARM64 T6020 and then to generate a (boot
Topic: App & System Services SubTopic: Core OS Tags:
2w
AlarmKit plays system error tone instead of custom sound files (iOS 26.0)
AlarmKit custom sounds are universally broken in iOS 26.0 stable - instead of playing your custom sound, it plays a system error/timeout beep. I've spent days investigating why custom sounds result in what sounds like an error beep (like when you cancel an operation or hit a timeout) instead of the actual audio file. I can now prove this is an Apple bug, not implementation error. Evidence: Test 1: My Implementation Followed Apple's documentation exactly Tried both bundle and Library/Sounds (as documented) Result: System error beep (not my audio) Test 2: Professional Apps Tested ADHDAlarms (popular AlarmKit example by jacobsapps) https://github.com/jacobsapps/ADHDAlarms Their airhorn.mp3 custom sound: same error beep (not an airhorn) Their default sound: works perfectly Test 3: Device Testing Physical iPhone (iOS 26.0 - 23A341): broken iOS Simulator: broken Not device-specific Files are found correctly, but the actual audio file is never played. Instead, you hear what sounds like a system err
3
0
88
2w
Reply to Safe areas ignored after navigating a WebView/WebPage back in a NavigationStack
Yes, I'm having the same problem (with a wrapped WKWebView, but presumably also the new WebView). The jumping-on-back-button issue was also a problem before iOS 26, but you could work around it by using .ignoresSafeArea(.all, edges: .bottom) However, now in iOS 26, Apple wants the content to flow behind the toolbar, meaning the above fix is no longer suitable. Did you manage to find a workaround?
Topic: Safari & Web SubTopic: General Tags:
2w
Reply to I Need some clarifications about FoundationModels
Happy to help answer some of these! Yes. The Foundation Models framework uses the on-device system foundation model. It's an ~3 billion parameter model designed and trained by Apple. Is the language model provided by FoundationModels designed and trained by Apple? Or is it based on an open‑source model? The exact same on-device model is available on iOS, iPadOS, macOS, and VisionOS on all devices that support Apple Intelligence. Is this on‑device model available on iOS (and iPadOS), or is it limited to macOS? No. The general on-device model you access via Foundation Models is not a coding model and isn't suitable for most code tasks. Xcode on Mac has a separate built-in coding model to help with code completion. When I write code in Xcode, is code completion powered by this same local model? If so, why isn’t the same model available in the left‑hand chat sidebar in Xcode (so that I can use it there instead of relying on ChatGPT)? Yes and no. You can give the on-device model access t
2w
Reply to Supervised devices show wifi setup screen on restart
This behavior still exists in iOS 26.0.1 and iPadOS 26.0.1 even after upgrading the Apple Configurator host to macOS Tahoe 26.0.1. On every restart, Software Update Complete is displayed, along with: Your iPad has been updated to iPadOS 26.0.1. Your iPhone has been updated to iOS 26.0.1. Followed by the Welcome screen with the Get Started button. (Upgrading the Apple Configurator host to macOS Tahoe 26.0.1 did, however, fix the blank Profiles bug in Apple Configurator Version 2.18 10A23.)
2w
Reply to MapKit JS Look Around not pointing camera towards the lat/lng entered
That sample code doesn't show how to create a place from a lat/lng or lookup a place by address, so I'm not sure if it would help my use-case. Even though lat/lng is a 2D point with no heading information, the point were the camera is vs. the requested point creates a line that the camera should be pointing to. The Apple Maps app does this automatically. We're also using Look Around in our iOS app and the heading is calculated there automatically from the same lat/lng we're providing to MapKit JS. See screenshots below: Native app Look Around MapKit JS Look Around
2w
Reply to Incorrect position rendering of WGS84 coordinate in MKMapView: Discrepancy between Apple Maps (Hong Kong) and Amap (Mainland China)
First of all, never use comments for replies. Apparently they don't trigger notifications, for people who use them. But they also don't get noticed at all. WGS 84 is a large and complex standard, among many similar large and complex standards designed for dealing with coordinates on the earth. However, because WGS 84 is such a broad standard, it isn't going to have much practical meaning in more specific contexts like a map display. When it does have a specific meaning, it will typically have some kind of qualifier. It is usually better to refer to EPGS identifiers. Apple Maps is a good example. The Apple Maps display uses EPGS:3857, AKA WGS 84 / Pseudo-Mercator. But most government and professional mapping systems like ArcGIS use EPGS:4326, AKA WGS 84. You can easily see the difference between these two systems in an image or map. The above references to CLLocationCoordinate2d using WGS 84 is also true, but the significance there is related more
2w
APNS Notifications not received on macOS Device
Hello Team, We are currently experiencing an issue where some of our devices are not receiving push notifications. We are sending notifications via the Apple Push Notification portal (https://developer.apple.com/notifications/push-notifications-console/) using the following two requests. However, in both cases, the notifications are not being delivered to the devices. Scenario 1 : When we send a request with apns-push-type set to alert, we receive the following error. Request : curl -v --header authorization: bearer ${AUTHENTICATION_TOKEN} --header apns-topic: com.testcompany.sampletest --header apns-push-type: alert --header apns-priority: 10 --header apns-expiration: 0 --data '{aps:{alert:{title:Test Notification Title,subtitle:Test Notification Sub Title,body:Test Notification Body}}}' --http2 https://api.push.apple.com:443/3/device/*devicetoken* Response: { code: 400, message: bad-request, reason: The device token is inactive for the specified topic. There is no need to send further pushes to the
2
0
111
2w