Android · product flavors · Gradle
Android Gradle flavor code uniqueness
Android bulk publishers अक्सर एक repo से दर्जनों product flavors ship करते हैं। अगर सिर्फ `res/` assets change होते हैं, Play duplicate apps देखता है। apporig uploaded Gradle project में source sets और shared modules compare करता है।
Gradle flavors duplicate detection क्यों trigger करते हैं
Flavor-specific resources के साथ identical `main` source ऐसे apps बनाता है जो different दिखते हैं लेकिन same Kotlin architecture share करते हैं। Play moderation APK structure और developer history check करता है।
Full multi-flavor repo या separate flavor exports upload करें – apporig workspace में variants के बीच overlap map करता है।
Flavor audit workflow
Gradle project upload → sibling apps के against compare → COPY flagged shared domain modules rewrite → Play Console upload से पहले rescan।
अक्सर पूछे जाने वाले प्रश्न
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.