4.3(a) - Design - Spam

Hello everyone,

I’m looking for advice from developers who may have faced a similar situation, as we appear to be stuck in a long-running loop of Guideline 4.3(a) rejections on iOS with no actionable feedback from App Review.

Over an extended period, our iOS app has been repeatedly rejected under Guideline 4.3(a) (“similar or repackaged”), regardless of the changes we make. The responses from App Review consistently use the same high-level language and do not indicate what specifically is considered problematic.

Some relevant context:

  • The app is built with Flutter using a single shared codebase.
  • The macOS version, built from the same codebase with the same overall structure and UI, has been approved without issues.
  • The iOS version, using that same implementation, continues to receive 4.3(a) rejections.
  • We do not use purchased templates and do not operate multiple developer accounts.
  • Like most apps, we use some third-party and open-source components where technically appropriate.

Across multiple submissions, we have tried to address the feedback as best we can by making changes to UI/UX, assets, metadata, internal structure, and overall product quality. However, App Review has not provided clarification even at a high level (for example, whether the concern is primarily related to UI/UX, code structure, metadata, user flows, or overall product framing). Requests for any directional guidance have resulted in the same generic responses, both in review replies and via support.

This leaves us making blind changes without a feedback loop. As a result, it’s difficult to understand whether the issue is realistically correctable, or whether the app is effectively blocked due to similarity clustering or other non-obvious review heuristics.

Any firsthand experiences, practical steps, or lessons learned would be extremely helpful.

4.3(a) - Design - Spam
 
 
Q