Search results for

“Apple Maps Guides”

155,900 results found

Post

Replies

Boosts

Views

Activity

Reply to NEURLFilter production build fails with _NSURLErrorPrivacyProxyFailureKey — how to provision OHTTP privacy proxy for bundle?
It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. does it take a long time to get approved? I’m not involved in the approval process, so I can’t give you any concrete numbers. But based on what I’ve seen reported by other folks in the forums, it seems to be more like weeks than days. I cannot find a way to see the status of my request. Yeah, that’s my understanding as well )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
NEURLFilter production build fails with _NSURLErrorPrivacyProxyFailureKey — how to provision OHTTP privacy proxy for bundle?
Summary I'm implementing NEURLFilter with the com.apple.developer.networking.networkextension.url-filter-provider entitlement for a system-wide URL filtering feature. The feature works perfectly in development-signed builds (connecting successfully to my PIR server over extended testing) but every production-signed build fails before any network call is made. NEURLFilterManager reports .serverSetupIncomplete (code 9). After installing the NetworkExtension debug profile, the unredacted com.apple.CipherML logs reveal the cause: no privacy proxy is provisioned for this bundle identifier, and the connection is configured proxy fail closed. Environment iOS 26 Entitlement: com.apple.developer.networking.networkextension.url-filter-provider Extension point: com.apple.networkextension.url-filter-control PIR server configured via NEURLFilterManager.setConfiguration(...) Privacy Pass issuer configured Dev-signed builds: working correctly, connecting to the PIR server Production-signed builds (both TestFlight and distri
2
0
210
1w
Reply to Calling SecKeychainUnlock with a locked keychain and an invalid password returns errSecSuccess on macOS 26.4
[quote='883774022, oleksandr91, /thread/821894?answerId=883774022#883774022, /profile/oleksandr91'] We’re using SecKeychainChangePassword to change the keychain password. [/quote] To be clear, that’s not API, and thus not supported by DTS. There isn’t a good way to change the password for a file-based keychain. I’ve seen folks do it by spawning the security tool with the set-keychain-password command, but that’s problematic on at least two levels: Using command-line tools as API is usually a bad option. Especially in a case like this, where the tool was clearly designed to be used by a user. You either have to pass in the passwords as arguments or do the pseudo-TTY dance, neither of which is ideal. I discussed your issue with some folks internally and we couldn’t come up with any good suggestions for you. What you really want is an API to change the user’s password in all relevant contexts (OD, login keychain, data protection keychain, FileVault, and probably more than I’m forgetting). Such an API does not ex
Topic: Privacy & Security SubTopic: General Tags:
1w
Reply to Programmatic IP Discovery for VZVirtualMachine in an App Store Sandbox
i [want] to determine ip address of guest os without any cooperation from guest. Thanks for confirming that. This is a fundamentally tricky problem to solve, at least in the general case. The guest chooses how it’s going to assign IP addresses to an interface, and the host has no direct control over that choice. However, there may be an indirect way to do this: Virtualization framework lets you create a network that’s backed by a vmnet network (VZVmnetNetworkDeviceAttachment). vmnet framework lets your configure a network with a specific DHCP mapping (vmnet_network_configuration_add_dhcp_reservation). There are some significant caveats: The guest must default to using DHCP. You can’t support bridged mode (VMNET_BRIDGED_MODE), because in bridged mode the guest isn’t talking to the vmnet DHCP server. This is all new in macOS 26. But otherwise I think it’ll work. So please try it out and let me know how you get along. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten D
Topic: App & System Services SubTopic: Core OS Tags:
1w
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
We're experiencing the same issue and wanted to add our voice to this thread. Our app also has the Contactless Pass Provisioning capability approved and has been working fine for a long time, but we started seeing the exact same Ineligible profile error a couple of days ago — without any changes on our end. We've confirmed that the entitlement (com.apple.developer.contactless-payment-pass-provisioning) is present in the downloaded provisioning profile, and the capability is still enabled in the Developer Portal. Despite that, Xcode continues to mark our profiles as ineligible. This is now blocking us from releasing an important bug fix to our customers. We'd really appreciate any update on the timeline for a resolution. Is there anything we can do in the meantime to work around this, or should we simply wait for a fix on Apple's side? Thank you for escalating this internally.
1w
Reply to First-time notarization submissions stuck "In Progress" — two submissions, 15+ hours
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
1w
Reply to Wi-Fi Aware UpgradeAuthorization Failing
I think you should file a bug about this. It’s hard to be sure exactly what’s going on, but your description certainly sounds like there’s an issue on the Apple side of the fence. Please post your bug number, just for the record. I have some general advice about filing Wi-Fi bug reports in… ah… Filing a Wi-Fi Bug Report. In this case, however, I recommend that you also install the Accessory Setup Kit for iOS/iPadOS debug profile, available from our Bug Reporting > Profiles and Logs page. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
Reply to SecItemCopyMatching returns errSecAuthFailed (-25293) after macOS 26.4 upgrade — persists until SecKeychainLock/Unlock
[quote='822120021, AntonPastrevich, /thread/822120, /profile/AntonPastrevich'] We've filed FB22448572 for this [/quote] Thanks. That’s the best path forward for this. [quote='822120021, AntonPastrevich, /thread/822120, /profile/AntonPastrevich'] Is there a known issue with securityd’s keychain authentication after 26.4? [/quote] Well there is now that you’ve filed a bug about it (-: Seriously though, as I mentioned on that other thread you found, macOS 26.4 has significant changes to how we unlock the login keychain. In that thread, the developer is doing something unusual, and it’s not clear what the right path forward is. But in your case my understanding is that you’re doing something pedestrian — accessing a keychain item from early in your app’s lifecycle — and that makes the path forward clear: File a bug so that the keychain team can investigate. Which is what you’ve done (-: [quote='822120021, AntonPastrevich, /thread/822120, /profile/AntonPastrevich'] Would migrating to the data protection keychain …
1w
SecItemCopyMatching returns errSecAuthFailed (-25293) after macOS 26.4 upgrade — persists until SecKeychainLock/Unlock
We've filed FB22448572 for this, but posting here in case others are hitting the same issue. After upgrading macOS from 26.3.2 to 26.4, SecItemCopyMatching returns errSecAuthFailed (-25293) when reading kSecClassGenericPassword items from the default login keychain. The keychain reports as unlocked, but all authenticated operations fail. The error doesn't self-resolve — we've observed it persisting for 7+ minutes across repeated calls and process restarts. The only workaround we've found is SecKeychainLock(nil) followed by SecKeychainUnlock(nil, 0, nil, false), which prompts the user for their password and clears the stale state. Apple's own security CLI tool also fails while the keychain is in this state: $ security show-keychain-info ~/Library/Keychains/login.keychain-db security: SecKeychainCopySettings .../login.keychain-db: The user name or passphrase you entered is not correct. The trigger seems to be process lifecycle — a new process accessing the keychain early in startup (e.g., from the app
1
0
285
1w
Apple Pay Sandbox: onpaymentauthorized not fired after successful authentication (started March 6)
Hello, We are encountering an issue with Apple Pay on the Web in the sandbox environment where payments cannot be completed because the onpaymentauthorized event is not triggered. The same implementation was working normally until March 5, but the issue started occurring consistently from March 6 without any changes to our code, certificates, or merchant configuration. Environment Apple Pay on the Web (JavaScript) Safari (iOS / macOS) Apple Pay Sandbox Merchant domain verified Merchant validation succeeds Observed Flow The Apple Pay flow proceeds normally until authentication: User clicks the Apple Pay button ApplePaySession.begin() is called onvalidatemerchant fires Merchant validation request succeeds completeMerchantValidation() is called Apple Pay sheet is displayed User authenticates with Face ID / Touch ID onpaymentauthorized is never triggered Because this event never fires, the payment token is not returned and the payment cannot proceed. ApplePayS
2
0
360
1w
App Store connect api key generation.
Hi, I can't generate new key in the App Store connect dashboard. I'm receiving this as error. { errors : [ { id : 59e466f3-70aa-4798-b183-8a4903a7c2cc, status : 403, code : FORBIDDEN_ERROR.PLA_NOT_VALID, title : Operation is forbidden because of PLA status., detail : } ] } I'm the account owner and I accepted all the policy agreements in both apple developper dashboard and app connect dashboard. what's goin on?
2
0
799
1w
Reply to WKWebView customUserAgent replaces system User-Agent with NetworkingExtension identifier on iOS 26.4
It looks like you’re trying to report a bug. If so, the best place to do that is in Feedback Assistant. See Bug Reporting: How and Why? for lots of hints and tips for that process. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Safari & Web SubTopic: General Tags:
1w
Reply to UITextField and UITextView abnormally popped up the network permission application interface
[quote='883809022, Mingmiu, /thread/822198?answerId=883809022#883809022, /profile/Mingmiu'] I reported it as FB22333352 [/quote] Thanks. That’s definitely the right path forward for this. IMPORTANT I noticed that you didn’t attach a sysdiagnose log to your bug report. Even though this problem is easy to reproduce, a sysdiagnose will help with the routing of your issue internally. So please reproduce the problem, trigger a sysdiagnose log, and then attach it to this bug. For more information about sysdiagnose logs, see Bug Reporting > Profiles and Logs. For context, that alert says: 允许 “testNetwork”使用无线 数据? 关闭无线数据时,部分功能可能无法 使用。 [无线局域网与蜂窝网络] [仅限无线局域网] [[不允许]] A machine translation is: Allow testNetwork to use wireless data? When wireless data is turned off, some functions may not be available. [Wireless LAN and Cellular Network] [Wireless LAN only] [[Now Allowed]] This alert only shows up if the iPhone was bought in China, where iOS gives the user the option to control an app’s access to Wi-Fi (normally the
Topic: UI Frameworks SubTopic: UIKit Tags:
1w
Reply to Developer Program enrollment still pending after payment
Dear BearlyMad, Thank you for your comment! I accidentally made a duplicate payment, so I am currently contacting Apple Developer Support to request a refund.
Replies
Boosts
Views
Activity
1w
Reply to NEURLFilter production build fails with _NSURLErrorPrivacyProxyFailureKey — how to provision OHTTP privacy proxy for bundle?
It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. does it take a long time to get approved? I’m not involved in the approval process, so I can’t give you any concrete numbers. But based on what I’ve seen reported by other folks in the forums, it seems to be more like weeks than days. I cannot find a way to see the status of my request. Yeah, that’s my understanding as well )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
1w
NEURLFilter production build fails with _NSURLErrorPrivacyProxyFailureKey — how to provision OHTTP privacy proxy for bundle?
Summary I'm implementing NEURLFilter with the com.apple.developer.networking.networkextension.url-filter-provider entitlement for a system-wide URL filtering feature. The feature works perfectly in development-signed builds (connecting successfully to my PIR server over extended testing) but every production-signed build fails before any network call is made. NEURLFilterManager reports .serverSetupIncomplete (code 9). After installing the NetworkExtension debug profile, the unredacted com.apple.CipherML logs reveal the cause: no privacy proxy is provisioned for this bundle identifier, and the connection is configured proxy fail closed. Environment iOS 26 Entitlement: com.apple.developer.networking.networkextension.url-filter-provider Extension point: com.apple.networkextension.url-filter-control PIR server configured via NEURLFilterManager.setConfiguration(...) Privacy Pass issuer configured Dev-signed builds: working correctly, connecting to the PIR server Production-signed builds (both TestFlight and distri
Replies
2
Boosts
0
Views
210
Activity
1w
Reply to Calling SecKeychainUnlock with a locked keychain and an invalid password returns errSecSuccess on macOS 26.4
[quote='883774022, oleksandr91, /thread/821894?answerId=883774022#883774022, /profile/oleksandr91'] We’re using SecKeychainChangePassword to change the keychain password. [/quote] To be clear, that’s not API, and thus not supported by DTS. There isn’t a good way to change the password for a file-based keychain. I’ve seen folks do it by spawning the security tool with the set-keychain-password command, but that’s problematic on at least two levels: Using command-line tools as API is usually a bad option. Especially in a case like this, where the tool was clearly designed to be used by a user. You either have to pass in the passwords as arguments or do the pseudo-TTY dance, neither of which is ideal. I discussed your issue with some folks internally and we couldn’t come up with any good suggestions for you. What you really want is an API to change the user’s password in all relevant contexts (OD, login keychain, data protection keychain, FileVault, and probably more than I’m forgetting). Such an API does not ex
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to Programmatic IP Discovery for VZVirtualMachine in an App Store Sandbox
i [want] to determine ip address of guest os without any cooperation from guest. Thanks for confirming that. This is a fundamentally tricky problem to solve, at least in the general case. The guest chooses how it’s going to assign IP addresses to an interface, and the host has no direct control over that choice. However, there may be an indirect way to do this: Virtualization framework lets you create a network that’s backed by a vmnet network (VZVmnetNetworkDeviceAttachment). vmnet framework lets your configure a network with a specific DHCP mapping (vmnet_network_configuration_add_dhcp_reservation). There are some significant caveats: The guest must default to using DHCP. You can’t support bridged mode (VMNET_BRIDGED_MODE), because in bridged mode the guest isn’t talking to the vmnet DHCP server. This is all new in macOS 26. But otherwise I think it’ll work. So please try it out and let me know how you get along. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten D
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
We're experiencing the same issue and wanted to add our voice to this thread. Our app also has the Contactless Pass Provisioning capability approved and has been working fine for a long time, but we started seeing the exact same Ineligible profile error a couple of days ago — without any changes on our end. We've confirmed that the entitlement (com.apple.developer.contactless-payment-pass-provisioning) is present in the downloaded provisioning profile, and the capability is still enabled in the Developer Portal. Despite that, Xcode continues to mark our profiles as ineligible. This is now blocking us from releasing an important bug fix to our customers. We'd really appreciate any update on the timeline for a resolution. Is there anything we can do in the meantime to work around this, or should we simply wait for a fix on Apple's side? Thank you for escalating this internally.
Replies
Boosts
Views
Activity
1w
Reply to Issue when repeated AP connections started and stopped multiple times
Lemme start you out with Understanding NEHotspotConfigurationErrorInternal. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
1w
Reply to First-time notarization submissions stuck "In Progress" — two submissions, 15+ hours
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
1w
Reply to Wi-Fi Aware UpgradeAuthorization Failing
I think you should file a bug about this. It’s hard to be sure exactly what’s going on, but your description certainly sounds like there’s an issue on the Apple side of the fence. Please post your bug number, just for the record. I have some general advice about filing Wi-Fi bug reports in… ah… Filing a Wi-Fi Bug Report. In this case, however, I recommend that you also install the Accessory Setup Kit for iOS/iPadOS debug profile, available from our Bug Reporting > Profiles and Logs page. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
1w
Reply to SecItemCopyMatching returns errSecAuthFailed (-25293) after macOS 26.4 upgrade — persists until SecKeychainLock/Unlock
[quote='822120021, AntonPastrevich, /thread/822120, /profile/AntonPastrevich'] We've filed FB22448572 for this [/quote] Thanks. That’s the best path forward for this. [quote='822120021, AntonPastrevich, /thread/822120, /profile/AntonPastrevich'] Is there a known issue with securityd’s keychain authentication after 26.4? [/quote] Well there is now that you’ve filed a bug about it (-: Seriously though, as I mentioned on that other thread you found, macOS 26.4 has significant changes to how we unlock the login keychain. In that thread, the developer is doing something unusual, and it’s not clear what the right path forward is. But in your case my understanding is that you’re doing something pedestrian — accessing a keychain item from early in your app’s lifecycle — and that makes the path forward clear: File a bug so that the keychain team can investigate. Which is what you’ve done (-: [quote='822120021, AntonPastrevich, /thread/822120, /profile/AntonPastrevich'] Would migrating to the data protection keychain …
Replies
Boosts
Views
Activity
1w
SecItemCopyMatching returns errSecAuthFailed (-25293) after macOS 26.4 upgrade — persists until SecKeychainLock/Unlock
We've filed FB22448572 for this, but posting here in case others are hitting the same issue. After upgrading macOS from 26.3.2 to 26.4, SecItemCopyMatching returns errSecAuthFailed (-25293) when reading kSecClassGenericPassword items from the default login keychain. The keychain reports as unlocked, but all authenticated operations fail. The error doesn't self-resolve — we've observed it persisting for 7+ minutes across repeated calls and process restarts. The only workaround we've found is SecKeychainLock(nil) followed by SecKeychainUnlock(nil, 0, nil, false), which prompts the user for their password and clears the stale state. Apple's own security CLI tool also fails while the keychain is in this state: $ security show-keychain-info ~/Library/Keychains/login.keychain-db security: SecKeychainCopySettings .../login.keychain-db: The user name or passphrase you entered is not correct. The trigger seems to be process lifecycle — a new process accessing the keychain early in startup (e.g., from the app
Replies
1
Boosts
0
Views
285
Activity
1w
Apple Pay Sandbox: onpaymentauthorized not fired after successful authentication (started March 6)
Hello, We are encountering an issue with Apple Pay on the Web in the sandbox environment where payments cannot be completed because the onpaymentauthorized event is not triggered. The same implementation was working normally until March 5, but the issue started occurring consistently from March 6 without any changes to our code, certificates, or merchant configuration. Environment Apple Pay on the Web (JavaScript) Safari (iOS / macOS) Apple Pay Sandbox Merchant domain verified Merchant validation succeeds Observed Flow The Apple Pay flow proceeds normally until authentication: User clicks the Apple Pay button ApplePaySession.begin() is called onvalidatemerchant fires Merchant validation request succeeds completeMerchantValidation() is called Apple Pay sheet is displayed User authenticates with Face ID / Touch ID onpaymentauthorized is never triggered Because this event never fires, the payment token is not returned and the payment cannot proceed. ApplePayS
Replies
2
Boosts
0
Views
360
Activity
1w
App Store connect api key generation.
Hi, I can't generate new key in the App Store connect dashboard. I'm receiving this as error. { errors : [ { id : 59e466f3-70aa-4798-b183-8a4903a7c2cc, status : 403, code : FORBIDDEN_ERROR.PLA_NOT_VALID, title : Operation is forbidden because of PLA status., detail : } ] } I'm the account owner and I accepted all the policy agreements in both apple developper dashboard and app connect dashboard. what's goin on?
Replies
2
Boosts
0
Views
799
Activity
1w
Reply to WKWebView customUserAgent replaces system User-Agent with NetworkingExtension identifier on iOS 26.4
It looks like you’re trying to report a bug. If so, the best place to do that is in Feedback Assistant. See Bug Reporting: How and Why? for lots of hints and tips for that process. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Safari & Web SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to UITextField and UITextView abnormally popped up the network permission application interface
[quote='883809022, Mingmiu, /thread/822198?answerId=883809022#883809022, /profile/Mingmiu'] I reported it as FB22333352 [/quote] Thanks. That’s definitely the right path forward for this. IMPORTANT I noticed that you didn’t attach a sysdiagnose log to your bug report. Even though this problem is easy to reproduce, a sysdiagnose will help with the routing of your issue internally. So please reproduce the problem, trigger a sysdiagnose log, and then attach it to this bug. For more information about sysdiagnose logs, see Bug Reporting > Profiles and Logs. For context, that alert says: 允许 “testNetwork”使用无线 数据? 关闭无线数据时,部分功能可能无法 使用。 [无线局域网与蜂窝网络] [仅限无线局域网] [[不允许]] A machine translation is: Allow testNetwork to use wireless data? When wireless data is turned off, some functions may not be available. [Wireless LAN and Cellular Network] [Wireless LAN only] [[Now Allowed]] This alert only shows up if the iPhone was bought in China, where iOS gives the user the option to control an app’s access to Wi-Fi (normally the
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
1w