I would like to inquire about an error that has started occurring while debugging AppStore billing. (In sandbox environment) This error occurs after entering a password and completing the purchase process, and in this case, no completion alert appears. The error doesn't seem to depend on the purchase item, sandbox account, or device, and shows unstable behavior - sometimes succeeding and sometimes failing. Additionally, this error started occurring after special debugging where the network was disconnected during the purchase process. Moreover, the same error occurs in the TestFlight version of our already released normal (supposedly) version. I think this might be a sandbox-specific error where the system has temporarily become unstable, but what do you think? If so, how can I resolve this issue? I would appreciate your insights on the cause and appropriate response. Error details below: <SKPaymentQueue: 0x283b3d070>: Payment completed with error: Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={NSUnderlyingError=0x28364d770 {Error Domain=AMSErrorDomain Code=305 "Purchase Failed" UserInfo={NSLocalizedDescription=Purchase Failed, AMSStatusCode=200, AMSServerPayload={ "cancel-purchase-batch" = 1; customerMessage = "Unauthorized_message"; failureType = ""; "m-allowed" = 0; pings = ( ); }, NSLocalizedFailureReason=Server canceled the purchase}}, storefront-country-code=JPN, client-environment-type=Sandbox}

Whether using Storefront.current?.countryCode or SKPaymentQueue.default().storefront?.countryCode, both are returning "USA" only. (It used to return the correct country code before the update.) In the sandbox environment, the country code is returned correctly, but in the TestFlight environment, it always returns "USA". There's no mention of this behavior in the beta release notes, so I'm posting it here for visibility.

Problem Description: My iOS app's In-App Purchase shows "Product not found" error even though the IAP is approved in App Store Connect. The app returns 0 available products when trying to fetch them. But there are no errors in Simulator. Technical Details: App: iOS SwiftUI app using StoreKit 2 Error: Product not found. Available products count: 0 What Works: App compiles and runs without errors StoreKit 2 implementation follows Apple's guidelines Product fetching code is correct (Product.products(for:)) IAP is approved in App Store Connect Bundle ID matches between Xcode and App Store Connect No errors shown in App Store Connect interface What Doesn't Work: Product.products(for:) returns empty array App cannot find the approved IAP product Purchase flow cannot proceed due to missing product App Store listing doesn't show "Offers In-App Purchases" badge What I've Tried: Implemented product caching and robust error handling Added comprehensive debug logging Verified bundle ID and product ID match exactly Uploaded multiple app versions (3+ rounds) Waited for App Store approval each time Tested on multiple devices and accounts Checked App Store Connect for any configuration issues Status Quo: The IAP is approved in App Store Connect but Apple's servers are not returning the product to the app. This appears to be a StoreKit backend configuration issue rather than a code problem. Again I'm getting no errors in Simulator Has anyone experienced this specific issue where an approved IAP returns 0 products? What was the solution? P.S. One thing that I added: when the user buys the App they get a pre written script as a thank you. Which Is part of the “product”. P.P.S https://github.com/Fle4k/Dialog https://apps.apple.com/app/dialog-pro/id6746421328

We are experiencing a significant issue with the SKStoreReviewController.requestReview(in: scene) API that may be affecting our app's rating collection on the App Store. Issue Details: Development Environment Behavior: The rating popup displays consistently in development builds (as expected per documentation) API calls are functioning correctly in our test environment Production Environment Issue: We have observed a major drop in App Store ratings received between January and July 2025 The same codebase that works in development is deployed to production Analytics Confirmation: Before calling SKStoreReviewController.requestReview() in production, we fire analytics tags to track API invocations Our analytics show no drop in the number of times this API is being called This confirms the API is being invoked correctly in production Discrepancy: Despite consistent API calls (confirmed by analytics), we see a major drop in actual ratings received on the App Store This suggests the rating popup may not be displaying to users in production, even though the API call is successful Questions: Are there any known issues with SKStoreReviewController.requestReview() API between January-July 2025? Are there any iOS version-specific issues that might prevent the popup from appearing in live app? What debugging steps do you recommend to identify why the API calls aren't resulting in visible rating prompts?

Hi. I have chosen a name for my new app, which isn't available in "English U.S.". When uploading it to TestFlight using Xcode, I get. The app name you entered is already being used. If you have trademark rights to this name and would like it released for your use, submit a claim. I changed the primary (and only) language from "English U.S." to "English U.K." and the app name is now accepted by App Store Connect. The app is supposed to be worldwide available and doesn't target any specific geographical region. It's also only available in English (no localizations). Are there any disadvantages using "English U.K." i.s.o. "English U.S."? What are the differences between both when it comes to App Store presentation, ranking, search, ... I don't really see why Apple offers 4 English languages. Every style understands the other one, despite some minor spelling differences.

Hi, I recently received a Pending Termination Notice from the Apple Developer Program, citing evidence of dishonest or fraudulent activity and a violation of Section 3.2(f) of the Apple Developer Program License Agreement. I believe this action may have been triggered by a mistaken device or network association with my brother’s developer account, which was previously terminated. While we did use the same MacBook and iPhone/iPad for testing in the past, we are completely separate indie developers with different Apple IDs, apps, and publishing histories. All of my apps are 100% original, built over the past 5 years with significant time and effort. I’ve already prepared a full appeal that includes: Proof of identity confirming we are two different individuals A detailed explanation of the historic device overlap A strong commitment to compliance, including use of dedicated devices, accounts, and networks moving forward Before I submit, I’m hoping to ask: Is there any way to ensure my appeal will be reviewed by a human and not auto-dismissed? Has anyone experienced a similar issue and successfully resolved it? Is there a direct way to reach Developer Relations or App Review for edge cases like this? I’m fully committed to adhering to Apple’s guidelines and would greatly appreciate any opportunity to resolve this misunderstanding. Thank you for your time and any help

I got a “DPLA violation” email. About an hour later my app disappeared from Top Charts in multiple countries. The app is still live, searchable, and on the product page it still says “Chart No.2 – Education.” I only posted it on Reddit and made lifetime free to get feedback from the community. Here's the email: "Notification of Apple Developer Program License Agreement (“DPLA”) violation: Hello xx, We're writing to inform you that your company isn't in compliance with the Apple Developer Program License Agreement (DPLA). Section 11.2 (Termination) states: (g) if You engage, or encourage others to engage, in any misleading, fraudulent, improper, unlawful or dishonest act relating to this Agreement, including, but not limited to, misrepresenting the nature of Your Application (e.g., hiding or trying to hide functionality from Apple’s review, falsifying consumer reviews for Your Application, engaging in payment fraud, etc.). Be aware that manipulating App Store chart rankings, user reviews or search index may result in the loss of your developer program membership." The weird part: • The product page still shows ranks like “Chart No.2 – Education” (Hong Kong, and similar positions in a few other countries). • Search still finds the app normally. • But in the actual Top Charts lists the app is gone. Territories affected (so far): Hong Kong, Taiwan, Macao, South Korea, Singapore, Malaysia, Portugal and a few more. I did not buy installs, did not pay for reviews, did not gate features behind ratings. After the email I double checked and removed any copy that could be read as an incentive for reviews, just in case. I have already emailed Support (Search & Discoverability and App Review). I am waiting, but thought I should ask here too. My questions 1. Has anyone else seen their app silently removed from charts right after a DPLA warning? 2. Did it come back on its own? How long did it take? 3. Is there anything specific I should fix besides waiting and cleaning wording? 4. Is there an official appeal path for chart suppression, not full removal? Reddit posts for context: • https://www.reddit.com/r/iosapps/comments/1m4klxs/giving_away_lifetime_free_for_limited_time_i/ • https://www.reddit.com/r/SideProject/comments/1m5d7gh/im_giving_away_free_lifetime_access_for_my/ Thanks in advance for any guidance or shared experience.

I've got an app that uses WebRTC. When I try to upload it using Xcode I get the following error: Validation failed The app references non-public selectors in Payload/{MyApp}.app/{MyApp}: initWithURLStrings: (ID: 61a6dbe5-dac2-4910-a836-b4b9b2e891b4) This API is not private, it's just unfortunate that WebRTC chose to use this name as well, and it is falsely identified as a private API by Apple. Has anyone seen this? The funny thing is, I have the exact same app with different configuration in TestFlight internal only for staging, and I could upload it without any issues. And yes, I've tried uploading this app for test flight internal only. No success either.

I have been trying for almost a week to get my app approved. It is like the Submission team doesn't even read my notes. The first complaint is that my app was for a specific business and shouldn't be for the general public. This is true, so I put in the notes that I had requested private distribution and I filled out the request for the app to be distributed privately. The review notes say that I need to distribute my app privately. This is very frustrating. Also, they say the login button doesn't work. It works for everyone that uses it in the Test Flight. One nuance we have is that our servers will not respond to IP addresses that orginate outside of the US. I have this in caps in the notes. They still say that the Login button doesn't work. The app was written for iPhones, yet they keep testing it on an iPad. There doesn't seem to be any way to communicate with the submission team other than through the test notes and they don't seem to be reading these. Can anyone direct me to where I can get some help on this? Thanks, Jim

My app keep getting rejected after changing complete UI. It's an finance tool app. any advice Guideline 4.3(a) - Design - Spam We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality. Resources Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third party Submitting several similar apps across multiple accounts

Hello everyone, I build and run the app in iPhone in developer mode but now i am trying to install and run the app in another iPhone in which i did not turned on the developer mode. it installed but not opening without the Developer mode. Is there any another way to install and run the app with Developer mode for one time. If not then tell me the process how i can do publishing in testFlight or appStore. Thanks

Hello, I’m an iOS developer and the original creator of the app "Instant Save: Reels story" (App Apple ID: 6469411763). On July 5, 2025, I received two Apple emails saying the app was transferred to another developer account. However, I did not initiate or approve this transfer. My Apple Developer account has Two-Factor Authentication enabled, and I received no OTP or request for approval. I submitted a legal dispute form via Apple’s Intellectual Property page on July 7, 2025, but I’ve only received an automated acknowledgment — no dispute number or follow-up. I’ve also contacted Apple Developer Support multiple times by phone, but they confirmed they cannot escalate legal cases or access my dispute status. Has anyone else faced this issue recently? I’m looking for any guidance or similar experiences while I await a response from Apple Legal. Thanks in advance,
 Bhautik Amipara

Hello Apple Developer Support & Community, I’m reaching out regarding the unexpected termination of my Apple Developer Program account, associated with App ID: 6744330283. Recently, my app was flagged under Guideline 4.3 - Spam, and I was asked to make necessary changes. I followed all guidance provided by Apple, including a phone call with an App Review team member, who clarified the steps I should take. I did not submit any further update after that call. However, before I had the chance to upload the new, compliant version of my app, my entire developer account was terminated without a clear explanation or additional warning. I believe this was a misunderstanding, as I was actively working on compliance and fully committed to resolving the issue. My app is not spam I only followed Apple’s instructions I never uploaded a new version after my call with App Review No specific violation or example of “spam” was shown to me I’ve submitted an official appeal via the App Review Board, but I’m hoping someone here can also assist or escalate this matter. My developer account and years of effort are at risk over what seems to be a miscommunication. Thank you for any guidance or assistance you can provide.

My app published 6 hours ago this is first version and IAP is still in review. My app is hard paywall app so people cannot continue in app and this is all happening during initial boost. I contacted with apple but they say they send message to review time and hours passed nothing changed. People downloading the app and I'm watching it without able to do anything :( Are there anyone experienced same thing ? Do you have any advice ?

Hello, Since updating to iOS 26 Beta 3, I’ve been experiencing an issue where transactions purchased through the normal in-app purchase flow continue to be reported as updated and unfinished—even after calling the finish() function. Please resolve this promptly.

Hi all, I submitted a healthcare-related iOS app on June 19 that integrates with a health monitoring device. It had a few prior rejections due to compliance concerns, which we addressed. Apple Developer Support confirmed the review is still in progress and that it requires additional time. I'm wondering if others have experienced similarly extended review timelines for healthcare or medical device-integrated apps, and how long it took for resolution. Would appreciate any advice or shared experiences on this. Thanks!

After posting a new version of our app, we used to have 80% of our userbase on the new version pretty quickly (usually 72 hours, sometimes less). Over the past few weeks, we've noticed that the App Store has throttled down app updates, and it now takes much longer for a new version of our app to reach 80% (approximately 15 days, so 5 times slower). He is an update graph before: And a similar update graph after: We've published several versions over the past couple of weeks, and we've seen the same slow update behavior for all of them. What could explain these differences ? At the time of this writing, the update graph has very slowly reached 80% and is now flat. In the past it would easily reach 90% (the last 10% were always slow to get).

Our app (app1) was recently transferred from Team A to Team B. While reviewing the Apple login implementation, we discovered that "Sign in with Apple" had been incorrectly set up to use the Service ID and App ID of another app (app2) — specifically, it was using app2.service as the Service ID and app2 as the App ID. In other words, app1’s users were authenticated through app2’s credentials due to a misconfiguration on our part. Now that app1 has been transferred to Team B, we’re trying to preserve those users. However, app2 is still in Team A, and we cannot maintain Team A anymore — meaning app2 must also be transferred to Team B if we want to retain access to the user data. One idea we considered is submitting app2 for App Review (even though it's non-functional) just to fulfill the transfer requirements, and then transferring it to Team B solely to retain the Apple login setup. Is this approach acceptable? Are there any recommended ways to handle this kind of misconfiguration while preserving existing Sign in with Apple users?

Hi, Our recent security scans, performed by Data Theorem, have flagged a potential App Store blocker related to the use of a private iOS class, NSBlock. We are concerned that this identified warning may lead to our apps being rejected during the next App Store submission. Issue Summary: We integrate a library, this SDK is developed using Kotlin Multiplatform, and during compilation, Kotlin automatically generates Objective-C/Swift interoperability code. As a result of this code generation, the compiled framework includes a reference to a private Apple class, NSBlock. It’s important to note that: No methods or functionality from NSBlock are being invoked or used. This reference is auto-generated by Kotlin’s ObjCExport.mm module. For additional context, you may refer to a related discussion on this issue: https://github.com/ricohapi/theta-client/issues/98 https://github.com/JetBrains/kotlin-native/issues/1642 https://github.com/JetBrains/kotlin-native/pull/1652/files We would like to confirm whether the presence of this unused reference to NSBlock will result in the rejection of our application during App Store review. Thankyou

Hello Apple Developer Team and Community, I’m writing to raise a serious concern regarding my app (App ID: 6744330283) which is now being repeatedly rejected under Guideline 4.3 (A) – Spam, despite being previously approved and published for at least two earlier versions. We have had multiple rounds of communication with the App Review team in the past, carefully addressing every request and making adjustments accordingly. These previous versions were reviewed and approved without any reference to 4.3 issues. However, since a recent update, we’ve been receiving rejections citing Spam 4.3 (A) — without any specific explanation or detailed reasoning. Even more frustrating: Each review now takes over a week to process, making our release cycle extremely difficult to manage. It required dozens of phone calls and emails just to get the app reviewed at all. I even had a meeting with an App Review team member, where I was told: “The recent updates are considered Spam 4.3, while the earlier versions that were approved are not.” But I am truly confused by this, because all the updates share the exact same codebase — there are no material differences between the approved versions and the ones now being rejected. This inconsistency and lack of clarity is making it impossible for us to move forward. We respectfully request: A clear and actionable explanation for why the recent versions are now considered Spam 4.3 (A), while earlier versions were not. Specific guidance or examples to help us understand what triggered this new interpretation. Transparency about what exactly changed — either in review criteria or policy enforcement — so that we can comply properly. We are committed to fully adhering to the App Store Review Guidelines and improving the app accordingly, but we can’t do that without transparency and fair communication. Any insights from the Apple team or other developers who’ve faced similar issues would be greatly appreciated. Thank you.