Thanks for the response, for context it was around 15 submissions over a few months and 30ish messages.
I get your example, but I think my situation’s a bit different. The updates weren’t just micro changes trying to slip something through, there was a mix of both small tweaks and broader changes. The issue was the feedback stayed very generic (“overtly sexual”) without pointing to specific elements, so each update was essentially a best guess at what might be triggering it. Especially early on, when only metadata was flagged, I assumed the issue was relatively minor.
By the end, I actually went in the opposite direction of evasion & submitted a build with everything unlocked and included screenshots showing all content upfront, so review had full visibility, as requested during a phone call. It’s possible I missed a couple of screenshots in earlier messages, but nothing was intentional.
That’s why the 3.2(f) decision caught me off guard, there was no intent to hide or mislead, just trying to interpret vague feedback and get the app into a compliant state.
I also had a call with a policy expert hoping to get more specific guidance, but the feedback remained high-level (“a bit too inappropriate for the App Store”) without pointing to any specific elements.
I made further changes after that call based on my interpretation, so receiving another generic response afterwards was disappointing. The fact I actively sought clarification and continued updating the app shows I wasn’t trying to evade anything, I was trying to understand the requirements and bring it into compliance.
I also have a full history of communication and development changes (including work with a programmer) that reflect genuine attempts to comply, although I wasn’t able to include supporting materials in the appeal.