[matheusfillipe]

The Google Play internal job fails on every push to main: Gradle stops with "property 'projectDir' doesn't have a configured value" in :app:rustBuildArm64Release.

The job runs tauri android init --ci before building. With the current Tauri CLI, init overwrites the committed buildSrc/.../BuildTask.kt with a newer template that expects a projectDir, but it keeps the committed RustPlugin.kt, which never sets one. The publish-android job builds the same committed project without init and succeeds, so this job now does the same.

flowchart LR
  A[committed gen/android] -->|before: init rewrites BuildTask.kt| B[Gradle: projectDir unset]
  A -->|now| C[tauri android build]

Loading

Summary by CodeRabbit

• Chores
  • Streamlined the Android publishing workflow by removing an initialization step and its associated environment configuration. This change affects the publishing process only; it does not change app features or behavior for end users.

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 51ee4523-bd10-4924-97d0-3bc1ff54bad1

Commits

Reviewing files that changed from the base of the PR and between 1730b35 and 38380a2.

Files selected for processing: 1

• .github/workflows/publish.yaml

Files with no reviewable changes: 1

• .github/workflows/publish.yaml

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

Walkthrough

The Google Play internal publishing job no longer runs npm run tauri android init -- --ci or sets NDK environment variables for that step.

Changes: Android publishing workflow

Layer / File(s)	Summary
Remove Android project initialization .github/workflows/publish.yaml	The job no longer runs the Android initialization command or sets NDK environment variables for it.

Priority: Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: Minimal · up to 38380

The internal publishing job can use the committed Android project without the removed initialization step. No actionable merge risk remains after normal checks.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: building the Google Play internal bundle from the committed Android project.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.

Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Preview URL: https://fix-play-internal-build.obsidianirc.pages.dev

Automated deployment preview for the PR in the Cloudflare Pages.