Guideline 4.2 says the following. If your app is not particularly useful, unique, or “app-like,” it doesn’t belong on the App Store. You should have spent the last two weeks enhancing the fictionality of your app with unique features that you don't see with other apps. The appeal board often sides with reviewers. Additionally, there is no promise as to when they take your case. So you should have had Plan B and Plan C before taking your case to the appeal board.

After a user successfully completes a purchase and later requests a refund, how long does it typically take for the refund to be processed and take effect? What does the App Store app tell you about requesting a refund? In cases where users may abuse the refund system (e.g., frequent or malicious refund requests), is there any way for developers to prevent or intervene in the refund process? There are cheaters wherever you go. It's not just app users. There are software developers who abuse the system with fake 5-star ratings and bogus last-minute discount price claims. You are simply better off staying away from these people and concentrating on development instead. I wouldn't waste a minute of my valuable time becoming a cat to chase mice.

Each review is a drip feed of one or two problems rather than a full review of all problems in one go - surely this has a cost associated which Apple is bearing unnecesarily? In the last week, all rejection reasons could have been stated months ago. That's because those issues have not been resolved? I don't understand why I should be asked if people will be interacting in my community forum - thats the entire point of a forum. Search the guideline for 'moderate.' 2.The chatbots are on the dashboard of my app, there is only one dashboard in my app, everything on my app is in one place, so the reviewer didn't even look for the feature. It's not they who have developed your app. I don't know what the chatbots are, either. The dashboard? I have no clue. I would use the language that your grandparent could understand if I were you. I often given them a video tutorial with subtitles.

metadata, screenshot, and localizations have been filled The localization for what? It seems quite obvious to me what the immediate issue is. If I were you, though, I would show several screenshots to make points instead of showing a checklist in writing.

It was there a month ago. It was there a week ago. It's still there now.

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.

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.

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?

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.

Have you seen this membership page? to help yourself?

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.

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.

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.

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.

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.