Google Play · rejection recovery
Google Play rejection: duplicate app code fix
Play Console rejections for repetitive content start with code, not screenshots. apporig compares Gradle projects in your workspace and flags Kotlin/Java overlap before you resubmit.
Why Google Play flags duplicate Android apps
Repetitive content rules hit developers who publish many similar apps to game search rankings. Shared Gradle modules, identical Activity flows, and reused ViewModels are common triggers.
apporig ingests Android Studio projects via ZIP or Git and compares every module against your existing Play catalog.
After a duplicate rejection
Analyze the rejected source plus sibling apps, rewrite COPY-flagged Kotlin layers, verify RELATED modules with QA, then resubmit with a short note on structural changes.
FAQ
Can apporig help after a Google Play duplicate rejection?
Yes. Compare the rejected Android project against your catalog, rewrite COPY Kotlin/Java modules, rescan, then resubmit.
What Google Play policies relate to code similarity?
Repetitive content and spam policies target catalogs of similar apps. Shared Gradle modules and identical Activity flows are frequent triggers.
How do I document differentiation for Google Play appeal?
Export apporig reports showing lower overlap after rewrites and attach them to your Play Console appeal or resubmission notes.
Does apporig analyze Kotlin and Java together?
Yes. Kotlin and Java are parsed with dedicated AST pipelines. Mixed Android repos fingerprint both languages.