Hello,Does anybody know how I can change my team name? The one that shows up on the app store?Thanks,Julian

Hi everyone, I’m based in Europe, and I’m trying to fully understand the current App Store payment rules for an iOS app that sells digital services or premium functionality used inside the app. My goal is not to bypass App Store rules, but to implement the correct, compliant payment flow depending on the user’s region and the App Store requirements that apply there. The app would offer things like premium features, credits, or access to digital functionality inside the iOS app. The payment flow I would ideally like to support, where allowed, is: iOS app -> Cloud ahndling -> Stripe Checkout page -> user pays -> Stripe handling -> my backend marks the user as premium What I’m trying to understand is whether this flow is allowed, restricted, or prohibited depending on the user’s App Store storefront / region. My questions are: For digital goods, subscriptions, credits, or premium features used inside an iOS app, is Apple In-App Purchase still required by default? In which regions, exactly, can an iOS app use or link to an external payment provider such as Stripe for digital services used inside the app? For users in the United States, after the Epic Games v. Apple changes, can an app show an external payment option such as “Subscribe on the web” or “Pay with Stripe”? If yes, what are the exact requirements, limitations, wording rules, Apple fees, or reporting obligations? For users in the European Union, under the DMA-related rules, does Apple allow external purchases through Stripe or a web checkout? If yes, do I need specific Apple entitlements, StoreKit External Purchase APIs, Apple approval, transaction reporting, or payment of Apple fees? For the rest of the world, should I assume that Apple IAP is mandatory for digital content, subscriptions, credits, and premium app functionality unless Apple has a specific regional program allowing external payments? What is the correct way to determine which payment flow a user should see? Should this be based on the user’s App Store storefront / StoreKit storefront, rather than IP address, device locale, billing address, or country selected manually by the user? Would a regional routing approach like this be compliant? if App Store storefront == US: show Apple-compliant external purchase link / Stripe option if allowed elif App Store storefront is in the EU and the app has the required Apple entitlement: show Apple-compliant external purchase flow else: show Apple In-App Purchase only If a user pays through Stripe or another external checkout in a region where external payments are allowed, can my backend unlock premium features inside the iOS app? Or are there restrictions on granting access inside the app when the purchase was not completed through Apple IAP? For a first App Store release, is the safest approach to launch with Apple IAP only, then later add external payment options only in regions where Apple explicitly allows them? For developers who have recently submitted apps with external payment links for digital services: Which countries or storefronts were accepted? Did App Review require special entitlements? Were there specific wording or UI requirements? Did Apple require transaction reporting or apply additional fees? Were there differences between the US, EU, and other regions? In short, I’m trying to understand the practical compliant architecture: iOS app = Apple IAP by default external Stripe / web checkout = only where regionally allowed by Apple backend = unlock premium access after valid payment, whether Apple IAP or approved external payment payment UI = adapted based on App Store storefront / region I would really appreciate answers from developers, App Review experiences, or anyone familiar with the current Apple rules after the Epic ruling, DMA changes, and Apple’s External Purchase Link / StoreKit External Purchase programs. Thanks!

Small error in the placement of the URL of an error message: Hello, I just found a very tiny error, when this warning shows up, it tells about a url to learn more, except that url leads to an empty page because the url ends with a "." that got integrated to the url.

After a 2.3.2 rejection (two promoted subscriptions had identical display name + description), I withdrew the review submission to edit the subscription metadata. The app version moved to "Developer Rejected," but both auto-renewable subscriptions stayed stuck in "In Review." There is no active review submission attached to them anymore, yet: The subscription metadata (display name / description) is locked / not editable. There is no "Remove from Review" control on the subscription page or the version page. The version page no longer shows an "In-App Purchases and Subscriptions" section. Has anyone hit this orphaned "In Review" state? Is there a developer-side way to release a subscription from review, or is contacting Developer Support the only path? Appreciate any pointers, I'm on a deadline. App: Mossly: Plant Care Journal - Apple ID 6770594348 Subscription Group: Mossly Premium - 22098178 Subscriptions, both stuck: Mossly Premium - Monthly - 6770598241 (com.mossly.app.monthly) Mossly Premium - Yearly - 6770599597 (com.mossly.app.annual1)

Hi everyone, I'm hoping someone here has experienced this and can point me in the right direction. I submitted my first app, Homeowners Checklist, for review and on May 21 the status changed to "Ready for Distribution." It has now been over two weeks and the status has never changed to "Ready for Sale" and the app has not appeared on the App Store. Here is my current setup: App Store Version Release is set to "Automatically release this version" There is no scheduled release date set All agreements in Agreements, Tax, and Banking show as Active I have not received any emails from Apple indicating there is an issue This is my first app on a new developer account I have contacted Apple Support multiple times via email and phone with no resolution. My case has been open since May 21 with no clear answer. Has anyone experienced this with their first app? Is there something I might be missing, or is this a known delay for new developer accounts? Any advice on who to contact or how to get this resolved would be greatly appreciated. Case ID for reference: 102900108706 Thank you

Hello Apple Developer Community, I'm encountering a persistent issue with my App Store Connect account where the bank account is stuck in "Processing" status, preventing me from fully activating the Paid Apps Agreement. This has been ongoing for several weeks, and despite following all recommended steps, including resubmitting tax forms, there's no progress, also contacting support who promise to reply in 48 hours but never do. This is urgent as I have 19,000 customers waiting for the app to launch, and the delay is causing significant business impact. I'm hoping someone here has experienced something similar and can offer advice, or perhaps Apple support can chime in to expedite. Account Details: Organization: Prosperity Bliss PTE Limited (Singapore-based PTE Ltd) Address: 2 Venture Drive, #19-21 Vision Exchange, Singapore, WILAYAH PERSEKUTUAN 608526 Account ID: 93410065 Agreements: Free Apps and Paid Apps Agreements are listed as Active (effective Dec 17, 2025 – Apr 18, 2026), but Paid Apps seems blocked due to banking. Bank Account: PROSPERITY BLISS (8256), Singapore, SGD currency, USD royalties. Tax Forms (all submitted Dec 15, 2025): U.S. Certificate of Foreign Status of Beneficial Owner: Active U.S. Substitute Form W-8BEN-E: Active Singapore Tax Questionnaire: Complete (resubmitted today, Dec 19, 2025, to try update the system) Issue Description: Initially, there was a yellow banner saying: "Your banking updates are processing, and you should see the changes in 24 hours. You won't be able to make any additional updates until then." This appeared weeks ago when I first added the bank details. Even after submitting all tax forms on Dec 15, the status remains "Processing," and the banner persists. I can't edit or add anything else in the Banking or Tax sections due to this lock. Steps I've Tried: Submitted all required tax forms on Dec 15, 2025 – they show as Active/Complete. Resubmitted the Singapore Tax Questionnaire today (Dec 19) as a potential fix, but no change yet. Logged out/in, cleared cache, tried different browsers/devices – no luck. Contacted Apple Developer Support via the web form (under Agreements, Tax, and Banking) multiple times over the past week – submitted tickets with screenshots and details, but no responses so far. Attempted phone support using regional numbers (+65 numbers for Singapore/Asia-Pacific), but got routed to general customer support instead of developer-specific. Requested a callback through developer.apple.com/contact/ – still waiting. From what I've read online (e.g., similar issues on Reddit and Apple Discussions), this seems like a common backend glitch, especially for non-US accounts, where the system gets into a loop (banking waiting on tax, but tax is done and locked by banking processing). Official docs say it should resolve in 24 hours, but it's been far longer. Has anyone else with a Singapore or international business account faced this and resolved it? Did you have to escalate to a specific team, or is there another workaround? Any tips on getting a faster response from support? I've attached screenshots of the Agreements page, Bank Accounts section (showing "Processing"), and Tax Forms for reference. Thanks in advance for any help – this is holding up my app distribution! Best, Frederik

Hi, I am new to Apple developer world. I am trying to publish my app. When I submit the app for review, i am getting a rejected status with unresolved issues. On the distribution page, i am getting "1.0 Invalid Binary". But no information about what the issue is that needs fixing, no email to tell me what the issue is. Has anyone seen this before? I have sent two emails to Apple, both unanswered and cannot get hold of them on the phone! As a paying member, i expect a bit more help and communication from Apple!!! app id: 6772153999

Hello, about a month ago, the Apple Store account of my former company was closed. I was already registered as a developer, so there's no problem with that. Was my personal account also closed when this company account was shut down? I contacted Apple support about this, and they said they would investigate. I still haven't received a response. Was my account closed? Or is there another issue? Nobody is explaining why this happened.

My app OneNest (App Store ID: 6762323106) has had in-app purchase localizations in "Waiting for Review" status for nearly 2 weeks. My subscriptions were approved but the localization for both the subscription and lifetime purchase IAPs remains pending. This is actively blocking customers from completing purchases in my live app. I have an open support ticket but have not received a response in 2 weeks. Has anyone experienced this? Is there a way to escalate IAP localization review specifically? Any guidance would be appreciated.

We are adding tap2pay as a payment method to our existing POS app. Our app is distributed business to business via Custom Apps. To get a production entitlement there's a checklist, in this checklist there are several sections. For Section 3, "Requirements for Enabling Tap to Pay on iPhone" there's a paragraph: If you distribute your app with programs such as Unlisted apps, Custom apps, or the Apple Developer Enterprise Program (ADEP) these requirements are applicable only if users are expected to accept terms and conditions using an Apple Account on the iPhone. We are using Custom Apps but its unclear what 'terms and conditions' refer to, does this refer to our own t&cs and not Apple's t&cs?

Posting because I have run out of changes to make and Apple is still hitting me with the same guideline. I run Bot Binder (App Store ID 6771506484), a fan-built collection-tracking app for action-figure collectors. No Hasbro license. No trademarked wordmark in the app name or icon. One developer, paid account, side project. Three 4.1(a) Copycats rejections in six days. May 30, vc109 rejected. Subtitle "Transformers Collection Hub" and keywords led with "transformers." Acknowledged. I rewrote the subtitle, scrubbed the keywords, shipped vc114 with a Hasbro attribution disclaimer modeled on Dex and Yugipedia, plus a Resolution Center reply citing 15 live App Store comparables. June 1, vc114 rejected. Same guideline. Flagged screenshot was the dashboard hero, which still rendered marketing text and a Hasbro figure in the featured spot. Acknowledged. I gated every brand-bearing UI surface behind an iOS check, swapped the iOS feature pool to third-party and upgrade-kit figures only, replaced the original mascot in both the iOS app icon and the in-app head graphic with a new abstract design, regenerated the splash, and shipped vc132. The mascot replacement was a real concession. That mascot is the visual identity of the brand on web and Android. I changed it on iOS specifically because the reviewer signaled the icon area was in scope. June 4, vc132 submitted with full scorched-earth metadata. Description rewritten end to end, zero third-party brand/character/trademark references anywhere (verifiable in the live appStoreReviewDetail record). Promotional text and keywords generic. Screenshots reshot from the gated iOS build with no franchise overlays or characters in hero positions. In-app disclaimer footer on every iOS screen. Public support page hosts the same disclaimer. Age rating bumped 4+ to 12+. June 5, 1:41 AM. Rejected again. Two notes: 4.1(a): "The metadata appears to contain potentially misleading references to third-party content. Specifically, the metadata still includes content that resembles Transformers without the necessary authorization. … If you do not have the necessary rights to the third-party content, it would be appropriate to revise the metadata to remove the third-party content before resubmitting for review." 2.3.3: "The iPhone and iPad screenshots do not show the actual app in use in the majority of the screenshots. Marketing or promotional materials that do not reflect the UI of the app are not appropriate for screenshots." This is the third time the rejection has cited "the metadata" without naming a single specific field. After three rounds my description has zero third-party references, promotional text has none, keywords have none, and screenshots are stripped. There is nothing left in the listing to act on. Before redesigning the mascot for vc132 I sent App Review a direct question asking for any guidance on the icon and mascot direction. The full reply: Hello, We appreciate your efforts to comply with the App Review Guidelines. We are not able to provide feedback on app concepts or features, but we recommend evaluating your suggestions against the App Review Guidelines, the Apple Developer Program License Agreement, and the Human Interface Guidelines. Additionally, if you are considering implementing any of the following functionality, we recommend reviewing all associated reference material: Apple Developer Apple Copyright and Trademark Guidelines Game Center iCloud In-App Purchase You may also choose to post a question in the Apple Developer Forums. Best regards, App Review That reply, taken with three rejection notes that name no specific field, reads exactly like a large language model behind a developer-relations endpoint. Nothing app-specific. References functionality with no bearing on my submission (Game Center, iCloud, In-App Purchase). Closes by redirecting me to this forum, which is the only reason I am writing the post. The whole exchange feels like I am talking to a system, not a person. If a human reviewer is on the other end of this thread, I am asking you to engage as one. One sentence naming the specific flagged surface resolves this thread today. The two notes also contradict each other on remediation. 2.3.3 wants screenshots showing the actual app in use, not marketing. 4.1(a) wants third-party-resembling content removed from "the metadata." Once the listing copy is generic and the screenshots show the real UI, what those screenshots show is the in-app catalog. So the only third-party-resembling content the reviewer can still be pointing at is the catalog itself, a different scope than how metadata versus in-app content has historically been drawn. What that means in practice: Bot Binder has over 1000 active users with new collectors joining every day, and the in-app catalog contains more than 10,000 figures. If 4.1(a) is pointing at the catalog, the only remediation Apple's note is offering me is to remove that content, which isn't viable. The catalog is the product. Stripping 10,000 catalog entries invalidates the collections, wishlists, and trade data of every existing user. There is no version of this app that satisfies that interpretation and still functions. Either the scope is different than I'm reading, or 4.1(a) is being applied to a category of app that cannot exist on the App Store, in which case I need that stated directly so I can stop iterating. What I need. App Review staff, if a person is reading this: name the surface. Which field, which screenshot, which paragraph still flags as third-party-resembling? One sentence. If the answer is "the in-app catalog," say so and I will stop submitting. Developers running unlicensed-IP collector apps on the App Store, particularly iCollect Action Figures (656405076, "Transformers" in subtitle), The Ark TFC86 by Chris Sudac, My G.I. Joes (1606553734), Dex (1555489854), Yugipedia (1026470546), Brick by Brick (525328219), Pokellector (600580227). What got you through 4.1(a)? Disclaimer language, or did you have to remove franchise content from the iOS build itself? Asking because some of you are doing exactly what I am being rejected for and your apps are live. Anyone who has booked an App Review Appointment for 4.1(a): did you get surgical guidance, or the same template? Full submission timeline, build IDs, screenshots, and the appStoreReviewDetail record available on request. After six days of taking every revision step Apple has asked for and landing in the same place, I just need actual specificity from somebody.

I have been rejected twice under Guideline 2.1(b) because my In-App Purchase subscriptions are not submitted for review. I cannot figure out how to attach them to my submission. Here is my situation: I have 6 auto-renewable subscriptions fully configured in App Store Connect under "Barrel Pro Subscriptions" — all have screenshots, pricing, descriptions, and review notes My app is iOS only, built with React Native/Expo My current version is 1.1, Build 10 (1.1.0) The problem: The "In-App Purchases and Subscriptions" section does not appear anywhere on my version page. I have scrolled to the very bottom and it is not there. I cannot find any way to attach my subscriptions to my submission before clicking "Submit for Review." The blue info box on the Subscriptions page says: "Your first subscription must be submitted with a new app version. Select it from the app's In-App Purchases and Subscriptions section on the version page." But that section does not exist on my version page. What I have tried: Cancelling the rejected submission and starting fresh Creating a new version (1.1) manually Uploading a new build (Build 10) Checking both "In-App Purchases" and "Subscriptions" sections in the sidebar Has Apple removed this section from the version page? How do I attach my subscriptions to my submission in 2026? Any help is greatly appreciated. Thank you.

我测试了 1、通过xcode安装到模拟器 2、通过xcode安装到手表 3、通过testflight安装到手表 都可以找到内购产品id。 但是提交审核后，审核回馈的信息都是找不到产品ID，已经被拒好多次了。 我账户其它应用的内购都是正常交易的，我做了如下检查： bundle id 第一次提交要选择的内购产品 内购产品的状态也是“Waiting for Review” 代码也是反复检查的，上面3种测试都是正常的 我留意到有两个奇怪的问题是， 1、我的二进制包被拒后过了几个小时，我的内购产品会因为没有提供二进制包而被拒。 2、内购产品会出现“Developer Action Needed”的状态，但是没有指明我需要采取什么行动，只是内购的描述的状态是“Rejected” 我想请教一下这里的好心人，我还需要做什么检查和修改才能让审核的时候可以找到产品id？

I am experiencing a critical and frustrating delay with an internal business application review. I would highly appreciate any insights or advice from the community or the Apple team on how to move forward, as our business operations are heavily impacted. Here is the exact timeline of our submission process: May 14 & May 19: Submitted the initial builds. On both occasions, the app transitioned to In Review within 4 hours but was rejected due to specific metadata/compliance deficiencies. Resolution: We thoroughly addressed all the points mentioned in the rejection notes, completed the missing requirements, and prepared a fully compliant build. May 22: Resubmitted the corrected build. Unlike the previous quick turnarounds, the app became completely stuck in the queue (Waiting for Review) with zero communication or updates for over a week. June 1: Out of concern that the submission was caught in a system glitch, I canceled the review and resubmitted it. It is currently still waiting with no status change. Expedited Review: I submitted an Expedited Review request detailing our urgent operational needs, but we have received no response or acknowledgment yet. Business Impact & Context: This is an essential internal tool for our business operations. We currently have 20 employees utilizing it via Ad Hoc distribution, but we are actively onboarding new personnel who need immediate access to the app to perform their daily duties. The limitations and manual management of Ad Hoc distribution are now causing a severe bottleneck in our daily workflows. Given that the first two reviews started within hours, it feels like the app has been flagged or placed into a different administrative review queue after the rejections, but the complete silence is hurting our business. Has anyone dealt with a similar sudden freeze after fixing rejection points? Are there any alternative communication channels available when both App Store Connect and Expedited Review forms go completely unanswered? Thank you in advance for your time and help.

Hello everyone, I submitted the first update for my app on April 14. On April 18, I canceled that submission and immediately resubmitted it the same day, as many people suggested that resubmitting might help speed up the review process. Today is June 4, and after 47 days, the update is still stuck in “Waiting for Review.” I’ve seen that many other developers are experiencing the same issue, but 47 days is a very long time for me, and I have no idea how much longer I should expect to wait. I hope we can all find a solution to this situation soon. Any advice, insights, or shared experiences would be greatly appreciated. Thank you all.

With the shift away from the Trends section of App Store Connect, how do I see Total Active Subscriptions for all my apps in the app store that offer subscriptions? I found the aggregate number and the associated charts very useful as a way of monitoring over performance across all my apps and which are related. Since the June 1 shift to analytics on a per app basis, several important (for me anyway) charts are missing and no longer work. Is there another way to get this data? If you are going to take a function away you should give us an alternate way to get the same data.

Hello, I need advice from experienced iOS developers. I have a completed iOS application ready for App Store submission. My Apple Developer account is active and fully paid. I successfully created the Bundle ID. I added the developer to App Store Connect with the Admin role and access to all apps. The developer has a Mac and works on the project. I only have an iPhone and do not own a Mac. The developer says they may need direct access to my Apple Developer account to complete the signing process and upload the app. My questions are: Is the Admin role in App Store Connect sufficient for uploading an app to the App Store? Does the developer really need my Apple ID and password, or should the current permissions be enough? What is the safest and recommended way to allow a developer to complete the upload without sharing my account credentials? Are there any additional permissions required in Apple Developer that I may have missed? Thank you for your help

I recently noticed that an app called Private Browsing Web Browser has been ranking at the top for the keyword “browser” on the App Store for a long time, even ahead of well-known browsers like Chrome, Firefox, and Safari. This is not only the case in the U.S.; it also appears to rank top in many other regions. This app has not been updated for a long time, and both its interface and feature set seem extremely basic. There also appears to be nobody to discuss it on the internet, and some of the App Store ratings look very suspicious. I previously reported this to the Apple team by email, and questioning about the algorithm, but they consistently responded: The App Store ranking system has no problem, and it's working as expected.” I wanted to ask everyone: Do you think it is normal for this app to rank number one for “browser” on the App Store? Also, the same developer has another very similar browser app called Snowbunny Private Web Browser, which also ranked high.

Does the App Review process have access to Apple-Hosted Asset Packs during review? My app uses Asset Packs to offer a library of data to the end-user (with a workaround, if unavailable), but I am frequently seeing the workaround screen in App Review with errors I haven't seen elsewhere. The latest error I encountered (via the App Review team's feedback) was: "A server with the specified hostname could not be found." thrown from (to my belief) AssetPackManager.shared.ensureLocalAvailability. This is unexpected to me, as both this code as well as the asset packs have already been released and are working reliably in production. Has anyone else experienced these issues?

Hi Apple Developer community and Apple Review team, I'm hoping to get assistance with a persistent 4.3(a) rejection for our app ByGate (net.bygate.vpn). Submission ID: c8278a90-8e90-45b2-9256-d2e6b34e9518 Latest review date: May 19, 2026 Our situation: ByGate is not a generic VPN tool. It is a dedicated client application for ByGate's proprietary server infrastructure. The app works exclusively with ByGate servers - users cannot enter custom addresses, import third-party configurations, or connect to any other provider. It is functionally similar to a banking app or a streaming app: it only connects to one specific service. We have been operating ByGate as a cross-platform service: Android app live on Google Play Windows desktop app distributed via our website macOS desktop app distributed via our website Active paying subscriber base across all platforms Our existing users regularly contact our support team asking when the iOS version will be available. They are already using our servers and subscriptions on other devices and want the same experience on iPhone. Why we believe the rejection doesn't apply: Apple's own guidelines (4.8) recognize "apps that are a client for a specific third-party service" as a distinct, legitimate category. ByGate fits this exactly - the same way Netflix, Spotify, or any banking app is a dedicated client for one specific service. The concern about "similar binary" is understandable - like many VPN apps, we use an open-source networking library. But using a shared networking library (like WireGuard, OpenVPN, or in our case libbox) does not make an app conceptually identical to others, just as using SQLite doesn't make a database-backed app a duplicate of every other such app. Unique features of ByGate not found in other apps on the App Store: Split tunneling mode specifically pre-configured for Russian-language internet services Anonymous account creation (no email or phone number required) Freemium model with 100 MB free tier, no registration required Access exclusively to ByGate's own server nodes in Europe and USA Our 24/7 support on Russian-language We have responded to every rejection with detailed explanations, but receive only the standard templated response. We are genuinely committed to compliance and would welcome direct guidance on what specifically needs to change, or a review call with the App Review team. Thank you for your time.