Hello everyone, I’m hoping the community (and maybe someone from App Review) can point me in the right direction. I submitted my new game on 22 April 2025. The build was rejected, so I filed an appeal the same day and re‑submitted it twice after that. The appeal has shown “Waiting for Review” ever since, and I’ve never received the usual “We got your appeal” email, just the generic “We’re seeing higher volume” message. Although this is a fresh developer account, I’ve shipped 50+ apps for other organizations over the years and never ran into a delay like this, so I’m pretty sure the hold‑up isn’t about the actual build. Why it’s urgent:
Influencer promos, community streams, and some paid ads were all timed around the original launch window. After four weeks of silence people assume the game’s been cancelled, and traffic/comments are sliding fast. What I’ve tried so far: Emailed App Review → same volume auto‑reply Used the Contact Us form twice Added a short note in Resolution Center every few days If anyone from App Review sees this or if another dev has broken out of a similar appeal limbo any tip or nudge would be hugely appreciated. Thank you in advance for your time.

Hi, Since Friday 18 April 2025, around 9am, my team and I have been unable to manage one particular app in App Store Connect. Whenever we open the app’s page and try to view “General → App Information,” or when we press “Add for review” on the current iOS version, App Store Connect immediately displays “Something went wrong. Try again later.” and the content never loads. The error occurs every single time, in both Safari and Chrome on multiple Macs, while all our other apps in the same developer account behave normally. Our build and submission tooling (Fastlane) hasn’t changed for more than a year and continues to work for the rest of our apps. Every attempt to open App Information or submit the version fails. I have already opened a ticket ~1 month ago and shared all the screenshots, screen recordings and .har files but seems like really take their time to fix things. It feels like a server-side issue isolated to this single app, so any guidance or a manual unblock would be greatly appreciated.

Hello Apple dev world and teams , I am experiencing anormal Waiting for Review for our app, now for more than a week and decided to post the issue here and hopefully get help. We had successfully upgraded to organization membership and the process with Apple support was really enchanting really responsive, hoping to have the same experience with this issue for review also.

Our app's App Clip version has been published to app store, but still we can not open "Edit Advanced Experiences" page, when we click on it, we will be redirected to the homepage of connect. Did I miss some settings, or is this a bug? We can not open the single detail page of "Advanced App Clip Experiences" Diagnostic information Associated Domain

Hi everyone, I’m facing a frustrating issue with the App Store review process and wanted to know if anyone else has gone through something similar. I first submitted my app on April 15, 2025. After waiting for nearly 8–10 days with no progress, I ended up rejecting the binary myself out of frustration. I then resubmitted the app on April 24, 2025, but as of today, it’s still showing "Waiting for Review" with no updates or movement. This delay is really affecting my release schedule, and I’m not sure if there’s something wrong on my end or if this is just an unusual queue time. Has anyone else experienced this recently? Is there anything I can do to speed things up or get insight from Apple? Appreciate any help or shared experiences. Thanks

Directive 4.8 - Conception - Services de connexion L'application utilise un service de connexion tiers, mais ne semble pas offrir une option de connexion équivalente avec toutes les fonctionnalités suivantes : L'option de connexion limite la collecte de données au nom et à l'adresse e-mail de l'utilisateur. L'option de connexion permet aux utilisateurs de garder leur adresse e-mail privée de toutes les parties dans le cadre de la configuration de leur compte. L'option de connexion ne collecte pas les interactions avec l'application à des fins publicitaires sans consentement. Prochaines étapes Révisez l’application pour proposer une option de connexion équivalente qui répond à toutes les exigences ci-dessus. Si l'application inclut déjà une option de connexion qui répond à toutes les exigences ci-dessus, répondez à l'évaluation de l'application dans App Store Connect, identifiez quelle option de connexion répond à toutes les exigences et expliquez pourquoi elle répond à toutes les exigences. De plus, il serait approprié de mettre à jour les captures d'écran dans les métadonnées de l'application pour refléter avec précision l'application révisée une fois qu'un autre service de connexion aura été implémenté. Notez que la connexion avec Apple répond à toutes les exigences spécifiées dans la directive 4.8 . Comment resoudre ce probleme ??? J'ai une metode de connexion par email et mot de passe.

Our app submission has been rejected due to issues related to the following guidelines: Guideline 4.8 – Login Services Guideline 5.2.1 Legal – Intellectual Property We’ve reviewed both guidelines carefully and would appreciate any insight or advice on how best to resolve these issues. ** Guideline 4.8.0 – Login Services** Our app uses both custom and third-party login methods, with a strong focus on user privacy and minimal data collection. Here's how our system works: -Custom Login Methods: Phone + MPIN – Authenticates users via secure, encrypted APIs without collecting name or email. Phone + OTP – Only verifies the phone number; no additional data is collected. Phone + Biometric – Uses on-device biometrics strictly for authentication. No biometric data is stored or transmitted. -Third-Party Logins: We offer Google and Facebook login via Expo AuthSession. Only minimal user data (name, email, and ID) is retrieved for authentication purposes. No user data is used for analytics, advertising, or tracking without explicit user consent. All data interactions are encrypted and comply with privacy standards. We believe this implementation is in line with the intent of Guideline 4.8, and we would appreciate any specific guidance if further changes are required. Guideline 5.2.1 Legal – Intellectual Property Our app, BookMyRajshree, is developed, owned, and operated solely by Skill Lotto Solutions Private Limited. We have clarified the following: -"BookMyRajshree" is a privately owned brand under Skill Lotto Solutions Pvt. Ltd. -It is not affiliated with any government entity. -We are not using any government logos, names, or impersonating any government service. -All intellectual property rights related to this brand are held by our company. We understand there may be concern due to the term “Rajshree” being associated with some government-run lotteries. However,we have clearly stated that our app is a private platform and we do not present ourselves as a government-authorized service. We have submitted relevant documentation showing our ownership of the brand but still our app is getting rejected because of the above guideline We kindly ask for your help or any suggestions on how we can resolve these issues in compliance with the guidelines. If there's anything more specific that Apple is looking for in terms of documentation or implementation changes, we’re ready to take immediate action. Thank you in advance for your support!

My app has been under review for exactly 35 days. There are no response since the first day, it is just waiting in the In review stage. I canceled it thinking it was a bug and sent it again, but there is no progress. I have sent more than 10 tickets, but no response. I opened a topic in the forum, but there is no response eitheri this is second. There is no place I can reach or ask for help. The Apple team is working great, you are great :) They will probably reply to this post with the words "click this link to get support" and direct me to the link I have previously submitted +10 tickets and have not received a response.

Hi everyone, We’ve developed an iOS app that is working perfectly across our internal testing environments including: TestFlight iOS simulators Physical iPhones and iPads within our organization However, during App Store review, the build gets marked as incomplete, and the review team reports the following issues: Issues Reported by App Review: Login error message: "device token must be string" Sign In With Apple: Reviewers are redirected back to the login screen after authentication. No error message is shown, but the user isn't logged in. Account creation: The team is unable to create a new account using the provided credentials. Everything functions correctly in TestFlight, simulators, and local builds. The issue only seems to happen in the App Review environment, making it difficult for us to reproduce. We suspect that push notification permission might not be granted or the token is not being generated in the App Review sandbox environment — leading to a null/undefined value that breaks login. The "device token must be string" message likely appears when our backend validation expects a string, but receives a different type or undefined. Also, the Apple Sign In redirect and account creation failures may be related to Keychain, token handling, or review sandbox behaviors.

Hello Developer Community and Apple Staff, Like many others I've seen posting here recently, I'm facing persistent Guideline 4.3 Spam rejections for my puzzle games. I'm hoping for guidance as I believe I've identified and corrected the initial technical cause, but I'm still facing rejection and need help understanding why. My Situation: I develop grid-based puzzle games in Unity, often using my own well-developed reusable codebase (for GridManager, Tile logic, etc.). My last successfully approved app ("Seat Em All!") used my standard workflow: New empty Unity project + import my necessary code = No 4.3 issues. The 4.3 rejections started with my next game ("Twisty Train"). My mistake: Duplicated the entire "Seat Em All!" project folder, including all .meta files/GUIDs. I now understand this likely triggered spam flags due to identical technical IDs, despite adding new mechanics. My subsequent game ("Egg Pack") unfortunately repeated this flawed copy process from "Twisty Train" and was also rejected under 4.3. Corrective Actions Taken for Latest Submission: For my most recent submission, ("Egg Factory: Sorting Puzzle" - conceptually similar to Egg Pack but built to fix the issue), I took specific, major steps to address the technical duplication: Used a new, unique Bundle ID. Used the "GUID Fixer" tool to regenerate unique GUIDs for ALL assets within the entire project folder. Used a new app name and icon. The Current Problem: Despite these steps to eliminate technical duplication and ensure unique identifiers, "Egg Factory: Sorting Puzzle" was still rejected under Guideline 4.3 Spam. Seeking Specific Feedback & Potential Causes: I'm now trying to understand what, beyond unique technical identifiers, is causing this. I design my games ("Seat Em All!", "Twisty Train", "Egg Factory") to have distinct core mechanics and themes, even if they share my Unity codebase and a visual style. Could the automated review be detecting structural similarities in my own reusable code, even with unique GUIDs, and potentially misinterpreting it as template usage (similar to issues some devs using specific game engines have reported)? Is the consistent visual art style across different themes being flagged? Is the core puzzle/sorting loop considered too similar despite mechanical differences? Request for Call: Getting generic 4.3 feedback isn't helping me resolve this. I've seen other developers mention that a direct call with the App Review team was invaluable for clarifying complex situations like this. Would it be possible to schedule a call to discuss my case? Understanding the specific reason "Egg Factory" is still flagged, despite the technical fixes, is crucial for me to move forward correctly and ensure compliance. Any insights from the community, or specific guidance/a call from Apple Staff, would be incredibly helpful. Thank you, UtkuG

Hello, We are posting here in hopes of getting some help or advice regarding a critical situation we’re currently facing. We submitted our iOS app last month, which was developed for an international event that officially began yesterday. This app is part of a national project with high visibility, involving government officials and ministers. However, we are stuck in the "Waiting for review" status since the initial submission, in March 21 (24 days ago). Note that we already submitted a few IOS applications in the past with the same account, and we didn't have any problems. Here is a quick summary of what we tried in the store: Initial submission: March 21, 2025 Resubmission: March 25, 2025 Last submission attempt: April 8, 2025 Expedited Review Request: accepted, but the review still hasn't started We’ve contacted Apple Support multiple times through mails and phone calls, and received confirmation that our expedited review request was approved. However, no progress has been made since then, and the app remains in “Waiting for Review” status, now 1 day past the critical launch deadline. We understand that expedited reviews are not always guaranteed, but given the urgent and national importance of this project, we are doing everything we can to try and ensure the review begins as soon as possible. If anyone from the App Review team sees this post, or if any developers have experienced a similar situation and can offer advice, we would be truly grateful. Thank you in advance for your time and support.

Refer to the attached screenshots I am trying to push an update for an existing iOS app that I developed a few years ago (App ID: 1465985188) but I am getting this error: A required agreement is missing or has expired. This request requires an in-effect agreement that has not been signed or has expired. (ID: O4YFH7VPB2LECAUAVXR6G4WRFQ) (403) I checked my agreements page and there is no clear indication of any missing agreements left to sign or what not. I have tried different builds of this project to no avail. I am stuck in a rut and I have been already waiting two weeks for customer support to acknowledge my issue and get back to me. My membership is due in a couple months, and honestly, if this is not resolved by end of this month I am not gonna renew. Attaching screenshots of all the agreements, and as you can see all the agreements are signed.

This question is related to this post (of mine). It seems default build settings do not include dSYM files needed when uploading embedding app package. But now Xcode issues new warnings about this. Now the question - how do I tell Xcode to create dSYM files for me, say when I build My.Framework? I asked AI chatbot which tells me that for release build I need to : set "Debug Information Format" to DWARF set "Strip Debug Symbols During Copy" to off I have item 1 turned on (which I believe is the default). But item 2 is on, maybe that's the reason I do not have dSYM files in final built My.Framework. Should I turn "Strip Debug Symbols During Copy" off?

Hello Developers, I submitted my app Score + for review on March 15, and it has been stuck in review for over 20 days with no progress. On March 22, I contacted Apple Developer Support, and they assured me that my app would receive an expedited review, but nothing has changed in the past two weeks. After waiting 20 days, I thought there might be a technical issue preventing my app from being reviewed, so I incremented the version number and resubmitted it. However, it is still not being reviewed. I am wondering if my app is: ❌ Stuck in the queue due to a system error ❌ Blacklisted for some unknown reason ❌ Delayed due to a backlog of reviews Has anyone else experienced such a long delay? What can I do to escalate this issue further? Any advice would be greatly appreciated! Thank you! Erdinç Ayvaz

I submitted my iOS app for review with the "On Hold" status, but I uploaded the build using an older SDK version. According to the guidelines, starting April 24th, apps need to be built with the updated SDK. If my app is approved and ready for release, will I be able to release it after April 24th, even though it uses the older SDK? Also, how long can the app remain in the "On Hold" status before I need to take further action?

Hi everyone, I’m experiencing an unexpected delay in the review process for my app (RadioBar), and I’d appreciate your guidance. Here’s the timeline: March 24: Received feedback from the review team stating that identified issues could be resolved in the next update. Same day (March 24): Fixed the issues immediately and resubmitted the app. March 24–28: App remained in "In Review" status with no updates. March 28: Resubmitted the app again, assuming possible system issues. Status returned to "In Review." March 31: Requested an expedited review via the Resolution Center due to urgent bug fixes impacting users. As of April 2, the app remains stuck in "In Review" with no progress. This delay is disrupting my development schedule and affecting users awaiting critical fixes. Steps taken: Ensured compliance with all guidelines. Responded promptly to initial feedback. Submitted expedited review request. Could you kindly investigate the delay and prioritize the review? Any clarification or assistance would be greatly appreciated. Thank you for your support!

I've seen other similar posts with no clear answers and solutions. My Unity app has been rejected several times with this message: The UIRequiredDeviceCapabilities key in the Info.plist is still set up in such a way that the app will not install on the device used in review. Review device details: Device type: iPhone 13 mini OS version: iOS 18.4 Next Steps Please check the UIRequiredDeviceCapabilities key to verify that it contains only the attributes required for the app features or the attributes that must not be present on the device. Attributes specified by a dictionary should be set to true if they are required and false if they must not be present on the device. I have made sure the submitted app has only one value for UIRequiredDeviceCapabilities, arm64, which is required by Unity. Initially Metal was listed as well, but I've removed it in trying to fix this problem. Additionally, I've ran the app through TestFlight and it functions fine. I'm not sure what else to try to fix this issue, though I've seen from other posts that indicate this type of rejection could possibly be a bit of a red herring and the real issue could be something else. Any help would be appreciated

I use Expo EAS tool to submit to iOS and honestly I never had any issues before, at least on other projects. In the past few days I have been trying to submit a new build for an update of an older app but I am getting this error: A required agreement is missing or has expired. This request requires an in-effect agreement that has not been signed or has expired. (ID: O4YFH7VPB2LECAUAVXR6G4WRFQ) (403) I checked my agreements page and there is no clear indication of any missing agreements left to sign or what not. I have tried different builds of this project to no avail. I am stuck in a rut and I have been already waiting three days for customer support to acknowledge my issue and get back to me.

I don't get any idea why I am getting the following warnings when I tried to upload one of my apps:

I have an unpublished app that we use as our development environment, and we need to transfer it to another Apple Developer account. Since the app is not published, the standard App Transfer process in App Store Connect does not apply. Is there any workaround to transfer the app without creating a new developer account, changing the bundle ID, or reconfiguring all the associated certificates and provisioning profiles? We would like to avoid the need to rebuild and reconfigure everything from scratch. Any guidance on this process would be greatly appreciated!