Our app had been stuck since October 8th, and it finally got approved yesterday! I got lucky when I noticed that phone support was available while checking my app status in App Store Connect. I immediately requested a callback. It literally took two hours for someone from the App Review support team to call me back, but I had already made up my mind that even if it took 10 hours, I was going to wait. The representative who called me was incredibly helpful, understanding, and professional. She genuinely went above and beyond to help. She assured me that if my app's status didn't change during the review process within 24–48 hours, I could email her directly for further assistance. Before we even ended the call, I received an email notifying me that my app status had changed to "In Review." Then, just two hours later, I received another email: Congratulations! Your app has been approved. My advice to everyone going through a similar situation: Keep checking for phone support availability in App Store Connect. If the option becomes available, request a callback. And most importantly, BE RESPECTFUL. Don't yell at the support representatives. I did express my frustration and explained how stressful the situation had been, but I did it respectfully. In fact, the representative told me I was the only person who hadn't yelled at her. Remember, these people are also doing their jobs and trying to help. Be professional, communicate your concerns clearly, express your frustration when necessary, but also show appreciation for their efforts. Sometimes, a respectful conversation can go a long way. That's my personal experience, and I hope it helps someone who's currently stuck in the App Review process. Don't lose hope!

Our app was stuck since October 8th, but it finally got approved yesterday! While checking App Store Connect, I noticed phone support was available and immediately requested a callback. It took literally 2 hours, but I was determined to wait, even if it took 10. The support representative was incredibly helpful and understanding. She assured me that if my status didn't change within 24–48 hours, I could email her directly. Before we even ended the call, my status changed to "In Review." Just 2 hours later, I received the approval email! My advice: Keep checking for phone support availability and request a callback when you see it. Most importantly, be respectful. I expressed my frustration, but never yelled or disrespected anyone. The representative even mentioned I was the only person who hadn't yelled at her. Be professional, explain your concerns, and appreciate the people trying to help. Sometimes, a respectful conversation goes a long way! That's my experience. Don't lose hope!

That’s not true. Our client’s app is completely free, and we submitted it on the 8th. Since then, it has remained stuck in “Waiting for Review,” with no direct or indirect response from Apple. We’ve sent multiple emails, spoken with different representatives, and even had our expedited review request accepted, yet we’re still waiting with no progress. We check the status every day, hoping for an update. It’s incredibly frustrating, especially as paid members who expect at least some level of communication and support. Unfortunately, the ball is entirely in Apple’s court, and there’s very little we can do except wait. I genuinely hope someone from the App Review team sees this, steps in to help shake things up, and gets this submission moving. The prolonged delay and complete lack of communication are disappointing, to say the least.

We are in the same boat. We submitted our app on the 8th and have yet to receive any updates. I’ve been following up with the support team almost daily on the phone, but their visibility into the review process is limited, so they haven’t been able to provide any meaningful updates. Unfortunately, the review team, which is the only team that can provide further clarification, has remained silent. I’ve also sent multiple emails requesting an expedited review. Last Friday, the support team confirmed that the request had been accepted, but since then, there have been no further updates or signs of progress. I initially expressed my frustration in my post, but after giving it some thought, I realized that a more constructive approach would be more productive. We’re all facing the same uncertainty, and I believe sharing our experiences and supporting one another is more helpful than dwelling on our frustration. I understand how frustrating this situation can be, especially when there’s no clear timeline or communication. However, repeatedly expressing our frustration is unlikely to speed up the process. At this stage, we’ve done what we can, and the next step is up to Apple‘s developers reviewing team. Hopefully, they will provide an update soon and move things forward. In the meantime, let’s remain patient, keep each other informed, and hope for some positive news for everyone waiting. Wishing us all a successful review and approval soon Amen!

I appreciate the detailed breakdown and the candor. At the core, I completely agree with your primary thesis waiting for Apple to change or relying on public feedback to alter platform policy is a losing strategy. If a business depends on absolute platform predictability to survive, it's built on fragile ground. Where our perspectives naturally differ is on the utility of community spaces. I view open discussion not as an attempt to hold Apple accountable but as a practical form of risk intelligence a way for developers to map out systemic friction together so others can adapt faster. You see that same discourse as a distraction from execution. Ultimately, we both end up at the same practical destination focusing on what we can control, hardening our businesses against volatility, and executing within the reality we're given. Thanks for the sharp debate thou it's a good reminder that self-reliance is the only constant we can count on.

I agree that developers must take responsibility for their businesses, understand the market, and recognize that Apple ultimately operates in its own commercial interests. I also agree that fraud and low-quality AI-generated content are legitimate challenges that need to be addressed. However, these issues don't negate the importance of transparency and accountability. Addressing fraud and maintaining clear communication with legitimate developers are not mutually exclusive. Developers aren't asking Apple to guarantee their success or surrender control of its platform. They're asking for enough clarity and consistency to make informed business decisions, particularly when platform changes affect products they've invested significant time, effort, and resources in building. I also don't think raising concerns should automatically be dismissed as complaining. Understanding the market means understanding the risks associated with the platforms on which a business depends. Constructive feedback is one way to address those risks and encourage meaningful improvements. Community forums exist for exactly this reason: to give people a space to share their experiences, express their frustrations and concerns, learn from one another, and offer encouragement. Not every post needs to be a solution or a success story. Sometimes, simply sharing an experience helps others realize they're not alone, brings attention to a common problem, or encourages a meaningful discussion. Dismissing these conversations as mere complaining overlooks the value that community forums provide. Ultimately, Apple has the right to make its own decisions, and developers have the right to question those decisions, share their experiences, and explain the consequences they face. The goal isn't to change Apple's business model or demand special treatment. It's to encourage a more transparent and predictable ecosystem that benefits both Apple and the developers who contribute to it. Holding a platform accountable and encouraging constructive dialogue aren't signs of entitlement; they're part of building a healthier developer community.

I’m not arguing that dependence automatically entitles anyone to respect. I’m arguing that when a platform benefits from developers building on it, there’s a reasonable expectation of accountability, transparency, and consideration for the people who help create that value. And no, the solution doesn’t have to be seizing the means of production. It starts with clear communication, predictable policies, meaningful support, and a willingness to acknowledge the impact of platform decisions on the people who rely on them. As for the plan, that’s exactly the point: developers shouldn’t have to demand basic transparency every time something changes. If a company wants people to build their businesses around its ecosystem, it should take that responsibility seriously.

Ours has been stuck in “Waiting for Review” since October 8, with absolutely no updates. I’ve spoken with multiple representatives, opened several tickets, sent countless emails, and still haven’t received a single response. It’s incredibly frustrating. Honestly, this shows capitalism at its peak. A company with a $5 trillion market cap, yet the developers who help build and sustain its ecosystem are left completely in the dark. Developer phone support has been discontinued, emails go unanswered, and even expedite requests are being ignored. Developers are an essential part of the ecosystem, not an afterthought. The least they deserve is transparency, timely communication, and a support system that actually works. It’s disappointing to see a company of this scale show so little accountability toward the developers who invest their time and effort into its platform.