“Apple Maps Guides”

Summary On macOS 26.4.1 (25E253), iCloud Drive file uploads can enter a silent deadlock where every upload attempt fails at the transport layer. No error is surfaced anywhere — not in Finder, not in System Settings, not in the iCloud status panel. The upload queue simply stops. Other iCloud services (Photos, Mail, App Store) continue to work normally through the same networking infrastructure at the same time. Root Cause The issue is a stale HTTP/3 (QUIC) session cached in the user-level nsurlsessiond process's BackgroundConnectionPool. The deadlock cycle: cloudd requests an upload to the GCS storage endpoint nsurlsessiond provides the cached (broken) HTTP/3 session The TLS handshake succeeds, but the body upload dies mid-transfer (err=T, requestDuration=-1.000, responseHeaderBytes=0) cloudd retries with a new connectionUUID — but nsurlsessiond still routes through the same poisoned QUIC session This repeats indefinitely Killing cloudd alone does not help — nsurlsessiond retains the poisoned pool. Only killin

I've been able to run this sample project with the PIRServer. But the urls are still not blocked. https://developer.apple.com/documentation/networkextension/filtering-traffic-by-url https://github.com/apple/pir-service-example I got this on the log Received filter status change:

Hi everyone, We’re facing an issue while trying to change the Primary Language / Primary Locale of a long-standing live iOS app in App Store Connect. The app has been live for 4–6+ years. When attempting to update the Primary Locale from App Information, we receive the following error: “Primary Locale couldn’t be saved because you must first provide all the required screenshots for each version in this language.” However: The target localization (English – UK) already exists. All required screenshot sets are uploaded. No screenshot sections are blank (iPhone and iPad – all visible display sizes). Both the live version and the version in review contain complete screenshot sets. No Apple Watch or iMessage extensions are currently included in the build. A clean build has been uploaded and selected. Removing the version from review does not resolve the issue. There are no visible validation errors in the UI. This appears to be either: A hidden backend validation requirement, A legacy platform association

I can't seem to find any way to update my now legacy details since moving country. My general apple account has changed just fine but my developer account still shows as UK and no way to update. Any ideas?

In my CarPlaySceneDelegate.swift, I have two tabs: The first tab uses a CPListImageRowItem with a CPListImageRowItemRowElement. The scroll direction is inverted, and the side button does not function correctly. The second tab uses multiple CPListItem objects. There are no issues: scrolling works in the correct direction, and the side button behaves as expected. Steps To Reproduce Launch the app. Connect to CarPlay. In the first tab, scroll up and down, then use the side button to navigate. In the second tab, scroll up and down, then use the side button to navigate. As observed, the scrolling behavior is different between the two tabs. Code Example: import CarPlay import UIKit class CarPlaySceneDelegate: UIResponder, CPTemplateApplicationSceneDelegate { var interfaceController: CPInterfaceController? func templateApplicationScene( _ templateApplicationScene: CPTemplateApplicationScene, didConnect interfaceController: CPInterfaceController ) { self.interfaceController = interfaceController downloadImageAndSetup

Hi, I purchased the Apple Developer subscription yesterday and the payment has already been successfully processed. However, my account is still not showing as active. Given that the payment has been completed, I would expect the activation to be reflected by now. This delay is impacting my ability to proceed with development and deployment, so I need clarification on what is causing the issue. Please review my account status as soon as possible and let me know: • If there is any pending verification or required action on my end • The reason for the delay in activation • The expected timeframe for the subscription to become active I would appreciate a prompt resolution to this matter. Thank you.

Hi, A few of my apps will be able to sync with iCloud. So I do realize that we're not allowed to mention any Apple-related names in our app descriptions. Looking for ideas on how to state that the app works with iCloud without saying iCloud. Thanks, Dan Uff

Hello! I’m building a VoIP app for iPhone and Apple Watch using PushKit and CallKit. I’m trying to understand the recommended watchOS architecture for this kind of setup. What we would like is for the watch to behave as an endpoint for incoming calls, so that when a call comes in the user can answer on either the iPhone or the watch. My understanding is that VoIP notifications are not supported on watchOS, so for incoming calls what we ended up having to do was send the watch a regular APNs alert notification and only start the actual call setup after the user interacts with it. This isn’t ideal, and the notification often appears a few seconds late. What we would like to be able to do is present the incoming call on the watch more like how FaceTime calls appear on Apple Watch. So I wanted to ask whether this is the intended pattern for a companion watchOS VoIP app. Is using a regular APNs alert notification the correct way to surface an incoming call on the watch, or is there a better suppo