Android · Product Flavors

Android Gradle Flavor 独特性

即将推出。批量发布者从一个仓库发布数十个 flavor。

Why Gradle flavors trigger duplicate app detection

Identical `main` source sets with flavor-specific resources produce apps that differ visually but share the same Kotlin architecture. Play Store moderation inspects APK structure and developer history.

Upload each flavor export or the full multi-flavor repo — apporig maps overlap across variants.

Flavor audit workflow

Export each flavor build → upload to workspace → compare all pairs → rewrite shared domain modules → rescan before Play Console upload.

常见问题

Why do Gradle product flavors trigger duplicate detection?

Flavors sharing identical main source sets with only resource differences produce structurally similar apps that Google Play flags as repetitive content.

How do I audit Android flavors for uniqueness?

Coming soon. Dedicated flavor/build-variant analysis is in development. Today: upload the full Gradle project or each flavor export as a separate project and compare COPY pairs in your workspace.

Does apporig analyze multi-flavor Gradle repos?

Coming soon. Per-flavor mapping is planned. Today: upload the repository as one Kotlin project — all source modules are compared against your catalog.

What Kotlin layers should differ between flavors?

Domain logic, ViewModels, repositories, and navigation flows — not just res/ assets and strings.xml.