I am developing a simple watch app and I use my personal watch for development with Xcode. Personal watch is series 10 gps only. I have two other watches that I want to use for testing the app, but not needing them to be connected to Xcode. The test watches have cellular option, and I need a cell plan per watch because the watches need to be standalone, not counting initial setup. To get the standalone cell plan the watches need to be configured using AWFK. Here is what I have tried/current issues. I switch between all three watches on my phone using the watch app. Originally tried to put test watches in developer mode, thinking I would connect to Xcode, developer mode is not available when watch is setup using AWFK. Pushed the watch app to apple connect, setup TestFlight group, added the test users and my phone user, accepted invites TestFlight is installed on my phone, I see the testflight setup for the watch app I set a test watch using watch app on the phone, run install for the test app from Tes
Search results for
Apple Maps Guides
151,695 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
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
Topic:
App Store Distribution & Marketing
SubTopic:
General
I'm encountering a strange behavior with one of my home's on Home app while I'm off network. When I launch the app it indicates that the hub is not responding and all of my devices are unavailable. However, on the menu bar at the bottom if I switch to Automation and back to Home the pop-up goes away and my devices are accessible again (sometimes this take a few attempts). Siri is also able to consistently control my devices without an issue. The same behavior occurs with Home app on other devices (e.g. Mac) and with other members that have access to the household. 3rd party HomeKit app like Controller does not have an issue. This issue began with iOS 26 and I haven't had much luck resolving the issue. I already tried rebooting everything, including removing and re-adding an Apple TV (home hub). I have other homes shared with me in Home App with similar network/environment that are still working. The home I'm having issues has the most number of devices though (over 100+).
Apple sent a final reminder asking developers to complete the updated age rating questions in App Store Connect. Final reminder: Answer the updated age ratings questions. We’re reaching out because you have not provided responses to the updated age ratings questions in the App Information section of your app in App Store Connect. If you don’t answer these questions by January 31, 2026, you won’t be able to submit app updates in App Store Connect. The email says that if the age rating questions are not answered by 31 January 2026, you will not be able to submit app updates. What is not clear is what actually happens after that date. Many of us are in the middle of development and may not be ready to submit a new build before the deadline. The email does not explain whether this means: A) You can still submit updates after 31 January 2026, as long as you complete the age rating questionnaire before submitting, or B) The app becomes locked and cannot be updated at all once the deadline passes This is no
Topic:
App Store Distribution & Marketing
SubTopic:
General
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
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
This answer is somewhat covered here: https://developer.apple.com/forums/thread/741948?answerId=811104022#811104022 The essence is that this warning refers to custom metadata saved in the HEIC images when using ObjectCaptureSession UI on iOS devices with LiDAR. There is no public way to provide this data besides using our ObjectCaptureSession capture UI which adds it automatically. If you are using another capture approach, you may safely ignore these warnings. The benefit of using the ObjectCaptureSession front-end is that we may additionally use these raw points to improve reconstruction of textureless surfaces (e.g. white walls) where depth maps may not be sufficient. To be clear, this point cloud data is distinct from the depthDataMap in the sample. This depth map may be available when reading HEIC files. It may be automatically populated (even on non-LiDAR devices) from stereo disparity data generated by AVCaptureSession in a multi-camera session, or may be derived from LiDAR data. Rega
Topic:
Spatial Computing
SubTopic:
General
Tags:
Thanks for the post, it seems like a nasty issue. We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to Developer Account I would recommend you to contact the developer account support at https://developer.apple.com/contact to make sure they are aware of the issue. Albert Pascual
Worldwide Developer Relations.
Topic:
App & System Services
SubTopic:
Apple Pay
Tags:
Hello, I sent this in as a feedback several weeks ago about watchOS 26.2 beta 2 but since the issue is still active now that watchOS 26.2 is in production I'm reposting here for the community. I would also like to submit a DTS about this issue but honestly don't know the best way to go about it and would appreciate advice about that. There seems to be an issue with VPP distribution for our app on watchOS 26.2. When our watchOS companion app is launched after being installed through VPP to a supervised iPhone, it encounters a dyld error before main() or any application code is even called. The same app launches correctly in every other circumstance we could imagine and test: – Installed through VPP on supervised devices running watchOS 26.1. – Installed from the app store (using an apple id) on a supervised iPhone and paired watch running iOS 26.2 / watchOS 26.2. – Installed through Testflight on a supervised iPhone and paired watch running iOS 26.2 / watchOS 26.2. – Installed through the app store on
Thanks such much again for your time & effort Kevin! I did look into the Documentation & tried different approaches but none seems to work. I also found a BLE sample project on the Apple Developer Documentation & it is also terminated after some time. However, unlike the Documentation states, I wasn't able to implement State Restoration and receive Characteristic updates once the App is terminated because of Memory Pressure. But I will continue to investigate into this direction. May I suggest to update the Documentation around Background Tasks to reflect the iOS Background Execution Limits https://developer.apple.com/forums/thread/685525 Neither the WWDC session nor the Documentation mention these limits. Additionally, several WWDC session like Background execution demystified & Why is my app getting killed are no longer available. Thanks a lot again
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags:
Kindly ensure that the admin of the developer account adheres to the instructions provided. The Apple Developer Program license agreement has been updated and needs to be read. To update existing applications and send new ones to the account owner, you need to read the updated agreement and accept it by logging into your account on the Apple Developer website. When the admin accepts the agreement you’ll be able to do your talks. Post like that should be go to the community forums as they cover those issues: https://discussions.apple.com/thread/255021447?sortBy=rank or talk to the developer support team. These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to Developer Account I would recommend you to contact the developer account support at https://developer.apple.com/contact to make sure they are aware of the issue. Albert Pascual
Worldwide Developer Relations.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Dear Apple Support Team, I am adding new subscriptions to my app and tried to submit them for review. However, I received the following error message: Your subscription could not be submitted for review. Please provide a privacy URL in App Privacy. I have already provided the privacy URL and changed nothing in the past.. Could you please advise how to resolve this issue so I can submit my new subscriptions for review? Thank you for your assistance. Best regards :)
Dear Apple, We have obtained the entitlement for NFC transactions for apps in the European Economic Area. With it it's possible to have a P2P NFC communication? if yes where I can found an example to have the writer part. In the documentation we have see the Device-to-Device transactions: If you have the legal right and the necessary regulatory permissions to provide device-to-device NFC solutions in the EEA, you can request access to iOS APIs to develop, test, or distribute an HCE Application for transmitting data over NFC to another mobile device. but in any place we discover documentation that explain how to do that. thanks
Topic:
App & System Services
SubTopic:
Tap to Pay on iPhone
Tags:
Hi, at first I submitted an app where you asked for a way to review everything while you mentioned a demo mode would be fine. I added a demo mode and submitted the app together with in-app purchases. Now you are asking for an actual API token for an external service which I cannot provide. I responded with the info about the demo mode. The next review was rejected because the in-app purchases are kind of lost. I cannot map them. Next re-submit was rejected because the in-app purchases are missing. The in-app purchases are stuck in a waiting status. Please do whatever you need to do to either release the in-app and let me map them again or map them yourself. Regards, Vitali
The One-time codes documentation details how to enable autofill for SMS based codes. However, there is no details about how to correctly implement autofill for email based codes. I am observing the email based autofill works inconsistently when using email based OTC. In my application: There is latency of 10-15 seconds from when the email arrives to when it is available for autofill. After the autofill feature is used, the OTC email is not being deleted from the inbox automatically. Without documentation, it's unclear to me what I might be doing wrong that is causing these side effects. I found an ietf proposal for how autofill with email based codes might work, but it’s unclear if this is how Apple has implemented the feature: https://www.ietf.org/archive/id/draft-wells-origin-bound-one-time-codes-00.html#name-email Existing docs for Autofill using SMS: https://developer.apple.com/documentation/security/enabling-autofill-for-domain-bound-sms-codes
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic:
Media Technologies
SubTopic:
Photos & Camera
Tags: