Skip to content

feat: Add Ludashi, PUBG and AnTuTu package options#684

Closed
ribbit384 wants to merge 1 commit intoutkarshdalal:masterfrom
ribbit384:packagename
Closed

feat: Add Ludashi, PUBG and AnTuTu package options#684
ribbit384 wants to merge 1 commit intoutkarshdalal:masterfrom
ribbit384:packagename

Conversation

@ribbit384
Copy link

@ribbit384 ribbit384 commented Mar 1, 2026

Not sure how everyone feels about this. But open to not merging if it's not wanted.


Summary by cubic

Adds a "variant" flavor dimension and new product flavors so we can build package-specific APKs for Ludashi, AnTuTu, and PUBG alongside the default. The app and ubuntufs modules now share the same flavors, with applicationIds: app.gamenative (default), com.ludashi.benchmark, com.antutu.ABenchMark, and com.tencent.ig.

Written for commit 2a6807f. Summary will update on new commits.

Summary by CodeRabbit

  • Chores
    • Updated build configuration to support multiple application variants with distinct identifiers.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 1, 2026

📝 Walkthrough

Walkthrough

Two Android Gradle modules introduce a "variant" flavor dimension with four product flavors: default, ludashi, antutu, and pubg. Each flavor specifies a distinct applicationId, enabling multiple APK builds with different package identities from a single codebase.

Changes

Cohort / File(s) Summary
Gradle Build Configuration
app/build.gradle.kts, ubuntufs/build.gradle.kts
Added "variant" flavor dimension with four product flavors (default, ludashi, antutu, pubg). Each flavor assigns a distinct applicationId: default inherits from defaultConfig, ludashi uses "com.ludashi.benchmark", antutu uses "com.antutu.ABenchMark", pubg uses "com.tencent.ig".

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Four flavors bloom in Gradle's den,
Each with IDs, distinct again,
From ludashi to PUBG's call,
One variant dimension rules them all!
Multiple APKs from one codebase blend,
A rabbit's delight, code's new trend! 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'feat: Add Ludashi, PUBG and AnTuTu package options' accurately reflects the main changes, which involve adding four new product flavors (default, ludashi, antutu, pubg) with distinct application IDs across two build.gradle.kts files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
app/build.gradle.kts (1)

150-155: Avoid using default as a flavor name — it's a Kotlin reserved keyword.

Using default as an identifier in Kotlin DSL can cause parsing issues or require backticks. Consider renaming to standard, base, or original.

♻️ Suggested fix
     productFlavors {
-        create("default") {
+        create("standard") {
             dimension = "variant"
             // Inherits applicationId from defaultConfig ("app.gamenative")
             isDefault = true
         }
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@app/build.gradle.kts` around lines 150 - 155, The product flavor name
"default" is a Kotlin reserved word and can cause DSL parsing issues; update the
productFlavors.create("default") usage to a non-reserved identifier (e.g.,
"standard" or "base") and update any references to that flavor elsewhere (build
variants or signingConfigs) to match the new name; ensure the create(...) call
and any places that referenced "default" (productFlavors, buildVariant names)
are consistently renamed so the Kotlin DSL no longer requires backticks.
ubuntufs/build.gradle.kts (1)

14-21: Avoid using default as a flavor name — it's a Kotlin reserved keyword.

Using default as an identifier in Kotlin DSL can cause parsing issues or require backticks. Consider renaming to standard, base, or original.

♻️ Suggested fix
     flavorDimensions += "variant"

     productFlavors {
-        create("default") { dimension = "variant" }
+        create("standard") { dimension = "variant" }
         create("ludashi")  { dimension = "variant" }
         create("antutu")   { dimension = "variant" }
         create("pubg")     { dimension = "variant" }
     }
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@ubuntufs/build.gradle.kts` around lines 14 - 21, The product flavor name
"default" in the productFlavors block is a Kotlin reserved word and can cause
DSL parsing issues; rename the create("default") flavor to a non-reserved
identifier (e.g., "standard" or "base") inside the productFlavors block and
update any other build logic or references that rely on the "default" flavor
name (tasks, variant filters, manifest placeholders, signingConfigs, etc.) so
they use the new identifier; ensure flavorDimensions and the other create(...)
calls remain unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@app/build.gradle.kts`:
- Around line 156-167: Replace the third‑party package IDs used as applicationId
in the productFlavor blocks for "ludashi", "antutu", and "pubg" with
project-specific, non‑infringing identifiers (e.g.,
com.yourorg.projectname.variant or a clearly documented placeholder), and add a
brief comment above those create("ludashi"/"antutu"/"pubg") blocks documenting
the legitimate purpose for these flavors (if any) so maintainers can review;
ensure the unique symbols to change are the product flavor definitions
create("ludashi"), create("antutu"), and create("pubg") in the build.gradle.kts
and do not retain com.ludashi.benchmark, com.antutu.ABenchMark, or
com.tencent.ig as applicationId values.

---

Nitpick comments:
In `@app/build.gradle.kts`:
- Around line 150-155: The product flavor name "default" is a Kotlin reserved
word and can cause DSL parsing issues; update the
productFlavors.create("default") usage to a non-reserved identifier (e.g.,
"standard" or "base") and update any references to that flavor elsewhere (build
variants or signingConfigs) to match the new name; ensure the create(...) call
and any places that referenced "default" (productFlavors, buildVariant names)
are consistently renamed so the Kotlin DSL no longer requires backticks.

In `@ubuntufs/build.gradle.kts`:
- Around line 14-21: The product flavor name "default" in the productFlavors
block is a Kotlin reserved word and can cause DSL parsing issues; rename the
create("default") flavor to a non-reserved identifier (e.g., "standard" or
"base") inside the productFlavors block and update any other build logic or
references that rely on the "default" flavor name (tasks, variant filters,
manifest placeholders, signingConfigs, etc.) so they use the new identifier;
ensure flavorDimensions and the other create(...) calls remain unchanged.

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2eee5d1 and 2a6807f.

📒 Files selected for processing (2)
  • app/build.gradle.kts
  • ubuntufs/build.gradle.kts

Comment on lines +156 to +167
create("ludashi") {
dimension = "variant"
applicationId = "com.ludashi.benchmark"
}
create("antutu") {
dimension = "variant"
applicationId = "com.antutu.ABenchMark"
}
create("pubg") {
dimension = "variant"
applicationId = "com.tencent.ig"
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Using package names of third-party apps raises serious policy and legal concerns.

The applicationId values for ludashi, antutu, and pubg flavors are package names belonging to well-known third-party applications:

  • com.ludashi.benchmark — Ludashi/Master Lu benchmark
  • com.antutu.ABenchMark — AnTuTu benchmark
  • com.tencent.ig — PUBG Mobile

Building APKs that impersonate other apps' package identities:

  1. Policy risk: Violates Google Play policies and could result in account/app bans
  2. Legal risk: Potential trademark infringement with original app owners
  3. Ethical concern: Commonly used for benchmark score manipulation by device manufacturers

Given the author's note ("Not sure how everyone feels about this"), I'd strongly recommend discussing with project maintainers before merging, and documenting the intended legitimate use case if there is one.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@app/build.gradle.kts` around lines 156 - 167, Replace the third‑party package
IDs used as applicationId in the productFlavor blocks for "ludashi", "antutu",
and "pubg" with project-specific, non‑infringing identifiers (e.g.,
com.yourorg.projectname.variant or a clearly documented placeholder), and add a
brief comment above those create("ludashi"/"antutu"/"pubg") blocks documenting
the legitimate purpose for these flavors (if any) so maintainers can review;
ensure the unique symbols to change are the product flavor definitions
create("ludashi"), create("antutu"), and create("pubg") in the build.gradle.kts
and do not retain com.ludashi.benchmark, com.antutu.ABenchMark, or
com.tencent.ig as applicationId values.

@xXJSONDeruloXx
Copy link
Contributor

+1, should probably also update the gh actions as well so these are added to releases

@ribbit384 ribbit384 marked this pull request as draft March 1, 2026 22:15
@ribbit384
Copy link
Author

Forgot to mark this as draft, far from done yet.

@ribbit384
Copy link
Author

Per project lead this feature is not wanted at all. PR closed.

@ribbit384 ribbit384 closed this Mar 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants