distributing-tauri-for-android

Builds, signs, and publishes Tauri v2 applications to Google Play as AAB or APK packages.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/dt418/better-shot-x --skill distributing-tauri-for-android-dt418
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distributing-tauri-for-android
Source: https://github.com/dt418/better-shot-x/tree/main/.agents/skills/distributing-tauri-for-android
Command: npx skills add https://github.com/dt418/better-shot-x --skill distributing-tauri-for-android-dt418

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Distributing a Tauri v2 app on Android involves many error-prone steps: configuring version codes, generating signed AAB or APK artifacts, managing keystores, and navigating Google Play submission. This Skill consolidates that entire workflow into clear, actionable guidance. ## Core Features & Use Cases - Build Configuration: Set minSdkVersion and versionCode in tauri.conf.json, with automatic version code calculation from semantic versions. - Artifact Generation: Produce Play Store-ready AAB files, APKs for testing, architecture-specific builds, and split-per-ABI outputs. - Code Signing & Submission: Create release keystores, wire signing into Gradle or CI environment variables, and follow the Play Console upload checklist. - Use Case: You finished a Tauri desktop app and want to ship it on Android. Use this Skill to generate a signed AAB, configure your keystore, and walk through the Play Console submission checklist. ## Quick Start Guide me through building a signed AAB of my Tauri app and submitting it to the Google Play Store.

Frequently Asked Questions about distributing-tauri-for-android

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Tauri app for the Google Play Store?

Run tauri android build with the --aab flag to generate an Android App Bundle, which Google Play requires for new apps. The signed output is located at gen/android/app/build/outputs/bundle/universalRelease/app-universal-release.aab.

How to sign a Tauri Android app with a keystore?

Generate a keystore with keytool, then create a keystore.properties file in gen/android containing your passwords, alias, and store file path. Reference these values in a release signingConfig inside gen/android/app/build.gradle.kts.

What is the difference between AAB and APK for Tauri builds?

AAB is the format Google Play requires for new app submissions, while APK is used for direct testing or alternative distribution channels. Build AAB with --aab and APK with --apk using the tauri android build command.

How does Tauri calculate the Android versionCode?

Tauri derives versionCode from your app version using the formula major times 1000000 plus minor times 1000 plus patch, so version 1.2.3 becomes 1002003. You can override this by setting versionCode manually in tauri.conf.json.

Why does my Tauri Android build fail with a signing error?

Signing failures usually come from an incorrect storeFile path in keystore.properties. Use an absolute path or a path relative to the gen/android directory, and verify the keystore alias and passwords match.

Can I automate Tauri Android releases in CI/CD?

Tauri has no built-in release automation, but you can configure Gradle signing from environment variables like ANDROID_KEYSTORE_PATH and ANDROID_KEY_ALIAS. For uploads, use the Google Play Developer API in your pipeline.