The hierarchy can potentially contain a large number of layers, with animations being created/configured for those layers as well. What is "large"? What happens if you do it all on the main thread? Do you notice any hitches? Does instruments pick up any problem? If not, then there's no problem. If there is a problem, this seems like a great opportunity to use Task yield to do everything on the main thread.

I want to clarify that my app is not a dating or spam app. It is a football/soccer game booking platform that has been established and operating long before the current AI era. Yes. I get it. I looked you up. I wouldn't have given you that reply if I thought you were just another dating app. But I don't work for Apple and I'm not on the clock. To be honest, a quick, superficial review of your app marketing did initially give me a little bit of a "meeting people" dating app vibe. Maybe now that dating apps are such the "go to" fraud app, you might need some adjustment there. I understand this is a challenge. But I think that established developers are often focused on their own app and don't see the scale of global fraud. That's Apple's primary focus. There are legitimate dating apps. But most new dating apps are likely fronts for less legitimate activities. The same process has happened in many different types of apps. The launch is scheduled for September 1 I'm sorry, but Apple isn't on deadline. Apple imposes its schedule on us developers, not the other way around.

Even getting this request understood and processed took approximately 1.5–2 weeks. That sounds about right. I recently changed my address and that was a far more difficult challenge than I had anticipated. It took about two weeks to get that resolved. The final address still isn't right, but it's close enough. I'm not going to fight over one comma. And this happened before AI slop hit. We have also involved experienced developers who have previously worked with Apple Developer accounts at established international companies, and this situation is highly unusual compared with their previous experience. But you just said that you were a new company, not an established international company. When I first setup my account back in 2015, it took Apple 4 months to fill out a single page form for Canada Revenue Agency. I can't imagine anything would be easier or faster today with the App Store several times larger, with so much more global fraud, and now AI slop. I am not looking for preferential treatment. I am simply asking Apple to investigate why an application that has already been accepted cannot proceed through the enrollment process, and to provide a clear explanation and resolution. It certainly sounds like Apple was doing that. But then you cancelled the entire process and started over. How do you know they weren't doing a lot of work trying to figure it out only to see you cancel the process? And now you're asking them to do it all over again. You also haven't said what "the technical issue" is. I don't want you to post details. There's probably a good reason you didn't explain it at first. But I have to be honest with you. I do regularly see people post these kinds of queries here in the forums, omitting some important detail, and then later follow up with the missing information. In every case, that one detail makes me think, "Oh yeah, that's really suspicious". Please treat this as a formal complaint and escalation request and provide me with a reference/case number for this complaint. This is the developer forum. The original idea was to be a place where developers could ask technical, coding-level questions. That's now really rare. Virtually all questions are now app review or enrolment questions that are impossible to answer. I sincerely hope this matter can now be escalated to someone who has the authority and technical access necessary to investigate and resolve it ASAP. That would be Developer Support. I recognize that it's now standard practice to also ask here. I don't know if it helps. Good luck!

Has anyone experienced this with Romanian (+40) numbers or prepaid SIM cards? Does that mean you are also using a prepaid SIM card? When it comes to Apple's professional infrastructure usage, such as credit card payments and phone verifications, it strongly appears that Apple doesn't have good reach into down-market services. This is probably by design to help limit fraud. Using a pre-paid SIM seems to go against the intent of the DSA, doesn't it? Apple is a California company so app developers are expected to play by California rules. You'll need to use the biggest companies, with the most expensive services you can find. Those payments and phone calls stand a better chance of going through.

our app uses certificate pinning, and any TLS-inspecting VPN kills every request at the client Does it need to do that? That is a real bug and we fixed it THE SAME DAY The speed that you fix bugs has no bearing on app review timelines. Furthermore, even if you did display an appropriate message, that doesn't necessarily mean Apple will accept it. For example, if your app isn't directly involved in some highly-secure, regulated industry, this could be seen as an attempt to evade app review. there is no human being you can talk to While Apple does now use AI for app reviews, there is always a human in the loop. You can reply to rejections and a human will see it. No guarantees about that human's workload and willingness to reply. costs a reviewer two minutes and would have saved BOTH of us a week Apple incurs no cost for app review delays. This would cost the reviewer two minutes. But it wouldn't necessarily save you a week. It definitely wouldn't save Apple any time. Apple operates at scale. They review over 9 million submissions a year. That's 25,000 a day. Two minutes matters at that scale. So why should Apple spend any extra time on your app when there are so many other submissions that they might be able to review and approve while your next submission is sitting in the queue? Android: same build, submitted today, live within hours. No drama, no mystery, actual release notes. The contrast does itself. So why not abandon Apple and focus on Android? You and I both know the reason. That's the same reason for all the delays. Apple doesn't have any deadline.

Don't use the comments. They hide your reply. Nothing in my reply should be considered "confirmation". I'm not an Apple employee. I'm just guessing based on the hundreds (thousands?) of virtually identical posts here in the forums. It doesn't take a genius to deduce that Apple is really bad at search. I have zero knowledge of any relevant details. It could easily be something else. But it probably isn't.

Any idea or help references ? Did you successfully complete the identify verification procedures? Is there anything unusual about your application? For example, I noticed a space before your question mark. That indicates that you probably aren't in the US. That may be enough to cause a delay.

Were there any changes in macOS 26.6.x around securityd, Keychain ACL handling, or legacy SecKeychain* APIs that could explain this? Anything involving security should be assumed to be constantly in flux. Our code uses some legacy SecKeychain* APIs, so we are currently investigating whether this is related. That sounds logical.

That's common. Many people complain about that. But with over two million apps, searching is going to be a challenge. Being available only in the US may also negatively impact your search results. To be honest, search was never one of Apple's strengths. I don't think it's a good idea to rely solely on the App Store for discovery.

Something broke around the 8 August maintenance and a lot of us have been stuck since. The forums were taken over by these posts many months before that, in early 2026.

Does it matter? Screenshots are automated. If the system isn't happy with your screenshot dimension, it will automatically reject it. Just try a different screenshot. Ideally, you want to pick Apple's latest flagship product.

I am not being found under any search terms. That's common. Many people complain about that. But with over two million apps, searching is going to be a challenge. the only way my app can be found is by typing the name in exactly as it’s spelled You are doing better than many other apps then. Any help or suggestions would be greatly appreciated. To be honest, search was never one of Apple's strengths. I don't think it's a good idea to rely solely on the App Store for discovery. I also don't recommend purchasing any ads. They don't work like many developers think they do. In my opinion, they only serve to establish a sense of "presence", "size", or market dominance for an app. So therefore, they're only going to be effective with you literally paint the internet with ads. There are many examples of successful ad campaigns using this strategy. Unless you are willing to spend a very large amount of ad money, you will need to try a more organic method. Beware of internet scams in this domain. Apple knows about those and will reject your app and terminate your developer account if they find that kind of activity.

Is there anything I can do to get the current submission reviewed, given that the previous submission was rejected and the appeal has not received a response? The last resort action seems to be posting in the developer forums, and you've done that. Could the previous Guideline 1.1 rejection be causing the subsequent submissions to remain pending? I suppose anything is possible. Apple has publicly acknowledged using AI for app reviews now. Nobody ever knew Apple's internal App Review processes in the first place, and now there's an AI component too. Should I continue waiting for the current submission, or is there another recommended process for escalating this situation? That would be my recommendation. You are still well in the "days" range of waiting. While I do often see people who still complain about wait times measured in hours, there are many people who are experiencing wait times measured in weeks. Guideline 1.1 - Safety - Objectionable Content The app’s marketing includes terms or images that reference objectionable content or services. These references can be found in the app’s metadata, including, but not limited to, the following metadata field(s): description and name. I’m not sure what triggered this rejection because the app name and description have not been changed for years. The app has been live and regularly reviewed during that time without this issue. That's a serious category and atypical of the 4.3 spam rejections that people more commonly complain about here in the forums. I don't know what changes you made to the description and name. But it seems pretty obvious what caused it. While your app may not be changing, the rest of the world is rapidly changing. Judging from the many complaints I see here in the forums, spam dating apps are extremely common and Apple is getting very good at detecting them. My guess is the AI has been trained to detect dating apps from all this new data. Then your older app partially tripped that. You didn't match spam so the rejection is based on safety. Hopefully your change to the description, and appeal submission will be enough to get the update approved. Good luck!

You don't need an active account to start developing. You can download Xcode for free from the Mac App Store. You may be able to download the official released (non-beta) version from the Developer site too. (Always download from the Developer site if you can). Otherwise, I'm afraid you'll have to contact Apple Developer support for the double payment. There seems to be some kind of identification requirement too, which may have to be done through the iOS app. You didn't mention that, so perhaps you haven't done that yet. I'm afraid that from the many identical reports here in the forums, it will take several weeks at least to get this sorted out.

Hello Apple Developer Relations / App Review Team, This is the Apple developer forum. While there are a handful of Apple engineers who post, they usually only post replies for technical questions. Replies for App Review questions are almost unheard of. When they do occur, they are always just a generic post saying the issue has been resolved. Our app has been in the review/resubmission process since July 7, 2026, and today is August 30, 2026. We have now been waiting for almost two months overall. "overall" doesn't count. Each submission is a unique event with its own timeline. However, the delays we have experienced are far beyond the normal review timeframe What you are describing is typical for reports here in the forum. Obviously people who get 48 hour turnaround times aren't complaining. At this point, our main concern is no longer the review outcome itself, but the unusually long amount of time between each review cycle. Your concerns may be misplaced. We would sincerely appreciate it if someone from the App Review team could check the status of this app and, if possible, help get the latest submission reviewed as soon as possible. While it's clear to see that App Review generally doesn't comment on such requests here in the forums, there is no way to tell if these posts are read or if they follow up with private replies. So maybe it's possible?