Search results for

Apple Maps Guides

150,132 results found

Post

Replies

Boosts

Views

Activity

Reply to Degrade IOS 18 beta to 17 beta to test legacy iOS
Ed addressed your specific question, but I want to address about the big picture… It seems like your goal is to downgrade an iOS device from a newer version of iOS to an older version. There’s no supported way to do that [1] on iOS or any of its ‘child’ platforms [2]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] The only exception being during the beta cycle of a new OS, where it’s possible to erase and device and install the most recent non-beta OS. [2] It is possible to do this with macOS.
3d
Reply to [iPadOS 26] EACCES (Permission Denied) on UDP Broadcast despite Multicast Networking Entitlement
NWConnection isn’t really set up to deal with UDP broadcasts. My advice, sadly, is that you use BSD Sockets for this. BSD Sockets is a much harder API to use correctly. I have lots of hints and tips in Broadcasts and Multicasts, Hints and Tips. The most critical point is that, when working with broadcasts and multicasts, you should target a specific interface. If you try to send a broadcast without specifying the interface, it’s hard to predict which interface it’ll be sent over. [quote='805719021, Tetsuya_0, /thread/805719, /profile/Tetsuya_0'] I suspect this may be a regression bug in the iPadOS 26 security sandbox [/quote] Well, it’s certainly a regression, but I doubt it’s in the sandbox. Usually the sandbox causes things to fail with EPERM. You are feel to file a bug about NWConnection, but I’m concerned that it’ll struggle to get traction given the state of broadcast support in Network framework. If you need a fix for this in the short-to-medium term, I recommend that you switch to BSD Sockets. If you d
3d
[iPadOS 26] EACCES (Permission Denied) on UDP Broadcast despite Multicast Networking Entitlement
My application (using a nested framework for networking) was working correctly on iPadOS 18, but failed to perform a UDP broadcast operation after upgrading the device to iPadOS 26. The low-level console logs consistently show a Permission denied error. Symptoms & Error Message: When attempting to send a UDP broadcast packet using NWConnection (or a similar low-level socket call within the framework), the connection fails immediately with the following error logged in the console: nw_socket_service_writes_block_invoke [C2:1] sendmsg(fd 6, 124 bytes) [13: Permission denied] (Error code 13 corresponds to EACCES). Verification Steps (What I have checked): Multicast Networking Entitlement is Approved and Applied: The necessary entitlement (com.apple.developer.networking.multicast) was granted by Apple. The Provisioning Profile used for signing the Host App Target has been regenerated and explicitly includes Multicast Networking capability (see attached screenshot). I confirmed that Entitlements canno
1
0
60
3d
Watchface Sharing Fails in TestFlight/AppStore on iOS/watchOS 26 (Works in Dev Builds)
Hello everyone, I am facing a critical and blocking issue regarding watchface sharing on iOS/watchOS 26 and would appreciate any immediate guidance or updates from the community or Apple. The Problem: We are unable to share watchfaces containing any complications from our app in TestFlight and App Store distribution environments. The operation fails with an error indicating the app and complications are unavailable. However, the exact same functionality works perfectly in all development builds (both Debug and Release schemes). This issue was not present on iOS/watchOS 18. We have testing, including: Successfully sharing the watchface in development environments. The failure occurs consistently across TestFlight and App Store builds. Exporting the watchface configuration from a TestFlight/AppStore build on iOS, transferring it to a paired watch, and finding it still shows as Unavailable. We suspect this may be related to the dual-target architecture of Watch apps. Any guidance or updates would be gre
2
0
107
3d
Reply to Watchface Sharing Fails in TestFlight/AppStore on iOS/watchOS 26 (Works in Dev Builds)
We found the solution. For iOS/watchOS 26, you MUST: Migrate from the legacy Watch dual-target to a single-target. Generate the watch face file within your TestFlight build and bundle it with your app; do not generate it in a development environment. This ensures the complications are associated with a valid App Store ID. This strict validation appears to be new in iOS/watchOS 26, as it was not present in iOS/watchOS 18. Reference: Sharing Apple Watch Faces.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
3d
Reply to In-App purchase no longer works with User-based VPP?
The administrator cannot use the App and Books API to make in-app purchases. A user can make in-app purchases when the administrator licensed the app using a user-based license. In this case the in-app purchase is charged to the Apple Account associated with that license. Managed Apple Accounts do not support commerce, so they cannot be used to make in-app purchases. If the behavior you're seeing does not match the above, please reproduce the issue, take a sysdiagnose, and submit feedback with the sysdiagnose attached, and provide timestamps indicating when the in-app purchase failed.
3d
iOS 26: Maps share sheet no longer provides com.apple.mapkit.map-item and only shares short maps.apple/p/... URLs (how to get coordinates?)
Since iOS 26, the Apple Maps share sheet no longer provides a com.apple.mapkit.map-item attachment when sharing a location to my Share Extension. Additionally, on real devices the shared URL is now a short link (https://maps.apple/p/...), which does not contain coordinates. On the simulator, the URL still includes coordinates (as in previous iOS versions). I'm trying to find the official or recommended way to extract coordinates from these new short URLs. Environment: Devices: iPhone (real device) on iOS 26.0 / 26.0.1 Simulator: iOS 26.0 / 26.0.1 simulator (behaves like iOS 18 — see below) App: Share Extension invoked from Apple Maps -> Share -> my app Xcode: 26.0.1 Steps to Reproduce Open Apple Maps on iOS 26 (real device). Pick a POI (store/restaurant). Share -> choose my share extension. iOS 18 and earlier (lldb) po extensionContext?.inputItems ▿ Optional> ▿ some : 1 element - 0 : - userInfo: { NSExtensionItemAttachmentsKey = ( {types = (p
2
0
138
3d
Reply to iOS 26: Maps share sheet no longer provides com.apple.mapkit.map-item and only shares short maps.apple/p/... URLs (how to get coordinates?)
We made a change this is rolling out, so that you'll begin to see the payloads you were using in the past through your Share extension over the next day. While the original details are returning to mitigate impacts to your app, it would be helpful for us to know the complete set of parameters you are parsing out of the URL, so we understand what data you're looking for when a place is shared to your app from Apple Maps. The URL is not intended to be a structured API or parsed out like this, and so I'd appreciate if you could create an enhancement request in Feedback Assistant for a representation of what you need that doesn't require parsing the URL like this. Please post the FB number here so I can follow-up on it internally. — Ed Ford,  DTS Engineer
3d
Reply to Unable to retrieve secure element pass after adding to Apple Wallet?
Hi @gtaylor, Just wanted to add a bit more context for others finding this post. For anyone else receiving an empty payment library for the user's device, please confirm with your PNO, card issuer, or service provider, that both Wallet extensions are included in the configuration metadata, along with the main issuer app. For more information, please see the section titled PNO Pass Metadata Configuration on the following page: Passes need to include the extension’s bundle identifier in associatedApplicationIdentifiers to ensure accurate status of existing passes in Apple Wallet. To learn more about this identifier key, see PNO Pass Metadata Configuration. Apple Pay on the Web Demo: Wallet Extensions https://applepaydemo.apple.com/wallet-extensions#pnoPassMetadata Cheers, Paris X Pinkney |  WWDR | DTS Engineer
3d
Unable to retrieve secure element pass after adding to Apple Wallet?
I am adding In-App provisioning to my app. I am able to access the Apple Pay Sandbox and I have successfully tested adding a secure element/payment pass to Apple Wallet. However, once the pass has been added to the wallet, I can not access or retrieve the pass from my app. I have confirmed with the PNO that the PNO Pass Metadata Configuration in the testing environment include the correct metadata for associatedApplicationIdentifiers and associatedStoreIdentifiers. Does anyone know why I am having this issue and how I can resolve it? Steps used to access pass in Apple Wallet I am unable to view the pass when I attempt to access it using the PKPassLibrary function as follows: let library = PKPassLibrary() if #available(iOS 13.4, *) { // This returns an empty array library.passes(of: .secureElement) } else { // This also returns an empty array library.passes(of: .payment) } // This returns an empty array too library.passes() Steps used to add pass to Apple Wallet These are th
7
0
5.2k
3d
Critical Bug in iOS 18.1 RC and watchOS 11.1 RC - WidgetKit Complications Not Syncing
I've encountered a major issue with the iOS 18.1 RC and watchOS 11.1 RC. It appears that complications running on WidgetKit cannot be synced as .watchface to these new release candidates. The error message indicates that the Watch Faces app and complication are not available, which is affecting all apps utilizing WidgetKit. This issue renders all WidgetKit-based complications unusable on watchOS 11.1 RC. It’s a serious problem for those of us who rely on these complications for our apps and for users expecting consistent functionality. APPLE, PLEASE FIX THIS ISSUE ASAP! This bug is a significant setback for developers and users alike, and any guidance or updates would be greatly appreciated.
4
0
910
3d
[iPadOS 28] EACCES (Permission Denied) on UDP Broadcast despite Multicast Networking Entitlement
My application (using a nested framework for networking) was working correctly on iPadOS 18, but failed to perform a UDP broadcast operation after upgrading the device to iPadOS 28. The low-level console logs consistently show a Permission denied error. Symptoms & Error Message: When attempting to send a UDP broadcast packet using NWConnection (or a similar low-level socket call within the framework), the connection fails immediately with the following error logged in the console: nw_socket_service_writes_block_invoke [C2:1] sendmsg(fd 6, 124 bytes) [13: Permission denied] (Error code 13 corresponds to EACCES). Verification Steps (What I have checked): Multicast Networking Entitlement is Approved and Applied: The necessary entitlement (com.apple.developer.networking.multicast) was granted by Apple. The Provisioning Profile used for signing the Host App Target has been regenerated and explicitly includes Multicast Networking capability (see attached screenshot). I confirmed that Entitlements canno
1
0
52
3d