Overview

I had published an App which App Clip is supported. I have receipt complaints from user where the user will keep showing the "Apple Media Services Terms and Conditions Have Changed" right after user click on the "Open" button in the App Clips. What I had tried: Let user switch the current logged in Apple Id region to one of our support region. Log out and log in with an Apple Id which had no issue.

Hi all, I am experiencing an error when attempting to pay for apple developer program "Your payment authorisation failed on card •••XXXX. Please verify your information and try again, or try another payment method." I have tried multiple payment methods and even another bank, Apple wont let me pay with apple pay in my region (AUS). Any suggestions?

I've paid the amount and the amounts deducted from my account , and its been 5 days , but still my developer account is not verified , how to deal with this .

Our app supports UIScene. As a result, launchOptions in application(_:didFinishLaunchingWithOptions:) is always nil. However, the documentation mentions that UIApplication.LaunchOptionsKey.location should be present when the app is launched due to a location event. Given that our app is scene-based: How can we reliably determine whether the app was launched due to a location update, geofence, or significant location change? Is there a recommended pattern or API to detect this scenario in a Scene-based app lifecycle? This information is critical for us to correctly initialize location-related logic on launch. Relevant documentation: https://developer.apple.com/documentation/corelocation/cllocationmanager/startmonitoringsignificantlocationchanges()

Hello there. My enrollment process with ID N2XM45Y7RA is stuck, even if all requirements are fulfilled. Nothing... a month guys? What can I do - or who do I contact.??????

Understand other technologies or app doing mirroring will have 2 screens active at the same time. But for Apple iPhone Mirroring is showing only 1 screen at a time and with other protection of same Apple ID, Bluetooth and Wifi for proximity checks. Hence, it is really considered a iPhone Mirroring? https://support.apple.com/en-sg/120421

Hi all, We can’t install our app from TestFlight. The app is visible in TestFlight for invited internal testers, but tapping Install fails immediately with: “The requested app is not available or doesn’t exist.” --Setup-- Distribution: TestFlight – Internal Testing Internal group created and testers added (invite accepted) Build processing status in App Store Connect: Complete TestFlight build status shows: Ready to Submit / Prepare for Submission Minimum iOS deployment target: iOS 15.0 Version/Build: 1.0.0 (1) What we tried Confirmed tester is signed into TestFlight with the same Apple ID email that was invited Removed/added testers to the internal group and resent invites Reinstalled TestFlight, signed out/in Verified build is assigned to the internal group Set and saved Monetization → Pricing and Availability → App Availability (All Countries/Regions) Question Has anyone resolved this issue? Is there a known TestFlight/App Store Connect stuck state that causes this error even for internal testing? Any recommended steps (new build number, group reset, availability/pricing settings, etc.)? Screenshots available (TestFlight error + App Store Connect build/group view). Thanks.

Dear Apple Developer Program Legal/Compliance Team, I am writing in response to the termination notice regarding my Apple Developer Program account, in which Apple cites an alleged violation of Section 3.2(f) of the Apple Developer Program License Agreement (ADP Agreement), based on “documented indications of fraudulent conduct.” I respectfully request formal clarification and detailed information regarding this determination, as I take compliance obligations under Apple’s agreements very seriously. Specifically, I kindly request the following: Clarification of Alleged Conduct Please specify the exact actions, behaviors, or activities that Apple has determined to constitute a violation of Section 3.2(f), including the category of conduct involved (e.g., technical interference, platform misuse, fraudulent activity, distribution abuse, business practice violations, or other). Scope and Nature of the Evidence Without requesting disclosure of sensitive internal systems, I respectfully ask for clarification regarding the general nature of the evidence relied upon (e.g., transactional records, system logs, behavioral patterns, policy violations, or platform integrity signals). Account-Level vs. Application-Level Issues Please confirm whether the alleged violation relates to: A specific application or applications, Account-level activity, Distribution mechanisms (TestFlight, Custom App Distribution, Ad Hoc, etc.), Or external operational behavior associated with the developer account. Opportunity for Rectification or Compliance Remediation Kindly advise whether Apple provides any compliance remediation pathway, corrective action mechanism, or review process for cases involving Section 3.2(f), including: Formal reconsideration or appeal procedures, Regulatory complaint mechanisms, Compliance audit or corrective action submissions, Reinstatement eligibility criteria. Reapplication and Cooling-Off Period Requirements Please clarify the conditions, requirements, and compliance expectations associated with the stated reapplication restriction period, including whether specific remediation steps, certifications, or compliance documentation may be required prior to any future eligibility review. My intent is to fully understand the nature of the determination, ensure full legal and contractual compliance, and clarify whether any formal resolution or review mechanisms exist under Apple’s policies or applicable platform regulations. I respectfully request that this inquiry be handled through the appropriate legal or compliance review channel. Thank you for your time and consideration. Sincerely, Jiuru Song [Team ID / Developer ID if available]8DJDU79WZ7 [Company Name, if applicable]ASIA DIGITAL ALLIANCE PTE. LTD.

Hello Apple Developer Technical Support / Core Location Team, I’m requesting clarification on the effective timing of the Info.plist key NSLocationDefaultAccuracyReduced. We shipped Version A with NSLocationDefaultAccuracyReduced = YES (reduced accuracy by default). In Version B we changed it to NO. After updating to Version B, on devices/users that have not previously granted location authorization for our app, the first authorization flow still behaves as if reduced accuracy is the default (i.e., the same behavior as Version A). Could you please confirm: When iOS evaluates/caches NSLocationDefaultAccuracyReduced (install time, app launch, or at first authorization prompt)? After an update changes this key from YES to NO, should the new value apply to users who have never authorized location for the app? Environment: Iphone 16 (IOS 26.0) I can provide a sysdiagnose and additional logs if needed. Thank you, Jack

Hi everyone, I’m seeking advice on an enrollment loop I’ve been stuck in for my Apple Developer Program account. I am based in Uruguay, and I’ve encountered a series of technical hurdles that Apple Support emails haven't been able to resolve. The Issue: Web Portal: When I log in to the portal, I see the message: "Your enrollment in the Apple Developer Program is under review. Please contact us." Apple Developer App: Support suggested using the app to finish enrollment, but the "Enroll Now" button is grayed out/disabled. It explicitly tells me to continue enrollment via the website, creating a circular dependency. Payment Failure: During my initial attempt, I noticed I was never asked for my card's CVV. Consequently, no charge was ever made to my bank, but the system seems to think a transaction is pending or "Under Review." The Barrier: As a user in Uruguay, I do not have a direct "Phone" option for support in my region—only email. The email responses I receive are automated or generic, telling me to either use the app (which is disabled) or call them (which isn't an option for my country). Has anyone from faced this "Under Review" stalemate? Is there a specific way to force the payment details to refresh or a known workaround for the disabled button in the app? Any help would be greatly appreciated.

Current issue (happening now) I get blocked immediately after entering my identity details and address. Apple Developer app (iPhone) I start the enrollment flow. After identity verification, I enter my address (Street Address, City/Town, State/Province, Postal/Zip, Phone). As soon as I tap Continue, I get: Contact Us to Continue There may be an issue with your account that needs to be resolved before you can continue. Please contact support. I cannot proceed past this point. Web enrollment (developer.apple.com) When I try on the web, I get: Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. This happens right after providing identity + address (before I can proceed further). Previous timeline (related background) ~3 months ago I incorporated my company in Türkiye (Ltd. Şti.) and tried to enroll as an organization. What happened First attempt on the web: enrollment was approved, but I couldn’t complete payment. Support told me to reset and try via the Developer app. Developer app enrollment then requested identity + “association with the enrolling entity” and company documents: Government-issued photo ID Employment/association verification Commercial registry extract (signed/stamped) Articles of association Tax office + tax number document Signatory circular I uploaded the requested documents. Apple replied that Turkish documents were unsupported and asked for “solicitor-certified English translations.” I uploaded English translations that were sworn-translator stamped. Why the translations were not notarized In Türkiye, due to the current economic situation, notarizing multiple translated corporate documents can cost hundreds of USD. Because of that, I initially provided sworn-translator certified (stamped) English translations rather than notarized translations. The translation office I worked with told me they regularly prepare company document translations for Apple Developer Program enrollments and that translator-certified translations are usually sufficient. My plan was to get everything notarized immediately if Apple explicitly requested notarization again or clarified that notarization was mandatory. About a week later, I received: Your enrollment request for your company has been declined. I followed up multiple times asking what exact requirement was not met (translation certification type, identity/association verification, etc.). Phone support said the decision was final and they could not disclose the reason. Additional detail discovered after the decline (document error fixed) After the decline, I reviewed all documents line-by-line and found a serious issue in my signatory circular: My company was incorporated on 27.08.2025. The signatory circular incorrectly stated that my authority started on 27.08.2023 (two years earlier). This was a notary/document preparation error. I immediately returned to the notary and had it corrected. They acknowledged the mistake, and I can obtain an official written statement confirming the correction if needed. However, Apple has not provided a channel to submit corrected documents, and support is not giving a path forward. What I’m asking the community Has anyone seen the “Contact Us to Continue” message triggered at the identity/address step and successfully fixed it? If yes, what specifically solved it? Is this typically an Apple Account eligibility/restriction flag, or can it be caused by address/region verification format issues? After an organization enrollment is declined, is there a known path to re-apply successfully (e.g., notarized translations vs translator-stamped, or having a different authorized representative apply as the Account Holder)? If documents were corrected after the decline (like the notary error above), is there any supported way to resubmit without starting from zero? Any concrete guidance would help. Thank you.

iPhone 13 mini running iOS 26.2 I went to mirror a stream to a previously used Roku device. The Roku popped right up on the Screen Mirror list, but would not respond. Investigation showed it had lost its network connection - so what showed on the Screen Mirror list was still in cache, not from a current request - and sure enough, after repairing the Roku's LAN connection, it worked fine. That raised these questions: Does the iOS device (iPhone) cache a Screen Mirror list for each network? How does the iOS device build its list of Screen Mirror servers on a local network? I presume it broadcasts a request to the LAN, the first time it is invoked on a new LAN, asking "Does anyone provide this service?" - Is that correct? [Is that broadcast a Bonjour function?] If not, how does it acquire its list of Screen Mirror servers? To avoid the problem of false positives in the Screen Mirror list, how can I clear that cache (#1) and issue a new request (#2) for current Screen Mirror servers? How can iOS avoid showing servers that no longer exist on the network? Is there any limit to the number of networks cached by iOS, or the number of servers cached per network? More generally, is there a good resource to read how iOS manages this issue?

Environment macOS 15.7.3 Xcode 26.1.1 / 26.2 iOS 18.5 / 26.2 iPhone 16 Pro Simulator and physical device Problem Description When tapping an unselected UISegmentedControl, the selected segment does not match the tapped position. Specifically, tapping the rightmost segment (index: 3) results in the leftmost segment (index: 0) being selected instead. Conditions for Reproduction This issue occurs when all of the following conditions are met: Built with Xcode 26.x UIDesignRequiresCompatibility is set to YES in Info.plist UISegmentedControl is positioned using Auto Layout with leading alignment Segments are added dynamically using insertSegment(withTitle:at:animated:) Note: The issue does not occur when segments are defined statically in Storyboard. Steps to Reproduce Create a subclass of UISegmentedControl that dynamically sets segments: class CustomSegmentedControl: UISegmentedControl { func setSegments(titles: [String]) { removeAllSegments() titles.forEach { title in insertSegment(withTitle: title, at: numberOfSegments, animated: false) } } } In the ViewController, configure the control: override func viewDidLoad() { super.viewDidLoad() segmentedControl.setSegments(titles: ["Item A", "Item B", "Item C", "Item D"]) segmentedControl.selectedSegmentIndex = UISegmentedControl.noSegment } Set UIDesignRequiresCompatibility to YES in Info.plist: <key>UIDesignRequiresCompatibility</key> <true/> Run the app and tap the rightmost segment ("Item D") Expected vs Actual Behavior Expected Actual Tap rightmost segment "Item D" (index: 3) is selected "Item A" (index: 0) is selected What I Tried (Did Not Work) Calling layoutIfNeeded() after adding segments: segmentedControl.setSegments(titles: ["Item A", "Item B", "Item C", "Item D"]) segmentedControl.layoutIfNeeded() // No effect Workarounds Set UIDesignRequiresCompatibility to NO (enables Liquid Glass design) Define segments statically in Storyboard instead of dynamically Sample Project Minimal reproduction project is available here: https://github.com/CH3COOH/Samples/tree/master/SampleSelectSegmentedControl Feedback Assistant This issue has been reported via Feedback Assistant: FB21712773 Has anyone else encountered this issue or found alternative workarounds?

So I've been bugging Apple (and anyone who will listen) for years, about the hassles that come with having one ID for iCloud+ (primary) and one ID for purchases (secondary). I forget why the split, but there was a reason, that's long since gone. Since discovering last year that finally, Apple have provided a way to transfer purchases from secondary to primary, I have lost so... much... time... trying to make this work. Following checklists many times... upgrading, downgrading, removing profiles... deregistering from TestFlight etc etc. After escalating within Apple support, the "solution" came back as "It's because you're a developer - you can't." Now, I've been around the block in 'puters enough times to know that, that "solution" is - even if correct, the "cause". A solution, it ain't. But in any case, surely Apple wouldn't do that to "us", right? Everyone else affected by the two-account hassles is now cured... but for those of us who live on our Macs and iPhones making software for Apple and its communities, it's "screw you guys". I'll try and climb off my high horse now... but man, frustrated is not even close, not helped by another 3 hours on the phone today, getting cut off twice and having to repeat myself again and again. I've even suggested de-registering as a dev, transferring assets etc... but one person even told me (albeit as if he was clutching at straws) that once a dev, that's it - no way back, and some options like transfer are gone forever! Has anyone here - as a developer - managed to transfer their purchases from one ID to another? Does anyone know any more about this? Can anyone put me out of my misery - or offer some calming advice before I totally lose my sh...share of sanity.

Hello, I am using the App Store Connect Finance Reports API to export monthly financial statements. API endpoint: https://api.appstoreconnect.apple.com/v1/financeReports Request parameters: reportDate: 2026-01 reportType: FINANCE_DETAIL However, the returned report shows an unexpected date range: Start Date: 09/29/2025 End Date: 11/01/2025 This does not match the requested month January 2026, and instead seems to cover a different settlement period. I would like to confirm: Is the Finance Reports API returning data based on Apple’s settlement cycle rather than the requested calendar month? How should we correctly map reportDate to the actual statement period? Is there a recommended way to reliably retrieve the financial report for a specific month (e.g. Jan 2026)? This behavior makes automated reconciliation difficult, so any clarification or guidance would be appreciated. Thank you very much for your help.

Hello, My app has been approved on the App Store, but the in-app purchases are still under review. This is the first time I'm publishing an app with in-app purchases. During sandbox testing, everything worked correctly. Is it normal for there to be a validation delay for in-app purchases after the app approval? Or is there a specific action I need to take, given that this is my first experience with in-app purchases? Thank you in advance.

I have a user (myself, during development) who originally signed in with Apple successfully. I attempted to revoke access via Settings > Apple ID > Sign-In & Security > Sign in with Apple, but the app appears stuck in the list and cannot be fully removed. Now when attempting to sign in again, the identity token contains the correct sub but email is undefined. According to Apple's documentation, "Apple provides the user's email address in the identity token on all subsequent API responses." I've tried programmatically revoking via the /auth/revoke endpoint (received 200 OK), and I've implemented the server-to-server notification endpoint to handle consent-revoked events, but subsequent sign-in attempts still return no email. The same Apple ID works fine with other apps. Is there a way to fully reset the credential state for a specific app, or is this a known issue with partially-revoked authorizations?

Hi everyone, We’re experiencing an issue with App Store Connect → Sales & Trends (Sales) → Last 24 Hours (hourly) reporting, specifically for In-App Purchase (IAP) sales. On January 30–31, 2026, when checking Last 24 Hours sales data, we consistently see IAP sales drop to 0 starting around 18:00 UTC, as if no purchases happened after that time. However, we can confirm that IAP transactions did occur during the same time window using other validation sources (e.g., server-side logs / analytics). In App Store Connect, those hours still show 0. I did a quick search and found reports of similar behavior affecting downloads/units for some teams, but in our case downloads/units look normal in Last 24 Hours. The problem appears to be only in the IAP sales portion. Questions: Is anyone else seeing hourly gaps / 0 values for IAP around Jan 30–31, 2026 (or today)? Is this a known Sales & Trends reporting delay that eventually backfills, or an ongoing issue? If you’ve seen this before, how long did it take to normalize/backfill, and did any specific check/filter help?

Hi, You're here because you've had issues with your implementation of In-App Provisioning Extensions for Apple Pay In-App Provisioning or In-App Verification. To prevent sending sensitive credentials in plain text, create a new report in Feedback Assistant to share the details requested below with the appropriate log profiles installed. Gathering Required Information for Troubleshooting Apple Pay In-App Provisioning or In-App Verification Issues While troubleshooting Apple Pay In-App Provisioning or In-App Verification, it is essential that the issuer is able to collect logs on their device and check those logs for error message. This is also essential when reporting issues to Apple. To gather the required data for your own debugging as well as reporting issues, please perform the following steps on the test device: Install the Apple Pay and Wallet profiles on your iOS or watchOS device. If the issue occurs on Mac, continue to Step 2. Reproduce the issue and make a note of the timestamp when the issue occurred, while optionally capturing screenshots or video. Gather a sysdiagnose on the same iOS or watchOS device, or on macOS. Create a Feedback Assistant report with the following information: The bundle IDs App bundle ID Non-UI app extension bundle ID (if applicable) UI app extension bundle ID (if applicable) The serial number of the device. For iOS and watchOS: Open Settings > General > About > Serial Number (tap and hold to copy). For macOS: Open the Apple () menu > About This Mac > Serial Number. The SEID (Secure Element Identifier) of the device, represented as a HEX encoded string. For iOS and watchOS: Open Settings > General > About > SEID (tap and hold to copy). For macOS: Open the Apple () menu > About This Mac > System Report > NVMExpress > Serial Number. The sysdiagnose gathered after reproducing the issue. The timestamp (including timezone) of when the issue was reproduced. The type of provisioning failure (e.g., error at Terms & Conditions, error when adding a card, etc.) The issuer/network/country of the provisioned card (e.g., Mastercard – US) Last 4 digits of the FPAN Last 4 digits of the DPAN (if available) Was this test initiated from the Issuer App? (e.g., yes or no) The type of environment (e.g., sandbox or production) Screenshots or videos of errors and unexpected behaviors (optional). Important: From the logs gathered above, you should be able to determine the cause of the failure from PassbookUIService, PassKit or PassKitCore, and by filtering for your SEID or bundle ID of your app or app extensions in the Console app. Submitting your feedback Before you submit to Feedback Assistant, please confirm the requested information above is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Apple Pay client. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your client, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer

In WKWebView, there is the WKUIDelegate method: func webView(_ webView: WKWebView, createWebViewWith configuration: WKWebViewConfiguration, for navigationAction: WKNavigationAction, windowFeatures: WKWindowFeatures) -> WKWebView? {} This delegate method provides a callback when a new window (for example, target="_blank") is requested in the web view. However, in native SwiftUI (iOS 26), WebView / WebPage APIs do not provide an equivalent delegate method to handle new window requests. As a workaround, I am using the following method: public func decidePolicy(for action: WebPage.NavigationAction, preferences: inout WebPage.NavigationPreferences) async -> WKNavigationActionPolicy {} In this method, when action.target == nil, I treat it as a new window request. My question: Is relying on action.target == nil in decidePolicy a reliable and future-safe way to detect new window requests in SwiftUI’s WebView, or is there a better or more recommended approach for handling target="_blank" / new window navigation in the SwiftUI WebView APIs? Code: public func decidePolicy(for action: WebPage.NavigationAction, preferences: inout WebPage.NavigationPreferences) async -> WKNavigationActionPolicy { guard let webPage = webPage else { return .cancel } // Handle case where target frame is nil (e.g., target="_blank" or window.open) // This indicates a new window request if action.target == nil { print("Target frame is nil - new window requested") // WORKAROUND: Until iOS 26 WebPage UI protocol is available, we handle new windows here // Try to create a new WebPage through UI plugins if handleCreateWebPage(for: webPage, navigationAction: action) != nil { // Note: The new WebPage has been created and published to the view return .allow } } return .allow }