Don’t resubmit the same build with only a general explanation. First determine whether Apple’s concern is the binary, metadata, account history, or the product concept itself. Audit the exact submitted IPA and store listing for shared frameworks, templates, assets, naming patterns, screenshots, keywords, bundle history and backend behavior. Include apps previously submitted by your account and anything produced by the same contractor. Then prepare a short differentiation matrix comparing your game’s core mechanics, progression, interface, original assets, content ownership and target audience with the titles Apple may be associating it with. Attach annotated screenshots and a brief video showing those differences in the submitted build. Ask App Review to identify whether the similarity concerns the binary, metadata or concept. An App Review Appointment can help if you bring this evidence and specific questions, but it will not replace visible differentiation. Appeal if your evidence demonstrates mistaken identity or ownership. If the core experience is genuinely too similar, make meaningful product and metadata changes before resubmitting instead of repeatedly uploading minor variations.

One important detail: Apple changed the IAP submission workflow on July 15, so the missing “In-App Purchases and Subscriptions” section on the app version page may no longer indicate a stuck IAP. Try opening Monetization → In-App Purchases, selecting the IAP, and clicking Add for Review. Add it to the existing draft submission that contains the rejected app version. Then check App Review → Draft Submissions and confirm that both the app version and the IAP are listed before submitting. Apple’s current instructions describe this workflow here: https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase/ If Add for Review is unavailable, the IAP cannot be added to the draft, or the app version cannot be selected, then your conclusion is likely correct: the submission state is stuck server-side. In that case, keep the support ticket open and send screenshots, the app version ID, IAP product ID, and draft submission ID, asking Apple to reset or unlock the submission state. I would not upload another binary solely for this issue.

arm64 itself is expected here—Apple’s documentation says it should be included for 64-bit apps and embedded bundles. I would not keep trying to remove or override it. The next step is to inspect the exported IPA from the exact submitted archive, not only the main app’s plist. Check UIRequiredDeviceCapabilities, UIDeviceFamily, MinimumOSVersion and supported architectures in every embedded extension and framework. A conflicting value in any nested bundle can produce an installation failure that App Review reports against the app generally. Also test that exact build through TestFlight on a physical compatible iPad after deleting any previous installation; a simulator install does not fully reproduce App Store installation validation. If every bundle contains only compatible values, reply without another speculative binary change. Attach the plist output for all bundles, identify the submitted build number and request the exact bundle identifier and installation error that failed on Apple’s device. Since arm64 is valid for the stated review device, the rejection may be using a generic template for a different packaging or installation problem.

This sounds primarily like an ownership and metadata-verification issue, so changing the binary is unlikely to help. Provide App Review with a compact evidence package: the Google Play listing, matching developer/company identity, package ownership, original publication date, source repository history and any trademark or business documentation. Explicitly state whether “Pet Shop Owner Simulator 3D” is your own title, a previous title, or wording that only appears in metadata. Then audit every metadata field, screenshot and icon for the exact disputed phrase. Remove unnecessary references to the Android title, but do not rename the product blindly until Apple identifies the conflicting third-party app. Ask them for the App Store URL or developer name they believe you are copying. If the ownership evidence is ignored again, file a single appeal focused on mistaken identity under 4.1(a). Disclosure: I’m affiliated with Resubmit AI; https://getresubmit.com can help turn the rejection and ownership evidence into a structured reviewer response.