I don't know much about root issues with apps. But this question seems like it might be useful: https://developer.apple.com/forums/thread/792826 I think that the term "privileged helper" historically referred to an older way for apps to temporarily gain root privileges. Apple didn't like that and pushed people towards launch daemons. Lots more information here: https://developer.apple.com/forums/thread/708765 if one needs these LaunchDaemons to perform some actions with root privileges, what exactly would enabling the App Sandbox (com.apple.security.app-sandbox = true) on the privileged helper tool accomplish? Is there any point in confining a process with root privileges inside a container? Again, I'm not sure about anything involving root. But I have discovered certain benefits to sandboxing everything. If you have any part that requires (or typically uses) sandboxing, then all parts should be sandboxed. It greatly helps with interoperability between different apps or different components within apps. If you need to break out of the sandbox, you can do that with an unsandboxed XPCService. But you can only do this with a true XPCService. For other types of XPC communication, then you can't cross the sandbox line.

Complaining about existing apps (apparently) having some similarity to a rejected app is a common practice going back many years. It's always been a bad idea. You don't know the story behind that app. We don't know the details behind your rejection. Apple's policies have evolved over the years and it's not unusual to find older apps that have been approved under different circumstances in different times. It's rare for Apple to retroactively ban those apps. It does happen sometimes in more egregious cases. But the bar to initial approval is much lower than the bar to ban an already-approved app. Furthermore, complaining in public is a very bad idea indeed. Apple has private channels for these kinds of reports. If you push hard enough, maybe you can ruin someone else's app and livelihood. But that doesn't necessarily mean your app is going to be approved afterwards.

Their only suggested "fix" is to remove CLT. That probably won't work as these tools typically just check for the existence of the app on disk. And the proxy app is always there. It's only enabled if you have Command Line Tools or Xcode installed.

Debugging has been borderline unusable for a couple of years. It's not unusual for a delay of a 30-60 seconds when first hitting a breakpoint. You have to wait until the spinner disappears and your variables show up. Otherwise you'll lock it up. A much better strategy is printing out debugging messages. For a typical multithreaded, asynchronous app, standard breakpoints aren't practical at all. Debug messages are the only way to go. And they can even serve double-duty. Sometimes you do need the debugger. A debug print statement can be a convenient place to set your breakpoint as it won't involve any real logic. PS: Make sure to roll your own debugging system. Apple's built-in logger is awful. You have to do extra work to avoid making all of your debug data .

I am new for apple developer. created my app by python It's probably not a good idea for a new developer to attempt what is probably one of the most difficult technological achievements possible. Apple has a wealth of information on how to write apps in Swift and SwiftUI. I recommend that approach.

Kindred is a dating app built around BaZi (八字) — a 3,000-year-old Chinese metaphysical system. Unlike standard dating apps, every user gets a personalised Four Pillars (四柱命盘) chart calculated from their exact birth date and time. So dating + astrology + collection of personally identifiable information == rejection. Good to know.

There's no guarantee that any users are going to update the app. Always put any online services behind your own domain name.

Don't use the comments feature. It hides your replies. You only need a DUNS number for an organizational account. There are many step involved to setup a functional app for a business. Wait times can be measured in months, not days.

Ok, I’ll be quiet. I won't say anything again. Who knows? Maybe I'm wrong and complaining on this forum really is the only way to get a review. See https://developer.apple.com/forums/thread/843267 When logic fails, what do you do? Double-down into absurdity.

I get it but how long does it take to rereview it i just fixed it. In some cases, that never happens. Anyone who came to this forum and posted a question had the opportunity to review the questions that have already been posted - today, this week, and pretty much every month in 2026. Just look at what you've already posted, "They keep finding problems and another 3 day wait". Most of the people posting on the forums these days can't get review times measured in days. Consider yourself one of the elite few. But it appears that Apple's patience is waning. In addition to the complaints about reviews taking weeks, there are also complaints about repeated rejections, which almost always evolve into a complaint about a total termination of a developer account. There is so much data right here in the forums about how to have a poor Apple developer experience. Yet people don't read these posts as cautionary tales, they read them as a how-to manual - how to get rejected and terminated, that is.

i did review. I saw people posting tardy status and Apple looking into it. We're literally on the forum right now. If I can read it, you can too. im going off the timeline APPLE GAVE ME. Please describe the guarantee you received from Apple. I think that would hold more weight than user opinions. Yes. Opinions can, and should, be discarded. But one can't ignore the flood of identical, daily postings. Those aren't opinions, they are experiences. Not all developers have the same experience. But those who do have a poor experience post multiple, futile messages about it. Your post is relatively unusual these days. Before AI slop days, it was more common to see people complain about review delays impacting self-imposed deadlines. The answer today is the same as it was then. Plan ahead. If you need to release on or before a given day, get your app done and submitted sooner. There's an option to specify the release date or even hold for developer release. But it has to be approved first. If you're a new developer, better add extra time. Now that AI slop rules the world, add a few extra weeks. It's probably too late even to pivot to College basketball at this point. Maybe start thinking about next year.

The app review delays have been extreme since AI slop took over app development. That was several months ago. It was probably a bad idea to submit a new app 4 days before you need it available.

Has anyone else experienced this? Yes. Obviously. It's literally taken over the forums. It's gotten so bad that now people are seeing these posts as opportunities to pretend to be Apple employees to extract private information for who knows what end.

To help us prepare a clear and accurate response for the App Review team Who is "us"? Are you an Apple employee? You don't have the expected Apple logos with your post. please share a brief overview of your app, including its main purpose, key features, and the problem it is designed to solve. Yeah. Don't do that. Never share private information on the internet, especially to someone who is pretending to be an Apple employee. I genuinely don't know what information is helpful to provide here. In this case, I'll properly invoke the 1st person plural. We've seen many, many, many identical posts. They've literally taken over the forum. There's no need to supply additional information. We all know those details. All I can tell you is that continued attempts to push through an app that Apple doesn't want may lead to termination of your entire developer account. In addition to reviewing posts on these forums, review the App Store itself. If there are a few thousand identical, or even similar, apps, chances are that Apple doesn't need any new ones. You're wasting your time looking at images and shared framework code. Try to come up with a more unique and distinctive app idea.

I submitted my first app just in time for week 0 of college football. Are you sure about that? Is there something on my end I need to do differently? Maybe review current events being discussed here in this forum and elsewhere on the internet and adjust plans and expectations accordingly.