One thing that may help frame the appeal: "Section 3.2" in these notices refers to the Apple Developer Program License Agreement (usually 3.2(f), dishonest or fraudulent acts), and 5.6 is the Developer Code of Conduct. So Apple sees this as an account-conduct issue rather than a functionality bug, which is why it was a removal rather than a normal rejection, and why the technical fix on its own probably won't reverse it. What tends to help an appeal like this: Look for anything that could look like manipulation from Apple's side: incentivised or bulk reviews, paid install campaigns or a promo vendor, a review-prompt or rewards SDK, an ad network with suspicious traffic, unusual refund patterns, or a link to another account (shared Mac, team member, payment details). In the appeal, say what you checked, what you removed or changed and when, and attach evidence (vendor invoices, analytics showing organic installs). Keep the technical fix as a separate, short point at the end, not the main argument. While the appeal is pending, don't upload new builds or set up a new account to republish. Apple tends to treat that as evasion, and it can make things worse.

Taking your questions in order: Separate step? Usually yes, in two parts. A removal through App Store Notices is lifted on Apple's legal side, not by App Review, so the "removed from sale" banner stays until App Store Notices closes it internally. That's normally a separate action from them confirming the dispute is resolved. Also open Pricing and Availability in App Store Connect and check that your countries/regions are still selected. After a removal they are sometimes cleared, and the app stays off sale even once the hold is lifted. Is the removal blocking 1.0.5? Quite possibly. An app with an open removal flag often sits in Waiting for Review until the flag is cleared. Don't cancel and resubmit, as that only resets your place in the queue. Better channel: besides replying in the App Store Notices thread with APP265997, open a case via developer.apple.com/contact → App Store Connect / "Removal of app". Ask specifically for the removed-from-sale status to be lifted following the other party's Oct 5 confirmation, and attach that confirmation. Once the banner is gone, you can also request an expedited review for 1.0.5.

A 4.1(a) finding on your own brand usually means the reviewer can't connect the App Store account to the "Erendor Online" name. Play Console screenshots don't prove that to Apple, because Google accounts aren't something they can verify. What tends to work: Proof Apple can check: a trademark registration or filing in the account holder's name, and/or an official website on a domain you control. The site should name the developer exactly as it appears on the App Store and link to both store listings. Upload that proof as an attachment in your App Store Connect reply (and in the App Review Board appeal), not only as text. Keep the message short: who you are, the proof, and one line confirming no other developer is involved. Since the metadata didn't change, look at what's new inside 1.1.27 compared with 1.1.24: new art or logos, a link to a fan wiki or Discord, server or community names. One of those is often what the reviewer matched against "third-party content". On the Extended Review flag: there's no way to request its removal directly. It usually drops off after a clean approval, so it's worth getting the ownership proof right before the next resubmission rather than resubmitting repeatedly.

Hi Maryyam, you're on solid ground. Guideline 3.1.3(e) (Goods and Services Outside of the App) says that when people pay for physical goods or services used outside the app, you must use a payment method other than In-App Purchase. Yard work and moving help fall under that rule. Reviewers usually flag this because of the word "credits": prepaid credits look like an in-app currency, which falls under 3.1.1. What usually clears it: Stop selling credit packs. Charge per task ("Pay $40 for this job") and tie each payment to a specific booking. In the app, the listing and the screenshots, swap "credits" for "booking payment" or "task payment". In your App Store Connect reply, quote 3.1.3(e) word for word. Add a 3-step path the reviewer can follow (post a task, accept a helper, pay for that task) and state that nothing digital is unlocked. If a stored balance is still needed (for example for refunds), make it refund-to-card only, with no other use in the app. The appeal and your reply run separately. Once you change the build or the wording, resubmit rather than waiting on the appeal.