Title: Stuck in a loop between Guideline 2.1 and 2.2: Reviewer refuses to play for 5 minutes. Body: I am an independent developer struggling with a repetitive rejection cycle for over a month. I need advice on how to handle a clear contradiction in the review process. The Loop:
- Initial Rejection (2.1): Reviewer said they couldn't locate the IAP.
- My Action: I added a prominent "IAP Test" button on the title screen to skip gameplay.
- Second Rejection (2.2): A different reviewer said the "IAP Test" button is a "Beta feature" and not appropriate for production.
- My Action: I removed the button and implemented a "Secret Command" (Easter Egg) that enables an "Assist Mode" (extending the timer to 5 minutes) so the reviewer can easily clear the game and reach the IAP screen in about 5-6 minutes.
- Latest Rejection (2.1): The reviewer now says: "While we appreciate you provide an instruction... we require a quicker way to access in-app purchases without spending significant time to play games."
The Current Solution: In my next submission, I am implementing a "Direct Warp" feature. Tapping the title logo 7 times will trigger a secret transition directly to the Ending Scene (IAP screen). The Contradiction & Question: Apple forbids "Test Buttons" (2.2), but now they refuse to spend even 3-5 minutes of gameplay to reach the IAP. I am forced to implement a "Warp" feature just to satisfy the reviewer's convenience. Has anyone else experienced a reviewer refusing to perform 5-6 minutes of gameplay? Is a "Secret Warp" considered a "Beta feature" under 2.2, or is it an acceptable compromise for 2.1? I want to ensure I don't get rejected for 2.2 again.
Thank you for your post. We're investigating this currently. A representative from App Review will contact you to provide further assistance. If you continue to experience issues during review, please contact us.
