Need assistance in implementing this device management feature. Our free plan lets each person use one special device. To make this work, we need to set up device control right after they log in. Because of this, we can’t let people use our app on more than one device or platform at the same time. If we don’t ask them to log in, we won’t know if they have already used their free device on Android or the Chrome extension. But Apple wants us to give people free access to things that don’t need an account. Can you help us find a way to do this?

Issue Description The submission did not include all the required information for apps offering auto-renewable subscriptions. The app's metadata is missing the following required information: A functional link to the Terms of Use (EULA). If you are using the standard Apple Terms of Use (EULA), include a link to the Terms of Use in the App Description. If you are using a custom EULA, add it in App Store Connect. Next Steps Update the metadata to include the information specified above. Resources Apps offering auto-renewable subscriptions must include all of the following required information in the binary: Title of auto-renewing subscription (this may be the same as the in-app purchase product name) Length of subscription Price of subscription, and price per unit if appropriate Functional links to the privacy policy and Terms of Use (EULA) The app metadata must also include functional links to the privacy policy in the Privacy Policy field in App Store Connect and the Terms of Use (EULA) in the App Description or EULA field in App Store Connect. Please let me know where I have to add this link (EULA). And by EULA, they mean a simple terms of use link, or is it something else?

I have submitted my app for review on 3rd of June 2025, and its status is stuck at 'Waiting for Review' since then until today (16th June 2025). I have requested expedited review and contacted support multiple times, but to no avail. I am posting it here hoping that it can get expedited as our stakeholders depend on this app update. Thank you. My support ticket are as follow : 102617392761

Hello, I am facing an issue with App Store Review Guideline 4.3(a) - Design - Spam. My app was rejected because it was found to be similar to another app previously uploaded on a different Apple Developer account. However, I have lost access to my old developer account and cannot remove or modify the previous submission. Currently, I am unable to: Log in to the old Apple Developer account Remove or update the app that is causing the conflict My new app is intended for internal testing only and is not yet published on the App Store. I have made efforts to modify the app, but the system still detects similarities with the old app. I would like to ask for advice or assistance on how to proceed in this situation, as I no longer have control over the previous account. Has anyone experienced a similar situation, and is there any way Apple can help resolve this? Thank you very much for your support.

Hello Apple Developer Team, I am currently integrating In-App Purchases (IAP) in my iOS app and would like to get a clear understanding of the App Store Review Guidelines related to offering paid digital content. My app provides access to digital content/features after payment. I would like to know if it is permitted to: Navigate the user to an external browser (e.g., Safari) from the app to complete the payment via a web-based payment gateway (like Razorpay, Stripe, etc.), and then unlock content in the app after verifying payment on the server. In this case: No purchases are made directly within the app. The app does not use an embedded WebView for the payment. The payment page is loaded in Safari via a deep link or external redirect. Would this approach comply with Apple’s guidelines, or would it be considered circumventing IAP requirements? I want to make sure I comply fully with Apple's policies. Thank you in advance for any clarification. Best regards, Sayed Muhammed App Name: Dream Treasure

Hello, We want to upload an app for our customers that uses our company's authentication system which will enforce 2factor (2fa) soon. The App review section in App Store Connect accepts only username and password. What is the desired way to interact with the review process now? Will Apple themselves register an account to use with 2fa? Or how could we provide access to the token? Can someone help? Regards

Hi, My developer payment was marked as "Paid" on June 5, 2025 in App Store Connect. As of June 16, the funds have still not arrived in my bank account. Apple only provides a Transaction ID (324756355), but no EFT or SWIFT reference number. My bank confirmed there is no record of any incoming or returned payment. Other developers have received their June 5 payments already. Mine seems to be either not sent or stuck. Apple support keeps telling me to wait 30 days, but without proof of actual transfer, this isn’t acceptable. Has anyone experienced this kind of delay before? Thanks.

Dear community, in order to modernize our build pipelines, I wanted to try out the new App Store Connect build upload API that was introduced in the WWDC video "Automate your development process with the App Store Connect API". However, when POSTing to https://api.appstoreconnect.apple.com/v1/buildUploads, I receive the following error message: { "errors": [ { "id": "9fb916ea-4d26-4712-8c55-d1d4b5320bf2", "status": "404", "code": "PATH_ERROR", "title": "The URL path is not valid", "detail": "The resource 'v1/buildUploads' does not exist" } ] } Is this API not yet available or am I doing something wrong? If it is not yet available, is there an ETA? Thanks in advance & best regards, Yannik

Whenever I use third-party apps on my iPhone SE 3, they don’t work properly. The apps even start crashing after using them for a while. please fix this bug in the next beta release?

Hello there! I have developed a website (https://finnia.ch). Now I have transformed it to an app (with webview). If anyone would like to check it out and test it here is the link: https://testflight.apple.com/join/hmyDw74t It is a administration tool (not a game). Simon

This is my first app subscription submission. I submitted it a week ago today and the status for the sub still says "Waiting for Review". I assume there's nothing for me to do at this point other than wait for Apple's approval. How long do these things normally take?

Hello, It has been almost a week since I submitted an appeal, but I haven’t received any response yet. Additionally, my app has been in the review queue for three days without any progress. This delay is quite frustrating. Is anyone else experiencing similar delays? Any suggestions on how to speed up the process? Thanks.

Dear Apple App Review Team, We would like to formally raise our concern regarding the prolonged delay in the review process of our game, Earth Arcade M: Torong Wanted (App Store Connect ID: [6744902975]). The delay has resulted in several critical issues that are impacting both our users and our business: Due to the delay, a test build was unintentionally made accessible to pre-registered users, as the final release version remains unreviewed. The official version has now been waiting in the review queue for over 10 days without progress. This situation is creating a significant disparity in gameplay experience between Android and iOS users, leaving us with a deep sense of regret towards our iOS player base. As iOS users lose interest due to the absence of a proper launch, our marketing efforts are losing momentum, and the business impact on our company is growing. We kindly urge you to expedite the review and approval process of our app as soon as possible. A timely release is critical not only for user experience but also for ensuring fairness across platforms. Thank you for your attention and understanding. Sincerely,Minipact Games

Hello, I’m building a Swift-based SDK (using SwiftUI) that will be distributed as a single .xcframework, and consumed by a React Native application. The SDK has multiple internal module dependencies (e.g., Essentials, CoreModels, CoreRepository), each of which is currently implemented as a local Swift Package (SPM). When I attempt to archive the main SDK framework using xcodebuild archive with BUILD_LIBRARY_FOR_DISTRIBUTION=YES, the archive process fails during SwiftEmitModule for these SPMs. I understand this likely relates to module stability requirements for .xcframework distribution. My key question: Is it mandatory to convert all Swift Packages (SPMs) into Xcode framework targets in order to successfully archive and bundle them into a distributable .xcframework? Or alternatively, is there a recommended approach to make Swift Packages archive-compatible for use in a compiled, closed-source SDK, without converting them into Xcode framework targets? Awaiting your guidance.

We’re seeing a strange issue with our TestFlight setup. We normally have 4 apps available in TestFlight (all of which are also live on the App Store). Today, 3 of them disappeared from TestFlight because their builds were marked as expired. I re-submitted new test flight builds, which made the apps reappear but now when trying to install ANY of our apps, we get an error saying: “The requested app is not available or doesn’t exist.” There are no issues or flags on the TestFlight pages in App Store Connect, all builds are validated, and all apps are still downloadable from the App Store without any problems. Has anyone else experienced this?

Apple just introduced a new Challenges feature in Game Center (WWDC 2025). I have Game Center enabled for my app and have working leaderboards (and achievements). Now I want to implement challenges (connected to my leaderboards). But the Game Center Challenges not showing in App Store Connect or Xcode 16.4 I have a working GameCenterResources file in Xcode and it allows me to add Achievement, Leaderboard, Leaderboard Set, but no Challenges. I'm based out of Europe. Any ideas?

Hello everyone, I’m reaching out to seek advice and support regarding a confusing issue I’m experiencing with my app’s review process. App ID: 6744330283 Here’s the situation: Versions 1.0 and 1.1 of my app were approved and successfully published on the App Store. However, updates 1.2 and 2.0 have both been rejected for Guideline 4.3 – Spam. The rejection happens extremely fast – less than 10 seconds after the app goes “In Review”, it gets rejected. There is no indication that the reviewer even launched the app. This is very frustrating because: The app has real user reviews, In-App Purchases, and active paying users. My app is 100% original – it is not a copy or template-based app. Even worse, the review process for versions 1.2 and 2.0 took over 7 days before even starting, and then they were rejected instantly, again without being opened. I’m happy to cooperate and improve my app further, but I feel like this may be a misunderstanding or a mistaken flag by an automated process. Has anyone experienced something similar? Is there any way to get a more thorough manual review or speak directly with the review team? Thanks in advance for any guidance or shared experience.

Hoping this is the right place to post. My app submission was rejected as my support url doesn't include a way to contact the developer. My previous app didn't have this problem, but the rules have changed now. Does anyone have any tips/templates that could be used to create a site that allows comms. I already own my own domain. Thanks , G

I inadvertently used the build number for the version number. How can I remove these versions/builds so that i can get back to my normal versioning scheme? I am now stuck using a version number of 110 instead of a build number of 110.

My app / subscription gets rejected with the following: Guideline 2.1 - Performance - App Completeness We have returned your in-app purchase products to you as the required binary was not submitted. When you are ready to submit the binary, please resubmit the in-app purchase products with the binary. and Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review. Once your binary has been uploaded and your first subscription has been submitted for review, additional subscriptions can be submitted from the Subscriptions section. Learn More ...ive tried all kinds. I archive a new build, upload it, update the app information top show new build so it ties in...and still nothing works. it is incredible frustrating. Can anyone help please. Ive wasted days on this