Android · product flavors · Gradle
Android Gradle flavor code uniqueness
Android bulk publishers often ship one repo with dozens of product flavors. If only `res/` assets change, Play sees duplicate apps. apporig compares source sets and shared modules across the Gradle project you upload.
Why Gradle flavors trigger duplicate detection
Identical `main` source with flavor-specific resources produces apps that look different but share the same Kotlin architecture. Play moderation checks APK structure and developer history.
Upload the full multi-flavor repo or separate flavor exports – apporig maps overlap across variants in your workspace.
Flavor audit workflow
Upload the Gradle project → compare against sibling apps → rewrite shared domain modules flagged as COPY → rescan before Play Console upload.
FAQ
Why do Gradle product flavors trigger duplicate detection?
Flavors that share the same main source set and differ only in resources produce structurally similar apps Google Play treats as repetitive content.
How do I audit Android flavors for uniqueness?
Upload the full Gradle repo or separate flavor exports as projects in one workspace, then review COPY pairs against sibling apps.
Does apporig analyze multi-flavor Gradle repos?
Yes. Upload the repository as a Kotlin/Java project – shared and flavor-specific source modules are compared against your catalog.
What Kotlin layers should differ between flavors?
Domain logic, ViewModels, repositories, and navigation – not just res/ assets and strings.xml.