Post

Replies

Boosts

Views

Activity

Comment on 3.2(f) triggered — account pending termination despite repeated attempts to comply
I get that they won’t provide step-by-step instructions, but pointing out specific elements that are considered non-compliant would benefit both sides. When the feedback is just “overtly sexual,” it’s hard to know what that actually refers to, whether it’s the imagery, VO, copy, or even the character relationships. Since only Apple knows where they draw that line, having more specific guidance would significantly reduce the number of resubmissions and make the process more efficient for all.
3w
Comment on 3.2(f) triggered — account pending termination despite repeated attempts to comply
Thanks, was around 15 submissions over a few months I get your example, but I think my situation’s a bit different. 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. By the end, I submitted a build with everything unlocked and included screenshots upfront, so review had full visibility, trying to interpret vague feedback and get the app into a compliant state.
3w
Comment on 3.2(f) triggered — account pending termination despite repeated attempts to comply
I think it's past that point my account is pending termination unfortunately
Replies
Boosts
Views
Activity
3w
Comment on 3.2(f) triggered — account pending termination despite repeated attempts to comply
I get that they won’t provide step-by-step instructions, but pointing out specific elements that are considered non-compliant would benefit both sides. When the feedback is just “overtly sexual,” it’s hard to know what that actually refers to, whether it’s the imagery, VO, copy, or even the character relationships. Since only Apple knows where they draw that line, having more specific guidance would significantly reduce the number of resubmissions and make the process more efficient for all.
Replies
Boosts
Views
Activity
3w
Comment on 3.2(f) triggered — account pending termination despite repeated attempts to comply
Thanks, was around 15 submissions over a few months I get your example, but I think my situation’s a bit different. 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. By the end, I submitted a build with everything unlocked and included screenshots upfront, so review had full visibility, trying to interpret vague feedback and get the app into a compliant state.
Replies
Boosts
Views
Activity
3w