Hi everyone, I’m unable to enable Xcode Cloud for any app on my account. At the final step of the Xcode workflow setup (“Confirm App on App Store Connect”), pressing Complete always returns: “ could not be added to Xcode Cloud. Authentication credentials are invalid.” This affects both existing apps and completely new test apps with fresh bundle IDs. What I’ve verified • I am Account Holder and Admin. • All agreements are accepted. • App creation, bundle ID registration, and certificate management work normally. • I’ve removed/re-added my Apple ID in Xcode and cleared all Xcode-* tokens from Keychain. • Test apps in clean Git repos reproduce the same error. Support I have already opened Case ID 102769512657 with Apple Developer Support, but I’m posting here in case others have seen this issue or know of additional steps to confirm the provisioning state.

90714: Invalid binary. The app contains one or more corrupted binaries. Please rebuild the app and resubmit. 我开发的OC项目，三个月前打包分发还没有问题，半个月前开始就一直报这个错。查了很多资料都无法解决，所有的SDK也都升级了，还是报这个错，麻烦Apple的工程师帮忙指正一下问题，如何解决这个问题。

Hello, I submitted my application for review and it's not being processed. Each time, I wait months for a response. This is incredibly frustrating because I'm already too late to announce my project. I've repeatedly requested an expedited review, but it doesn't work. Is anyone else experiencing the same issue?

Started an ASO challenge on an older mother-baby app and began by analyzing competitors’ ranked keywords to uncover gaps, relevance, and high-intent phrases using tools like Appvector. By identifying core keyword roots and filtering by context and search intent, I narrowed down high-value opportunities to expand from 146 to over 1,000 relevant search terms for the next steps in the ASO strategy.

My iPhone VoIP app, which I'm developing, uses Apple Push Notification service (APNs). I have a question regarding the following statement found in "[Overview of app transfer > Apps using push notifications]" Overview of app transfer You must manually reestablish push notification services if transferring an app that uses the Apple Push Notifications service (APNs). The recipient must create a new client SSL certificate using their developer account, as associated client SSL certificates, TLS certificates, and authentication tokens aren’t transferred. Question Let's say the recipient of the app transfer creates a "new SSL certificates, TLS certificates, and authentication tokens." Afterward, we need to verify that the Apple Push Notification service (APNs) works correctly when combining the transferred app with this "new SSL certificates, TLS certificates, and authentication tokens." However, until the recipient finishes verifying that it works correctly, the transferor want to keep the app available for download as before and be able to use the Apple Push Notification service. Is this possible? More specifically, can the recipient test the app to be transferred on TestFlight "before the transfer is completed"? I want to combine it with the "new SSL certificates, TLS certificates, and authentication tokens." and test it on TestFlight. Reading "[Initiate an app transfer]," it mentions the existence of a "Pending App Transfer" status. During this "Pending App Transfer" status, can the recipient test the app on TestFlight? Initiate an app transfer After you initiate the transfer, the app stays in its previous status, with the Pending App Transfer status added, until the recipient accepts it or the transfer expires after 60 days. Also, if there are any documents describing these procedures, I would appreciate it if you could share them. Thank you very much.

Hi all, I'm looking for a way to upload app builds to App Store Connect on Windows and Linux (I know on MacOS we can use Xcode to do that). I found that the Transporter command line tool could be used for this task here - https://help.apple.com/app-store-connect/#/devb1c185036. Then I did some research on the Transporter, and found that to download it you need to be approved by Apple for qualification in here - https://itunespartner.apple.com/en/movies/faq/Transporter_Getting%20Set%20Up. Other than this I can't find much info on exactly how to get access to the tool. Surprisingly not much resources about this on the Internet, and all the apple doc seems very vague on this. So my question is: Can the Transporter tool really be used to upload builds to App Store on Windows and Linux? If yes, what is the exact steps to get access to it? Has anyone been able to go through the process and use the tool?

Hello everyone, I recently submitted my new app “Bitcoin Miner – Mining Pool” for App Review. The app was submitted under my Apple Developer account (Account Holder: Harshil Patel). However, the status has been “Waiting for Review” for over 2 days without any movement. Details: Submission platform: App Store Connect Metadata & screenshots uploaded correctly No compliance warnings or “Missing Information” alerts No previous rejections for this version I understand the review process time may vary, but I’m unsure whether this delay is normal or if there’s something more I should check on my side. Questions for the community / Apple Team Is there a typical timeline for apps currently showing “Waiting for Review”? My only goal is to ensure the submission process is moving correctly. Any guidance or suggestions will be highly appreciated. Thank you! — Harshil Patel

Hello everyone, I am experiencing an unusually long review delay with my app Avanta (App ID: 6753948874) and would like to request guidance or escalation support if possible. 📌 Timeline & Issue Summary Our first submission was made on October 14, 2025. The app was initially reviewed and rejected once due to screenshot issues (nothing related to functionality or guideline violations). We immediately corrected the screenshots and resubmitted on November 3, 2025. Since then, the build has been stuck in “Waiting for Review” for more than 25 days, and we have received no further updates, clarifications, or review activity in App Store Connect. 📌 Why I’m Concerned This delay is far beyond normal review processing times (typically 24–72 hours). Our app has no unresolved guideline issues — only screenshots were requested once, and the updated assets are fully compliant. The lack of any movement (no “In Review”, no communication) makes me unsure whether the submission is stuck due to a technical/system error. 📌 What We Have Already Tried Double-checked all metadata, screenshots, and compliance items. Verified export compliance and agreements. Contacted Apple support through App Store Connect → no response yet. Tried cancelling/resubmitting earlier versions, but the issue persists. 📌 Request Could someone from the App Review team please look into whether this submission is stuck? We would sincerely appreciate guidance or escalation if necessary, as we have been waiting over 45 days since the first submission and 25+ days since the last resubmission. We respect the review process and understand high workload periods, but this delay appears to be a technical issue rather than a standard queue wait. Thank you in advance for any support or clarification you can provide. Kind regards, Taha

​ My app has been rejected multiple times during the last few weeks because Apple reviewer is unable to complete the purchase on revenue cat paywall. They gave this error message: Guideline 2.1 - Performance - App Completeness We were still unable to purchase the subscription successfully. Review device details: Device type: iPad Air 11-inch (M2) OS version: iPadOS 26.1 Next Steps When validating receipts on your server, your server needs to be able to handle a production-signed app getting its receipts from Apple’s test environment. The recommended approach is for your production server to always validate receipts against the production App Store first. If validation fails with the error code "Sandbox receipt used in production," you should validate against the test environment instead. Resources Note that in-app purchases do not need to have been previously approved to confirm they function correctly in review. Note that the Account Holder must accept the Paid Apps Agreement in the Business section of App Store Connect before paid in-app purchases will function. Learn how to set up and test in-app purchase products in the sandbox environment. Learn more about validating receipts with the App Store.   The offerings are fetched correctly but they are unable to complete the purchase. I tested on my physical iPhone with real account (not sandbox) and get the same exact error. I have provided screenshot of the paywall screen and my App Store Connect pages below. I think issue might be because my subscriptions on App Store are not approved but I’m not sure. I heard you are supposed to submit them same time when you submit your build. I submitted both but Apple also rejected my subscriptions saying the images were duplicate. Now they say “developer action needed” First of all, it says the images are optional so why does it matter what they are? Second of all, what image am I supposed to provide there then?  Guideline 2.3.2 - Performance - Accurate Metadata We noticed that your promotional image to be displayed on the App Store does not sufficiently represent the associated promoted in-app purchase and/or win back offer. Specifically, we found the following issue with your promotional image: – You submitted duplicate or identical promotional images for different promoted in-app purchase products and/or win back offers. Next Steps To resolve this issue, please revise your promotional image to ensure it is unique and accurately represents the associated promoted in-app purchase and/or win back offer. If you have no future plans on promoting this in-app purchase product, you can delete the associated promotional image in App Store Connect. Resources Learn how to view and edit in-app purchase information in App Store Connect. Discover more best practices for promoting your in-app purchases on the App Store.   Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Request an App Review Appointment at Meet with Apple to discuss your app's review. Appointments subject to availability during your local business hours on Tuesdays and Thursdays. Provide feedback on this message and your review experience by completing a short survey.     ​

When I try to get a new API Key I get the following error. "API Keys cannot be created due to an invalid Program License Agreement. Please update this agreement and try your request again." I have been to the agreement section, and it says: "Issued October 8, 2025. Accepted November 19, 2025." Any idea why I still get this error?? Not sure if that makes a difference. I had a paid account, but I didn't renew it because I don't need it anymore, and I was told that I can still use this account for free for app testing.

Hello everyone, I'm currently developing an iOS application and have a question regarding project architecture changes and App Store Connect submissions. My app is already uploaded to App Store Connect and is being used for internal testing via TestFlight. During development, I've realized my initial project architecture is flawed and unsustainable. The Problem and Proposed Solution I've decided the best approach is to completely redevelop the app from scratch using a new, clean Xcode project that implements a better architecture (e.g., MVVM, Clean Architecture). The Core Question If I create a brand new Xcode project for the redeveloped app, can I: Use the same Bundle Identifier (com.mycompany.myapp) in the new project? Successfully archive and upload the build from this new Xcode project to the existing app on App Store Connect? In essence, does App Store Connect require the new build to originate from the same Xcode project structure as the previous builds, or does it only validate the Bundle Identifier and Version/Build Number? Any advice or confirmation from developers who have gone through a similar complete project overhaul would be greatly appreciated. Thank you!

Regarding the “App Store Downloads” Analytics Report, I have submitted a report generation request with accessType: ONE_TIME_SNAPSHOT. Reference: https://developer.apple.com/documentation/analytics-reports/app-download I would like to confirm the scope of the Campaign data included in the report generated by this request. In the App Store Connect UI, I understand that there is an upper limit of 200 Campaign entries displayed. For the report output, however, could you please confirm whether it includes all Campaigns measured on the App Store Connect side? Or is there also any upper limit on the number of Campaign records included in the report itself?

Dear all, This is my first post in this forum - and, in fact, my first app, too! I'm glad to be here, and thanks in advance for your help. I'm looking to offer an app for a one-time payment. I'd also like people to be able to try the app for a week. It seems that the "Pricing and Availability" section in App Store Connect is not the right place to configure this kind of offer. It does allow me to set a one-time price, but I cannot find a trial-period there (or am I missing something?) Two different strategies seem possible here: Using in-app-purchases: make the actual app free, but ask users after a week to buy a non-consumable IAP. The problem with that: I need to verify that the app has been installed for seven days ... even if it has been uninstalled at some point. Using subscriptions: There is a "free trial" option for subscriptions. But after that free trial, subscriptions are being payed periodically. I'd rather have the user only pay once for lifetime-access. Some apps seem to use strategy 1 - I believe the "Lap swim" app does. But still it seems like a bit of a hack - is there a more elegant way to achieve this?

Hello, I’m developing an app that provides physical services such as equipment storage, maintenance, pickup, and delivery. The app does not provide any digital content, digital features, or any form of digital subscription. For payments, we are using an external payment gateway (similar to Stripe Billing or Braintree): iOS: Users are redirected to Safari to complete the payment. We also plan to support annual automatic renewal billing, using the payment gateway’s “billing key” or “recurring billing” feature. This is essentially a card auto-charge for a physical service, and it is not an in-app subscription. I want to ensure that our implementation is fully compliant with Apple’s App Store Review Guidelines, especially 3.1.5(a) regarding physical goods and services. I would appreciate guidance on the following: For apps providing physical services, is it acceptable to process payments through an external browser (Safari) instead of using In-App Purchase? Is recurring billing / automatic renewal with an external payment provider allowed, as long as the service being billed is physical and not digital? For apps offering only physical services, should we completely avoid using the Monetization → Subscriptions section in App Store Connect, since those subscription products apply only to digital content? Our goal is to ensure that the app follows Apple’s policies correctly and does not mistakenly fall under the category of digital subscriptions. Thank you very much for your help.

Hello everyone, I recently submitted my new app “Bitcoin Miner – Mining Pool” for App Review. The app was submitted under my Apple Developer account (Account Holder: Harshil Patel). However, the status has been “Waiting for Review” for over 2 days without any movement. 📍 Details: Submission platform: App Store Connect Metadata & screenshots uploaded correctly No compliance warnings or “Missing Information” alerts No previous rejections for this version I understand the review process time may vary, but I’m unsure whether this delay is normal or if there’s something more I should check on my side. 👉 Questions for the community / Apple Team Is there a typical timeline for apps currently showing “Waiting for Review”? My only goal is to ensure the submission process is moving correctly. Any guidance or suggestions will be highly appreciated. Thank you! — Harshil Patel

I previously added an iOS version 1.0.2 to App Connect, but decided to call it 1.1 instead. Currently, I have a build of 1.0.2 "Developer Rejected" now, but I can't find a way to remove version 1.0.2 or add version 1.1. How do I do this?

Hello, I noticed the Product.SubscriptionInfo subscriptionPeriod (of type Product.SubscriptionPeriod) is different for the same product between StoreKit Testing in Xcode and the sandbox/App Store (production) environment. For a “1 week” auto-renewable subscription, we get the following: StoreKit Testing in Xcode: 1 week gives a subscriptionPeriod with value of 1 and a unit of Product.SubscriptionPeriod.Unit.week Sandbox/App Store: 1 week gives a subscriptionPeriod with value of 7 and a unit of Product.SubscriptionPeriod.Unit.day This created issues in my app because I used the localizedDescription of a Product.SubscriptionPeriod to display a text similar to “$4.99 per week”. This is what I obtain with the StoreKit Testing in Xcode, but in the Sandbox/App Store environment, it displays “$4.99 per day” (because the subscriptionPeriod is “7 Days” and the unit is then .day). Obviously, this is not what I wanted to display. Other periods like “1 month”, “2 months”, “3 months”, “6 months, and “1 year”, the period provided by both StoreKit Testing and Sandbox/App Store correspond to the period unit specified in App Store Connect. In addition, I want to report that for a weekly subscription/offer or a 2 weeks offer, Product.SubscriptionInfo.subscriptionPeriod or Product.SubscriptionOffer.period == .weekly or .everyTwoWeeks is always false. We observe the following: With Sandbox or App Store live production: 1 week, Product.SubscriptionInfo.subscriptionPeriod == .weekly is false (because it’s “7 days”) 1 week, Product.SubscriptionOffer.period == .weekly is false (because it’s “7 days”) 2 weeks (offer), Product.SubscriptionInfo.subscriptionPeriod == .everyTwoWeeks is false (because it’s “14 days”) 2 weeks (offer), Product.SubscriptionOffer.period == .everyTwoWeeks is false (because it’s “14 days”) But with an Xcode StoreKit configuration file: 1 week, Product.SubscriptionInfo.subscriptionPeriod == .weekly is true (because it’s “1 week”) 1 week, Product.SubscriptionOffer.period == .weekly is true (because it’s “1 week”) 2 weeks, Product.SubscriptionInfo.subscriptionPeriod == . everyTwoWeeks is true (because it’s “2 weeks”) 2 weeks, Product.SubscriptionOffer.period == . everyTwoWeeks is true (because it’s “2 weeks”) So in sandbox and production, .weekly and .everyTwoWeeks is never possible. If someone from Apple could check the feedback FB19605865 🙂 Thank you Regards, Axel, @alpennec Code: do { let productIDs: [String] = ["revenueSocks_weekly_trial"] let products: [StoreKit.Product] = try await Product.products (for: productIDs) let weeklySubscription: StoreKit.Product = products.first! let displayPrice: String = weeklySubscription.displayPrice // For a weekly subscription in App Store Connect // With an Xcode StoreKit configuration file: subscriptionPeriod unit is Week (week), value is 1 → "1 Week" // With the Sandbox + App Store: subscriptionPeriod unit is Day (.day), value is 7 → "7 Days" let unitString: String = weeklySubscription.subscription!.subscriptionPeriod.unit.localizedDescription print("\(displayPrice) per \(unitString.localizedLowercase)") // StoreKit configuration file → "$4.99 per week" // Sandbox + App Store → "$4.99 per day" } catch { print(error) }

Hi all, Our app has been in review since November 1st, and the process has been very slow. We often wait several days between responses, and we keep receiving questions we’ve already answered - even when we point this out in our replies. We’ve contacted Developer Support by email, but the only reply we received was that they’re sorry for the delay and will look into it. We’re unsure whether requesting a phone call might help or if it could pause or reset the review process, and since we’re hoping the next response will finally approve the app, we’ve hesitated to use that option. Has anyone experienced something similar, or does anyone know whether requesting a call has any impact on the current review status? Thanks for any guidance.

Hello! I'm encountering a weird issue on TestFlight/AppStoreConnect. I've builds that are in the "Processing" state since the 19th (that's 5 days ago from the date of this post). I've tried to generate new builds to see if it was just a fluke during those days, but new builds generated today also get stuck at processing. It's starting to become an issue because everybody on our team that's not a developer can't test the latest changes... Is there any way that I can get them unstuck? Thanks!

My account has been active and in good standing for the past 2 years, and during this time I have never received any warnings or issues. Recently, after Apple reviewed my account, I received a notification about possible termination. After carefully reviewing the situation myself, I realized what may have caused this: I originally registered my Apple Developer account as an Individual Developer Account, However, the bank account used for App Store payments belongs to my registered company, At the time, I was not aware that the legal entity of the bank account must match the Apple Developer account registration. This was not done with any intention to misrepresent or misuse the platform. It was simply a misunderstanding of the account requirements. We have never deceived our users or the Apple Review Team in any way. For us as developers, providing an excellent user experience has always been our top priority, and we have always aimed to follow Apple’s review and compliance standards closely. We sincerely hope that, given our situation, the Apple Review Team could grant us an opportunity to correct these issues.