I would run a search here if I were you. I've answered the exact same line of questions several times.

a long review process with many resubmissions The word 'many' doesn't convey the exact number to others. Can repeated resubmissions / iterative changes alone be interpreted as “evasion” under 3.2(f)? It depends on what you have done, and nobody but people from Apple, Inc. knows it. You have been told that you have some questionable, overly sexual content. Suppose that that you have covered a sexually-revealing person with a see-through material. You've been warned 5 times. And each time you increase its opacity from 10% to 11%, 12%, 13%... If you do it many times without entirely getting rid of this person, I would definitely flag it for evasion.

a. Try changing CKQuerySubscription options to [.firesOnRecordCreation, .firesOnRecordUpdate] b. Try setting the shouldSendContentAvailable property of CKSubscription to true.

The issue was the feedback stayed very generic (“overtly sexual”) without pointing to specific elements They only tell you how you violate review guidelines. They won't tell you how you should make changes so that you will pass the review process. It's been like that for the past 15 years or longer. We only pay $99 annually. So it shouldn't be a surprise. If you need to find out how you should make changes, I'm afraid you need to hire a consultant.

An Apple person occasionally mentions a sit-down review session. Probably, that's what you want. I don't remember the exact session title, though.

I don't know if it's related, but my sample iOS app (iOS 18.5) doesn't receive a remote notification today in line with CKQuerySubscription, which it received yesterday.

My main concern is the lack of visibility. Since appeals to the Board do not appear in the Resolution Center UI, I have no way of knowing if my ticket is actually actively open, in a queue, or if it has been lost due to a system glitch. If you go back to the Contact Us screen, don't you see the ticket numbers for unsolved cases? This way of handling pending cases seems reasonable to me for an annual membership fee of $99.

Hello, Eskimo. I think I was reading this topic and then suddenly redirected to the Unauthorized page. There is no URL for the latter. Safari's History doesn't show the dates. So I cannot be certain although I have the creation date of the initial screenshot. After thread 820562, it's App Store Connect Screenshot Upload. That's when I came here to post this topic, I suppose.

I would set it to 17.0. Xcode is smart enough to tell you if any of the frameworks that you intend to use is not available for the current deployment version. If I'm right, the Translation framework, which I hardly use, is available from 17.4, though.

Enrolled: Monday, March 23. That's when you applied for a membership, right? You wouldn't be posting this topic if you are already enrolled in the developer program. Received the "2 business days to process" email. What have you done with it? It'll take Apple, Inc. several steps to make enrollment good. Apple, Inc. is a Certificate Authority. So they won't approve enrollment application without their identity verified, I suppose. You don't mention which membership type you are applying for. That's partly why some people ignore your cry for help.

How do you go from REST to Timer? Why are you using Timer? I would avoid using Timer unless I literally need to run an internal clock. What exactly is your definition of REST? Use of URLSession? And which framework? In case you didn't know, Timer doesn't run in background.

localization (titles and descriptions added) Localization for what!? Subscription group? Subscription plans? Perhaps, you don't have a localization insertion for the current sub group?

Has anyone experienced a situation where an app was flagged as a copycat after being live for a long time? I think I have once or twice only after forgetting to remove older versions. Also, I have read similar topics in the past two to three weeks. See what you can find with the search function if you want to know if there are other copycats out there. Is it possible that Apple updated their internal policies or comparisons, causing older apps to be re-evaluated? Anything is possible. Reviewers make a lot of mistakes. So do I, sometimes. I repeated two silly mistakes in setting the subtitle of the last submission. What would be the best way to respond in App Store Connect Resolution Center in this case? How would you quantify and measure the quality of your reply? Yet, I would make it as concise as possible to make the point so that it will be hard for them to dismiss. At last, I wouldn't take it to the Appeal Board if I were you unless you have good Plan B and C.

I am an individual developer. I submitted my first app for review on March 14, 2026. It remained without a meaningful response until March 31, 2026. During this time, I sent three expedite review requests, but none of them helped. At the same time, I submitted my second app on March 22, 2026. I also requested an expedite review for that app, but it is still in Waiting for Review as well. Because nothing moved, I withdrew the previous submission and uploaded a third build for the same app. However, the app is still stuck in review flow. I am afraid you have done everything that one should not have done. You flood them with support and expedite request tickets. Yesterday, I read a topic where one claimed that he had sent about 20 support tickets to the company. You flood them with these tickets. I opened a support ticket several weeks ago after two of my apps were ready to distribute but were automatically removed from the store for no reason. I received a reply some two weeks ago where an Apple lady said that they had been overwhelmed with the # of support tickets. I haven't received an answer as to why they were both subsequently removed. If you flood them with support tickets, we will all suffer.