Resolve TestFlight Compliance Rejection

My MMORPG game has just been rejected in Apple TestFlight for violating Guideline 4.3(a) – Design – Spam. I need someone who can move quickly to identify exactly what is triggering the “spam” flag, guide us for clean it up, and resubmit a fully compliant build.

Here is what I know so far:
• The rejection cites “Compliance issues” only, with no crash or UI remarks.
• Apple specifically references Guideline 4.3(a), which usually points to duplicate functionality, placeholder content, excessive promotional material, or other elements Apple classifies as low-value or repetitive.
• The core of the app is a playable MMORPG; no gambling, no mature content, and no third-party IP conflicts.

The task in plain terms:
1. Review the current Xcode/Unity project (source will be shared through share screen).
2. Pinpoint every element Apple might classify as “spam”—duplicate menus, placeholder graphics, repetitive review-begging pop-ups, etc.—and propose lean alternatives.
3. Recommend the fixes, making sure they do not break gameplay or existing Game Center, Push Notification, or In-App Purchase hooks.
4. Update metadata (screenshots, description, keywords) in App Store Connect so it accurately reflects the cleaned-up build.
5. Produce a concise changelog explaining the compliance corrections so I can reference it if Apple asks for clarification.

Acceptance criteria:
• The new build is submitted to TestFlight without triggering Guideline 4.3(a) in Apple’s initial review.
• A short report outlines every code, asset, or metadata change directly tied to the rejection.
• No new warnings appear in App Store Connect when the binary is uploaded via Transporter.
• Apple approval for TestFlight

You’ll have access to the entire repo, App Store Connect, and any previous rejection correspondence. If you’re fluent in Apple’s Human Interface Guidelines, Xcode 15, and TestFlight review nuances, you should find this straightforward. Let’s get my game back in the hands of beta testers ASAP.

We are also OK to use a different Developer account for publishing on TestFlight as long as this Developer account can be transferred to us at the later stage.