“Apple Maps Guides”

Environment Xcode 26.5 beta iOS 26.5 beta Using AccessorySetupKit + AccessoryTransportExtension framework Three extensions: AccessoryTransportAppExtension, AccessoryTransportSecurityExtension, AccessoryDataProviderExtension Background Everything worked correctly on iOS 26.4 beta. All three extensions shared the entitlement com.apple.developer.accessory-transport-extension, and the system launched them as expected. After upgrading to iOS 26.5 beta (both Xcode and device), the app compiles and runs, the accessory pairs and connects successfully (state = authorized, BLE connected, notification forwarding = allow), but none of the extensions are launched by the system. Investigation Captured system Console logs from the device and found these errors from deviceaccessd: error deviceaccessd ### Extension 'com.huami.NotificationForwardingDemo.AccessoryDataProviderExtension' is missing entitlement: com.apple.developer.accessory-data-provider for com.apple.accessory-data-provider error deviceaccessd ### Extension 'com

I purchased the Apple Developer Program on March 26, 2026. Payment went through immediately. I have the invoice (UA31019584), the order confirmation (W1318171870), and €99 charged to my card. Apple had no problem taking my money within seconds. Five days later: Account status: Pending Portal still says Purchase your membership and asks me to pay again App Store Connect: inaccessible TestFlight: inaccessible I contacted Apple Developer Support on day one — both by email and callback request. I now have three open cases and have received exactly zero responses: Case ID: 102856462218 — Program Purchase and Renewal Case ID: 102853916886 — Program Purchase and Renewal Case ID: 102853919455 — Program Enrolment Not a single acknowledgment. Not even an automated we're looking into it. Nothing. My app is built and ready. I have testers waiting. I cannot distribute anything — not even through TestFlight — because Apple took my payment and then stopped responding. I see dozens of thre

Hello Apple Developer Support / StoreKit Team, We recently observed a behavior regarding the appAccountToken in App Store Server Notifications v2 that seems to completely contradict the official documentation. According to the Set App Account Token documentation: The same appAccountToken continues to apply to renewal transactions if the customer upgrades, downgrades, or cross-grades the subscription. However, we encountered a scenario where an active in-app crossgrade resulted in an updated/overwritten appAccountToken inside the subsequent JWSRenewalInfoDecodedPayload, despite our backend never calling the Set App Account Token REST API. Our Observation: A user subscribes to our 1-month plan (Product A). Apple generates an originalTransactionId bound to their initial appAccountToken (Token A). Later, a crossgrade to a 1-year plan (Product B) is initiated from within the app while the user is logged into a different account in our system (Token B), but using the same underlying Apple

Hello, My app has been stuck in the App Store review process for approximately one month, with no progress or updates provided during this time. I have sent around 20 emails and also submitted an expedite request due to the critical nature of the issue. Unfortunately, I have not received any response to any of my inquiries. This situation has reached a critical point. Since my app is not functioning properly, I have lost all of my subscribed users, causing both financial loss and damage to my reputation. Based on my previous experience, review times are usually much shorter, so this delay appears highly unusual. I would greatly appreciate your assistance in clarifying the following: Why has my app not been reviewed yet? Why have my emails not received any response? Is there anything further I can do to expedite the review process? I kindly ask for this issue to be investigated and resolved as soon as possible. I am ready to provide any additional information if needed. App Apple ID: Apple ID

Hello, I am trying to gather information on the global availability of the Apple Find My Network. Specifically, I would like to know: Which countries currently support this feature? Is it available worldwide, with only a few specific countries/regions facing usage restrictions or complete unavailability? I have already reviewed the public Feature Availability page, but was unable to find any documentation addressing regional restrictions. Any clarification or pointers to relevant documentation would be greatly appreciated. Thank you!

Hi, My app status is currently “Ready for Distribution”, but it still hasn’t appeared on the App Store and I’m not sure what is blocking the release. In App Store Connect, I have already completed: • Agreements, Tax, and Banking (all active) • Pricing and Availability (countries selected) • Automatic release is enabled However: • My Digital Services Act (DSA) status is still “In Review” • I am also in the process of changing my account from Individual to Organization At this point, I’m not sure if the delay is caused by DSA review, account type change, or something else. Has anyone experienced a similar situation? Is there anything else I should check or complete to make sure the app goes live? Apple ID: 6760753842 Thank you.

Hello everyone, I’m looking for some clarification and advice regarding an unexpected App Review rejection under Guideline 4.1 – Copycats. My app has been live on the App Store since May 2024, and during that time, it has maintained the same core flow, structure, UI, and feature set. There have been no major redesigns or attempts to imitate any other app. Recently, I submitted a new version (v3.2) with only minor changes related to ad logic implementation (no UI/UX changes, no branding changes, no metadata changes). However, this update was rejected with the following reason: “This app or its metadata appears to be misrepresenting itself as another popular app or game…” This has left me quite confused for a few reasons: The app has been approved and publicly available for nearly 2 years There were no significant design or branding changes in this submission The rejection seems unrelated to the actual changes made in this version My questions: Has anyone experienced a situation where an app was flagged as a co

Hello Apple Developer Forums team, I would like to ask for help with my app review (App ID: 6755685130). I first submitted my app on February 14, 2026, and it has been almost 50 days. However, I still have not received clear feedback on what needs to be fixed. If there are issues with my app, I sincerely ask the review team not to provide only general guideline references. I still cannot tell which page, feature, or user flow is causing the problem. If possible, I would really appreciate screenshots, screen recordings, or a written description of the specific issue so I can make the right changes. I also want to clarify that this app is not AI-generated. It is a carefully planned app built with real effort using multiple native Swift frameworks. Thank you very much for your time and help.

We found that our apps (and other apps from different companies) cannot launch on iOS 9 to iOS 12 devices. The app can be installed successfully but crashes immediately on launch. From the device syslog: assertiond: The process failed to exec SpringBoard: Bootstrapping failed - Unable to bootstrap process Our distribution certificate was issued on Feb 2, 2026, signed by WWDR G3 intermediate certificate. This issue affects all apps under our Apple Developer account on iOS 9-12 devices. iOS 13 and above works fine.

Hi everyone, I’ve been working on an experimental prototype called FaceBridge that explores whether Secure Enclave–backed biometric authorization can be delegated between macOS and iPhone using only public Apple APIs. The goal of the project was to better understand the architectural boundaries of cross-device trust and approval flows that resemble Apple’s built-in Touch ID / Continuity authorization experiences. FaceBridge implements a local authorization pipeline where: macOS generates a signed authorization request the request is delivered to a trusted nearby iPhone over BLE / Network framework the iPhone verifies sender identity Face ID approval is requested using LocalAuthentication the iPhone signs the approval response using Secure Enclave–backed keys macOS validates the response and unlocks a protected action Security properties currently implemented: • Secure Enclave–backed signing identities per device • cryptographic device pairing and trust persistence • replay protection using n

My company only needed an Apple Developer Program account in order to sign macOS binaries. Because our scope was very limited, we enrolled with an individual account. Now our scope may grow, supporting more Apple features. As a result, we may need to change to an Organization account. If we change the account type, will this invalidate the certificate we use to sign the macOS binaries?