“Apple Maps Guides”

Hi, Our Apple Maps integration has been working normally for years, but starting today, newly created Maps tokens suddenly became unusable. Tokens created from the Apple Developer backend now return 401 Unauthorized everywhere we test them. We can reproduce this in: our own code Apple’s Try Maps Server API page MapKit JS So this does not appear to be limited to our app code. We also tested through a US network entry point to rule out a mainland China network issue, but the result was the same. At the moment, Maps tokens created in the backend seem to be unusable in all cases on our side. Has anyone else seen this today, or is there any known issue affecting Maps token creation or validation? Thanks.

I have been unable to renew my Apple Developer Program membership since March 28, 2026. The Renew button does not appear anywhere. I have submitted 3 support tickets (Case ID: 102864696639, 102861948474, 102858980607) with zero response over 12 days. My app Fiskal - Docloop has been removed from the App Store. Team ID: 2S4RNY42SZ. This is causing serious business impact. Please help.

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

Hello everyone I'm implementing age verification in my app to comply with upcoming age assurance laws (Utah, etc.), and I'm using AppStore.ageRatingCode from StoreKit to retrieve my app's current age rating. According to the documentation: extension AppStore { @available(iOS 26.2, macOS 26.2, tvOS 26.2, watchOS 26.2, *) public static var ageRatingCode: Int? { get async } } Use this property to fetch the age rating for your app and compare it with the last known age rating to check if it has changed. However, calling this always returns 0 in my environment. Environment: Device: Real physical device (not simulator) iOS version: 26.4 Sandbox Apple Account: signed in via Settings → Developer → Sandbox Apple Account App Store Connect: app is registered and age rating is configured Xcode Scheme → Run → Options → StoreKit Configuration: None Code: func getAgeRatingCode() async -> Int? { guard let ageRatingCode = await AppStore.ageRatingCode else { print(Age rating code unavailable) return nil }

I’m submitting an iOS app that uses Family Controls / DeviceActivity APIs, and App Store Connect rejects the archive during distribution with this error: Invalid Info.plist value. The value of the NSExtensionPointIdentifier key, com.apple.deviceactivity.monitor, in the Info.plist of “activity-tracking.app/PlugIns/ScheduleMonitorExtension.appex” is invalid. What I’ve already verified: Family Controls capability is approved for our team App IDs and distribution provisioning profiles were regenerated The source Info.plist for the extension contains: NSExtensionPointIdentifier = com.apple.deviceactivity.monitor The archived .appex inside the .xcarchive also contains the same exact value Signed entitlements in the archived .appex include: com.apple.developer.family-controls = true app group entitlement Main app archive is signed correctly as well Latest stable Xcode used This makes it look like the archive is configured correctly, but App Store Connect still rejects the Device Activity Monitor extension point itse

I did my apple enrolment on April 3rd and I don not have any response yet. What are the next steps

Hi everyone, I am currently working on automating the renewal process for our managed certificates using the App Store Connect API. However, I've encountered an issue where certificates of the Apple Push Service type cannot be retrieved or created. After reviewing the documentation on CertificateType, it seems there is no corresponding type for Push Service certificates. https://developer.apple.com/documentation/appstoreconnectapi/certificatetype Is there any other way or a workaround to obtain or manage these certificates programmatically? Any advice would be greatly appreciated.

Hello, I’m trying to better understand the implementation flow for Tap to Pay on iPhone. In a partner onboarding portal (Partner Hub), the process is presented in the following stages: • Registration • Prerequisites • Operations & Setup • Certification • Launch However, it’s not clear what actually changes after completing the “Prerequisites” stage. Questions: After completing “Prerequisites”, are there any changes in terms of entitlements or capabilities provided by Apple? Is access to Tap to Pay functionality enabled at this point, or does it depend on steps outside of Apple’s developer environment? At what stage is the production entitlement typically granted? Is there any Apple-specific action required between “Prerequisites” and “Operations & Setup”? I would appreciate any clarification on how this transition works from Apple’s perspective. Thank you.

Hello Apple Developer Support Team, I hope you are doing well. I am writing to request assistance regarding the activation of my Apple Developer Program membership. I have already completed the purchase of the Individual Developer Program (USD 99), but my account has not yet been activated. It has been longer than the usual processing time, and my Membership status still does not show as active. Thank you very much for your time and support. I appreciate your help.

My name is Paul Merriman. I am the founder of the Merriman Financial Education Foundation, a 501(c)(3) nonprofit dedicated to providing free financial education. Our iOS app was initially submitted under our technology manager's personal developer account, which was correctly flagged as an issue. We have since enrolled the Foundation as an organization using our verified D-U-N-S number and submitted all required documentation confirming our nonprofit status. We are experiencing two related issues: 1. Enrollment Stuck Processing Our Foundation enrollment has been in processing status for several weeks. Our enrollment ID is 7YAJUR73GH. We have not received any updates or communication from Apple about what is needed to complete enrollment. 2. App Store Connect Access Because enrollment is not complete, we cannot log in to App Store Connect using the Foundation's Apple ID. We receive this error: To access App Store Connect, you must be an individual or team member in the Apple Develope