@Cam_3344 I'd keep the appeal running and add evidence to it like GetResubmit said, rather than withdraw it. A couple of things on top of that. On buying an existing app: I wouldn't. Every update is reviewed against the guidelines at the time, the same as a new app. If they think the concept is in a saturated category, an update that turns the bought app into yours would likely get the same 4.3(b), and you'd have paid for the app on top of that. On the zero usage: I think Etresoft's point explains it. For 4.3(b), a reviewer can make the call from your screenshots and description before ever reaching the main feature, which fits your logs showing a login and nothing else. So for the appeal and any resubmission later, make the difference obvious before anyone opens the app: the first two screenshots show the personalised result, the thing competitors don't do, not the home screen the first line of the description says what's different in one sentence. the top of the review notes has 3 numbered steps from login to a finished generation, with a demo account that already has credits. While the appeal runs, you can also book a 30-minute app review appointment through Meet with Apple (Tuesdays and Thursdays, over Webex). It won't change the decision or speed it up, but you can ask directly which apps or features they think yours is too close to, which is the one thing the rejections haven't told you.

Since you'd prefer to keep things in writing, I'd skip the App Review appointment, as it's a live video call. A few things you can still do while you wait: Get your screenshots and description ready for your next submission. The 4.3(a) message includes "concept", and in a crowded puzzle genre the first screenshots are often what makes a game look like the others. Make the first two show the mechanic that's actually different, not the general look. Check whether your games share an engine setup, SDK stack or internal framework. 4.3(a) also covers apps that are too similar to each other, not only to other developers' apps, so several games from one studio getting the same rejection at once can be a sign of that. When the Board replies, answer in App Store Connect with short, numbered points. Clear and specific is easier for a reviewer to act on than long paragraphs. If it helps, I'm happy to read over your appeal or replies before you send them and help make the English clear and direct. No charge, just email me at saurav@getappflight.co.

You've already ruled out the usual setup causes, so I'd focus on your question 3, since the rejection doesn't say which step failed. Make the paywall show what went wrong instead of a plain "unavailable" message. Show the RevenueCat error code (and the StoreKit error underneath it, if there is one) in small text on that screen, with a retry button. If it fails again, ask App Review for a screenshot of that screen in your reply. That tells you whether it was offerings_fetch_failed, STORE_PROBLEM, or something else. Log the same errors along with the build number and a timestamp, so you can match them to the review time. STORE_PROBLEM is RevenueCat's error for a problem on the App Store's side. You can't fix that in code, but a clear message and a retry button means the reviewer can try again instead of hitting a dead end. In your reply to App Review, list the exact steps to reach the paywall and mention the retry button. Since they reviewed on iPadOS 27.0.1 and you can only test 26.5, it's worth testing on a real iPad on 27.0.1 with a fresh sandbox account if you can get hold of one.

Two things worth ruling out, because both can make the In-App Purchases and Subscriptions section disappear from the version page: Business > Agreements, Tax and Banking. If the paid apps agreement isn't active or the tax or banking forms are still pending, the section can be hidden from the version page. That would explain why there's nowhere to attach Pro Unlock. The IAP's status. It should say "Ready to Submit." If a localisation, the review screenshot or the price is missing, it won't show up as something you can add. If both of those are fine, it's on Apple's side. A first in-app purchase can't be submitted on its own; it has to go with the app version, so you need that section to appear. Filing it in Feedback Assistant as well as Developer Support is worth doing, since it reaches the App Store Connect team rather than App Review.