Android · product flavors · Gradle
Android Gradle flavor code uniqueness
Madalas mag-ship ang Android bulk publishers ng isang repo na may dose-dosenang product flavors. Kapag `res/` assets lang ang nagbago, nakikita ng Play ang duplicate apps. Ihahambing ng apporig ang source sets at shared modules sa Gradle project na in-upload mo.
Bakit nagti-trigger ang Gradle flavors ng duplicate detection
Ang identical `main` source na may flavor-specific resources ay gumagawa ng apps na magkaiba ang itsura pero pareho ang Kotlin architecture. Sinusuri ng Play moderation ang APK structure at developer history.
I-upload ang buong multi-flavor repo o separate flavor exports – imi-map ng apporig ang overlap sa pagitan ng variants sa workspace.
Flavor audit workflow
I-upload ang Gradle project → ihambing laban sa sibling apps → i-rewrite ang shared domain modules na na-flag bilang COPY → mag-rescan bago ang Play Console upload.
Mga madalas itanong
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.