Apple Maps Guides

Thank you Justin. There's one more quirk I've observed - Apple doesn't expose the analog proximity sensors on the trigger or grip buttons. These are the sense part of Sony's Playstation VR Sense Controller branding ;) In OpenXR / SteamVR with the Playstation VR2 these paths as independent triggers i.e. /user/hand/right/input/r1_sensor, /user/hand/right/input/r2_sensor, /user/hand/right/input/l1_sensor, /user/hand/right/input/l2_sensor, corresponding to the grips & triggers. Yes, this means the l2/r2 triggers have TWO analog capabilities - one for the analog relative touch/proximity, and one for the analog degree of trigger pull (which can be accessed via the .value on the button). Since this is an entirely new thing, should I update my existing feedback or file a new one?

You might be better off contacting Apple directly rather than posting on the forums if this happens again. No one on the forums can fix this, unless an Apple employee comes across your post and investigates it - and they don't investigate everything. If you're paying Apple for the service and the service isn't working, there must be some contact details you can use?

Thanks for asking @darkpaw, as you can see in the original thread, it fixed itself after talking to an Apple Engineer, but it takes time. And during this time, people complain and demand refunds...

I have also feedback using apple FeedbackAssistant system. FB21353175 (iOS26 Live Activity always display in Dark Mode)

Is there an Apple employee who can help us with this issue? Our business bank account is with UBS Switzerland and has been registered in App Store Connect for over five years. All payouts have worked without any issues during this time. App Store Connect has now suddenly marked the account as invalid, even though nothing has changed and the account is fully functional. A payout from Google Play was credited to this account today. We temporarily added a private account, removed the UBS account, and then added it again. However, the error message in App Store Connect remains unchanged. We need payouts to continue going to this account, as our accounting and business processes depend on it. Other business accounts exist but are used for different purposes. The error message refers to an incorrect “routing number”. However, when adding a Swiss bank account, there is no routing number field. Instead, a bank clearing number is required. We selected this number using App Store Connect’s search, and it match

Deedback Assistant ID: FB21352672 (Apple Pay In-App Provisioning – Apple server failure when adding a card)

Does Apple suggest that developers transition to arm64-only and drop support for arm64_32 devices? No — Apple Watch Series 9 and later, and Apple Watch Ultra 2 and later all support the arm64 architecture. There are many Apple Watch devices that run watchOS versions your app likely supports beyond that list, so you need to keep the arm64_32 architecture around for those devices. As noted in the announcement, you'll want to use the Standard Architectures build setting for your watchOS app, and that will automatically build the right set of supported architectures for your app, which will include arm64_32 as well as arm64. If we add support for both arm64_32 and arm64, the binary will almost certainly exceed the 75 MB app size limit, and potentially violate the size constraints for each architecture slice as well. What size constraints per architecture are you thinking of? The Maximum build file sizes documentation lists such a requirement for iOS apps in the iOS 7 and 8 time

Here is the code of my message extension, if that helps. I am indeed trying to write to the shared storage of the App Groups import os.log // Apple's modern, fast, privacy-safe logging system class NotificationService: UNNotificationServiceExtension { private let log = OSLog( subsystem: Bundle.main.bundleIdentifier!, category: pushnotificationsmessageextension ) var contentHandler: ((UNNotificationContent) -> Void)! // A mutable copy of the notification content — this is what we'll modify or save var bestAttemptContent: UNMutableNotificationContent? // Main entry point — called every time a push arrives with `mutable-content: 1` override func didReceive( _ request: UNNotificationRequest, withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void ) { // Save the handler so we can call it later (required!) self.contentHandler = contentHandler // Make a mutable copy so we can modify title, body, attachments, etc. bestAttemptContent = request.content.mutableCopy() as? UNMutableNot