Back to Details

android-playstore-setup

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Android Play Store Setup

Android Play Store 部署设置

This skill orchestrates complete Google Play Store deployment setup with automated publishing to the internal testing track using Fastlane.
本Skill可统筹完成Google Play Store自动化部署配置，通过Fastlane实现向内部测试渠道的自动发布。

What This Does

功能说明

Scope: Internal track deployment only (simplified for quick testing)
Sets up everything needed for automated Play Store deployment using Fastlane:
  1. Scan Project - Analyze project and generate setup checklist
  2. Fastlane Setup - Configure Fastlane with supply and screengrab
  3. App Icon - Generate and place icon assets
  4. Screenshots - Automated screenshot capture
  5. Store Listing - Feature graphic and metadata
  6. Privacy Policy - Generate privacy policy for GitHub Pages
  7. Version Management - Setup Git tag-based versioning
  8. Signing Configuration - Configure release signing
  9. Service Account - Play Store API access
  10. GitHub Actions - CI/CD workflows with Fastlane
适用范围： 仅支持内部测试渠道部署（为快速测试做了简化）
使用Fastlane完成Play Store自动化部署所需的全部配置：
  1. 项目扫描 - 分析项目并生成设置检查清单
  2. Fastlane配置 - 配置Fastlane的supply和screengrab组件
  3. 应用图标 - 生成并放置图标资源
  4. 截图自动化 - 自动捕获应用截图
  5. 商店列表 - 配置宣传图和元数据
  6. 隐私政策 - 生成适配GitHub Pages的隐私政策
  7. 版本管理 - 基于Git标签的版本控制设置
  8. 签名配置 - 配置发布签名信息
  9. 服务账号 - 配置Play Store API访问权限
  10. GitHub Actions - 基于Fastlane的CI/CD工作流

Prerequisites

前置条件

  • Google Play Developer account ($25 one-time)
  • Google Cloud Platform account (free)
  • Admin access to Play Console
  • Package name reserved in Play Console
  • Google Play开发者账号（一次性付费25美元）
  • Google Cloud Platform账号（免费）
  • Play Console的管理员权限
  • 已在Play Console中预留应用包名

Workflow Overview

工作流概览

1. Scan → 2. Review → 3. Setup → 4. Deploy
   ↓          ↓          ↓          ↓
  📋        ✅         🔧         🚀
1. 扫描 → 2. 审核 → 3. 配置 → 4. 部署
   ↓          ↓          ↓          ↓
  📋        ✅         🔧         🚀

Process

操作流程

Step 1: Scan Project (Analysis Only)

步骤1：项目扫描（仅分析）

Run 
/devtools:android-playstore-scan
What it does:
  • Scans AndroidManifest.xml and build.gradle
  • Detects Health Connect, ads, analytics
  • Checks for privacy policy
  • Generates 
    PLAY_CONSOLE_SETUP.md
    with pre-filled answers
Output: 
PLAY_CONSOLE_SETUP.md
Action: Review the generated file and address any warnings
运行 
/devtools:android-playstore-scan
功能：
  • 扫描AndroidManifest.xml和build.gradle文件
  • 检测Health Connect、广告、分析工具等组件
  • 检查隐私政策是否存在
  • 生成预填充答案的
    PLAY_CONSOLE_SETUP.md
    文件
输出： 
PLAY_CONSOLE_SETUP.md
操作： 查看生成的文件并处理所有警告信息

Step 2: Generate Privacy Policy (If Needed)

步骤2：生成隐私政策（如需要）

If 
PLAY_CONSOLE_SETUP.md
shows privacy policy is missing:
Run 
/devtools:privacy-policy-generate
What it does:
  • Scans project for app info
  • Detects Health Connect and third-party SDKs
  • Prompts for developer info
  • Generates 
    docs/privacy-policy.md
  • Creates GitHub Pages setup guide
Verify:
bash
test -f docs/privacy-policy.md && echo "✓ Privacy policy created"
Next: Enable GitHub Pages (Settings → Pages → Source: docs/)
如果
PLAY_CONSOLE_SETUP.md
显示缺少隐私政策：
运行 
/devtools:privacy-policy-generate
功能：
  • 扫描项目获取应用信息
  • 检测Health Connect和第三方SDK
  • 提示输入开发者信息
  • 生成
    docs/privacy-policy.md
    文件
  • 创建GitHub Pages设置指南
验证：
bash
test -f docs/privacy-policy.md && echo "✓ 隐私政策已创建"
下一步： 启用GitHub Pages（设置 → Pages → 源：docs/）

Step 3: Setup Version Management

步骤3：配置版本管理

Run 
/devtools:version-management
with platform=gradle
What it does:
  • Creates 
    scripts/version-manager.sh
    (core)
  • Creates 
    scripts/gradle-version.sh
    (Android adapter)
  • Creates 
    version.properties
    with initial version
  • Updates 
    app/build.gradle.kts
    to read from version.properties
Verify:
bash
./scripts/version-manager.sh latest
./scripts/gradle-version.sh generate patch
运行 
/devtools:version-management
并指定platform=gradle
功能：
  • 创建核心文件
    scripts/version-manager.sh
  • 创建Android适配文件
    scripts/gradle-version.sh
  • 创建初始版本文件
    version.properties
  • 更新
    app/build.gradle.kts
    以读取version.properties中的版本信息
验证：
bash
./scripts/version-manager.sh latest
./scripts/gradle-version.sh generate patch

Step 4: Generate Keystores

步骤4：生成密钥库

Run 
/devtools:android-keystore-generation
What it does:
  • Generates production-release.jks (for CI/CD)
  • Generates local-dev-release.jks (for local testing)
  • Creates KEYSTORE_INFO.txt with credentials
  • Updates .gitignore
Verify:
bash
ls keystores/*.jks
cat keystores/KEYSTORE_INFO.txt
运行 
/devtools:android-keystore-generation
功能：
  • 生成用于CI/CD的production-release.jks
  • 生成用于本地测试的local-dev-release.jks
  • 创建包含凭证信息的KEYSTORE_INFO.txt
  • 更新.gitignore文件
验证：
bash
ls keystores/*.jks
cat keystores/KEYSTORE_INFO.txt

Step 5: Configure Signing

步骤5：配置签名

Run 
/devtools:android-signing-config
What it does:
  • Adds signing configuration to app/build.gradle.kts
  • Configures dual-source credentials (env vars + gradle.properties)
  • Updates local ~/.gradle/gradle.properties
  • Adds validation for release builds
Verify:
bash
./gradlew assembleRelease
运行 
/devtools:android-signing-config
功能：
  • 向app/build.gradle.kts添加签名配置
  • 配置双源凭证（环境变量 + gradle.properties）
  • 更新本地~/.gradle/gradle.properties文件
  • 添加发布构建的验证规则
验证：
bash
./gradlew assembleRelease

Step 6: Configure ProGuard (If Not Already Setup)

步骤6：配置ProGuard（如未设置）

Run 
/devtools:android-proguard-setup
What it does:
  • Creates app/proguard-rules.pro with safe defaults
  • Enables minification and resource shrinking
  • Adds library-specific rules if needed
Verify:
bash
grep "isMinifyEnabled = true" app/build.gradle.kts
运行 
/devtools:android-proguard-setup
功能：
  • 创建包含安全默认规则的app/proguard-rules.pro
  • 启用代码混淆和资源压缩
  • 按需添加特定库的规则
验证：
bash
grep "isMinifyEnabled = true" app/build.gradle.kts

Step 7: Setup Fastlane

步骤7：配置Fastlane

Run 
/devtools:android-fastlane-setup
What it does:
  • Creates Gemfile with fastlane and screengrab
  • Creates fastlane/Appfile with package name
  • Creates fastlane/Fastfile with deployment lanes
  • Creates fastlane/Screengrabfile for screenshot automation
  • Creates fastlane/metadata/ directory structure
Verify:
bash
bundle exec fastlane --version
bundle exec fastlane lanes
运行 
/devtools:android-fastlane-setup
功能：
  • 创建包含fastlane和screengrab的Gemfile
  • 创建包含包名的fastlane/Appfile
  • 创建包含部署流程的fastlane/Fastfile
  • 创建用于截图自动化的fastlane/Screengrabfile
  • 创建fastlane/metadata/目录结构
验证：
bash
bundle exec fastlane --version
bundle exec fastlane lanes

Step 7a: Generate App Icon

步骤7a：生成应用图标

Run 
/devtools:android-app-icon
What it does:
  • Analyzes project for app name and colors
  • Generates docs/APP_ICON_SETUP.md with IconKitchen instructions
  • Provides helper script to process IconKitchen downloads
  • Copies mipmap resources and Play Store icon
Verify:
bash
test -f fastlane/metadata/android/en-US/images/icon.png
file fastlane/metadata/android/en-US/images/icon.png | grep "512 x 512"
运行 
/devtools:android-app-icon
功能：
  • 分析项目获取应用名称和配色
  • 生成包含IconKitchen操作指南的docs/APP_ICON_SETUP.md
  • 提供处理IconKitchen下载资源的辅助脚本
  • 复制mipmap资源和Play Store图标
验证：
bash
test -f fastlane/metadata/android/en-US/images/icon.png
file fastlane/metadata/android/en-US/images/icon.png | grep "512 x 512"

Step 7b: Setup Screenshot Automation

步骤7b：配置截图自动化

Run 
/devtools:android-screenshot-automation
What it does:
  • Adds screengrab dependency to app/build.gradle.kts
  • Creates debug manifest with required permissions
  • Creates ScreenshotTest.kt for automated capture
  • Creates DemoModeRule.kt for clean status bar
Verify:
bash
bundle exec fastlane screenshots
ls fastlane/metadata/android/en-US/images/phoneScreenshots/
运行 
/devtools:android-screenshot-automation
功能：
  • 向app/build.gradle.kts添加screengrab依赖
  • 创建包含必要权限的调试清单
  • 创建用于自动捕获的ScreenshotTest.kt
  • 创建用于清理状态栏的DemoModeRule.kt
验证：
bash
bundle exec fastlane screenshots
ls fastlane/metadata/android/en-US/images/phoneScreenshots/

Step 7c: Create Store Listing Assets

步骤7c：创建商店列表资源

Run 
/devtools:android-store-listing
What it does:
  • Generates docs/STORE_LISTING_GUIDE.md
  • Creates metadata templates (title, description, etc.)
  • Provides feature graphic generation script
  • Guides user through asset creation
Verify:
bash
test -f fastlane/metadata/android/en-US/images/featureGraphic.png
wc -c fastlane/metadata/android/en-US/*.txt
运行 
/devtools:android-store-listing
功能：
  • 生成docs/STORE_LISTING_GUIDE.md
  • 创建元数据模板（标题、描述等）
  • 提供宣传图生成脚本
  • 引导用户完成资源创建
验证：
bash
test -f fastlane/metadata/android/en-US/images/featureGraphic.png
wc -c fastlane/metadata/android/en-US/*.txt

Step 8: Create Deployment Workflows

步骤8：创建部署工作流

Run 
/devtools:android-workflow-internal
What it does:
  • Creates .github/workflows/build.yml (CI only - runs on push/PR)
  • Creates .github/workflows/release-internal.yml (Manual releases with Fastlane)
  • Adds Ruby setup and bundle caching
  • Uses 
    bundle exec fastlane deploy_internal
    for deployment
  • All actions pinned to SHAs
Verify:
bash
test -f .github/workflows/build.yml
test -f .github/workflows/release-internal.yml
grep "bundle exec fastlane" .github/workflows/release-internal.yml
运行 
/devtools:android-workflow-internal
功能：
  • 创建仅CI的.github/workflows/build.yml（在推送/PR时触发）
  • 创建基于Fastlane的手动发布工作流.github/workflows/release-internal.yml
  • 添加Ruby环境配置和bundle缓存
  • 使用
    bundle exec fastlane deploy_internal
    执行部署
  • 所有操作均固定到特定SHA版本
验证：
bash
test -f .github/workflows/build.yml
test -f .github/workflows/release-internal.yml
grep "bundle exec fastlane" .github/workflows/release-internal.yml

Step 9: Service Account Setup

步骤9：服务账号配置

Run 
/devtools:android-service-account-guide
What it does:
  • Provides step-by-step guide for Google Cloud setup
  • Documents service account creation
  • Creates Play Console setup documentation
Manual steps required:
  1. Create service account in Google Cloud
  2. Download JSON key
  3. Grant permissions in Play Console
  4. Add JSON to GitHub Secrets as 
    SERVICE_ACCOUNT_JSON_PLAINTEXT
运行 
/devtools:android-service-account-guide
功能：
  • 提供Google Cloud设置的分步指南
  • 记录服务账号创建流程
  • 创建Play Console设置文档
需要手动完成的步骤：
  1. 在Google Cloud中创建服务账号
  2. 下载JSON密钥
  3. 在Play Console中授予权限
  4. 将JSON添加到GitHub Secrets，命名为
    SERVICE_ACCOUNT_JSON_PLAINTEXT

Step 10: Add Keystore to GitHub Secrets

步骤10：将密钥库添加到GitHub Secrets

From 
keystores/KEYSTORE_INFO.txt
, add these secrets to GitHub:
bash
undefined
从
keystores/KEYSTORE_INFO.txt
中，将以下凭证添加到GitHub Secrets：
bash
undefined

From KEYSTORE_INFO.txt, copy the base64 encoded keystore:

从KEYSTORE_INFO.txt中复制base64编码的密钥库：

SIGNING_KEY_STORE_BASE64: <base64_string> SIGNING_KEY_ALIAS: upload SIGNING_STORE_PASSWORD: <password> SIGNING_KEY_PASSWORD: <password>

---
SIGNING_KEY_STORE_BASE64: <base64字符串> SIGNING_KEY_ALIAS: upload SIGNING_STORE_PASSWORD: <密码> SIGNING_KEY_PASSWORD: <密码>

---

Step 11: Validate API Connection

步骤11：验证API连接

Run 
/devtools:android-playstore-api-validation
What it does:
  • Creates scripts/validate-playstore.py
  • Tests Play Store API connection
  • Verifies service account permissions
Verify:
bash
python3 -m venv .venv
source .venv/bin/activate
pip install google-auth google-api-python-client
python3 scripts/validate-playstore.py /path/to/service-account.json com.example.app
运行 
/devtools:android-playstore-api-validation
功能：
  • 创建scripts/validate-playstore.py
  • 测试Play Store API连接
  • 验证服务账号权限
验证：
bash
python3 -m venv .venv
source .venv/bin/activate
pip install google-auth google-api-python-client
python3 scripts/validate-playstore.py /path/to/service-account.json com.example.app

Step 12: First Manual Upload (CRITICAL)

步骤12：首次手动上传（至关重要）

⚠️ Before GitHub Actions can deploy, you MUST manually upload your first release.
⚠️ 在GitHub Actions可以自动部署前，您必须手动完成首次发布上传。

Why?

原因：

  1. Google Play requires manual first upload to complete store listing
  2. Your production keystore becomes the upload key
  3. Play App Signing is automatically enabled
  1. Google Play要求手动完成首次上传以完善商店列表
  2. 您的生产密钥库将成为上传密钥
  3. Play应用签名将自动启用

Steps:

步骤：

bash
undefined
bash
undefined

1. Build release bundle locally

1. 本地构建发布包

./gradlew bundleRelease
./gradlew bundleRelease

2. Verify it's signed

2. 验证签名

jarsigner -verify -verbose app/build/outputs/bundle/release/app-release.aab
jarsigner -verify -verbose app/build/outputs/bundle/release/app-release.aab

3. Manual upload via Play Console

3. 通过Play Console手动上传


**In Play Console:**
1. Go to **Release** → **Internal testing**
2. Click **Create new release**
3. Upload `app-release.aab`
4. Complete store listing (title, description, icon)
5. Complete app content declarations
6. Publish to internal testing

**IMPORTANT:** The keystore used for this first upload must be the same one configured in GitHub Secrets!

---

**在Play Console中：**
1. 进入 **发布** → **内部测试**
2. 点击 **创建新版本**
3. 上传`app-release.aab`
4. 完善商店列表（标题、描述、图标）
5. 完成应用内容声明
6. 发布到内部测试渠道

**重要提示：** 首次上传使用的密钥库必须与GitHub Secrets中配置的密钥库一致！

---

Step 13: Test Fastlane Deployment

步骤13：测试Fastlane部署

After first manual upload is complete:
bash
undefined
完成首次手动上传后：
bash
undefined

Push to main branch to trigger deployment

推送到主分支触发部署

git add . git commit -m "Setup Play Store deployment" git push origin main

**What happens:**
1. GitHub Actions workflow triggers
2. Runs unit tests
3. Builds release bundle
4. Deploys to internal testing track

**Monitor:** Go to repository → Actions tab

---
git add . git commit -m "配置Play Store部署" git push origin main

**执行流程：**
1. GitHub Actions工作流触发
2. 运行单元测试
3. 构建发布包
4. 部署到内部测试渠道

**监控：** 进入仓库 → Actions标签页

---

Understanding Play App Signing

理解Play应用签名

Two Keys System

双密钥系统

Key TypePurposeHolderCan Reset?
App Signing KeySigns APKs for usersGoogleNo (permanent)
Upload KeyAuthenticates your uploadsYouYes (via Play Console)
密钥类型用途持有者可重置？
应用签名密钥为用户使用的APK签名Google否（永久）
上传密钥验证您的上传身份您是（通过Play Console）

Automatic Setup

自动配置

For apps created after August 2021, Play App Signing is automatic:
  1. First upload: Google generates app signing key
  2. Your production keystore = upload key
  3. Google re-signs with app signing key before distribution
No action needed - it just works!
对于2021年8月之后创建的应用，Play应用签名是自动启用的：
  1. 首次上传：Google生成应用签名密钥
  2. 您的生产密钥库 = 上传密钥
  3. Google在分发前会使用应用签名密钥重新签名
无需手动操作 - 自动生效！

Final Verification Checklist

最终验证清单

bash
undefined
bash
undefined

Project files

项目文件

✓ Fastlane configured (Gemfile, Fastfile, Appfile) ✓ Version management scripts in scripts/ ✓ Keystores in keystores/ (gitignored) ✓ Privacy policy in docs/privacy-policy.md ✓ Metadata in fastlane/metadata/android/en-US/ ✓ CI workflow in .github/workflows/build.yml ✓ Release workflow in .github/workflows/release-internal.yml
✓ Fastlane已配置（Gemfile、Fastfile、Appfile） ✓ 版本管理脚本位于scripts/目录 ✓ 密钥库位于keystores/目录（已加入git忽略） ✓ 隐私政策位于docs/privacy-policy.md ✓ 元数据位于fastlane/metadata/android/en-US/ ✓ CI工作流位于.github/workflows/build.yml ✓ 发布工作流位于.github/workflows/release-internal.yml

Build verification

构建验证

✓ ./gradlew assembleRelease succeeds ✓ Unit tests pass ✓ ProGuard enabled
✓ ./gradlew assembleRelease执行成功 ✓ 单元测试通过 ✓ ProGuard已启用

GitHub Secrets configured

GitHub Secrets已配置

✓ SERVICE_ACCOUNT_JSON_PLAINTEXT ✓ SIGNING_KEY_STORE_BASE64 ✓ SIGNING_KEY_ALIAS ✓ SIGNING_STORE_PASSWORD ✓ SIGNING_KEY_PASSWORD
✓ SERVICE_ACCOUNT_JSON_PLAINTEXT ✓ SIGNING_KEY_STORE_BASE64 ✓ SIGNING_KEY_ALIAS ✓ SIGNING_STORE_PASSWORD ✓ SIGNING_KEY_PASSWORD

Play Console

Play Console

✓ First manual upload completed ✓ Internal testing track active ✓ Service account has permissions
✓ 首次手动上传完成 ✓ 内部测试渠道已激活 ✓ 服务账号已获得权限

API validation

API验证

✓ scripts/validate-playstore.py passes

---
✓ scripts/validate-playstore.py执行通过

---

Next Steps

后续步骤

For Beta/Production Deployment

用于Beta/生产环境部署

Once internal testing is working:
bash
undefined
内部测试正常运行后：
bash
undefined

Add beta track

添加Beta测试渠道

/devtools:android-workflow-beta
/devtools:android-workflow-beta

Add production track

添加生产环境渠道

/devtools:android-workflow-production
undefined
/devtools:android-workflow-production
undefined

Track Information

渠道信息

TrackAudienceReview TimeUse Case
InternalUp to 100 testersInstantQuick testing, no review
Closed (Alpha)Invited testers< 24hBeta testing
Open (Beta)Anyone can join< 24hPublic beta
ProductionAll users1-7 daysFull release
渠道受众审核时间使用场景
内部测试最多100名测试人员即时快速测试，无需审核
封闭测试（Alpha）受邀测试人员< 24小时公测前测试
公开测试（Beta）任何人可加入< 24小时公开公测
生产环境所有用户1-7天正式发布

Troubleshooting

故障排除

"Package not found" in API validation

API验证时提示"Package not found"

  • Ensure app exists in Play Console
  • Verify package name matches exactly
  • Complete first manual upload
  • 确保应用已在Play Console中创建
  • 验证包名完全匹配
  • 完成首次手动上传

"Upload key mismatch"

"Upload key mismatch"

  • Your first upload keystore ≠ GitHub Secrets keystore
  • Fix: Use Play Console → App signing → Request upload key reset
  • Re-upload with correct keystore
  • 首次上传使用的密钥库 ≠ GitHub Secrets中的密钥库
  • 解决方法：通过Play Console → 应用签名 → 申请重置上传密钥
  • 使用正确的密钥库重新上传

"Permission denied" for service account

服务账号提示"Permission denied"

  • Grant "Release to production" permission in Play Console
  • Wait 5-10 minutes for permissions to propagate
  • 在Play Console中授予"发布"权限
  • 等待5-10分钟让权限生效

GitHub Actions fails to deploy

GitHub Actions部署失败

  • Verify all GitHub Secrets are set correctly
  • Check workflow logs for specific error
  • Ensure first manual upload was completed
  • 验证所有GitHub Secrets是否正确设置
  • 查看工作流日志获取具体错误信息
  • 确保已完成首次手动上传

Summary

总结

You've successfully setup:
  • ✅ Privacy policy (GitHub Pages ready)
  • ✅ Version management (Git tag-based)
  • ✅ Release signing (production + local dev)
  • ✅ Fastlane deployment automation
  • ✅ GitHub Actions CI/CD (internal track)
  • ✅ Play Store API connection
Your app is now ready for continuous integration and deployment!
Every push to main or PR → Automatic build & test (CI) ✅ Manual workflow trigger → Version management + deployment to internal track 🚀
All checks must pass before marking this skill as complete.
您已成功完成以下配置：
  • ✅ 隐私政策（适配GitHub Pages）
  • ✅ 版本管理（基于Git标签）
  • ✅ 发布签名（生产环境 + 本地开发）
  • ✅ Fastlane部署自动化
  • ✅ GitHub Actions CI/CD（内部测试渠道）
  • ✅ Play Store API连接
您的应用现已支持持续集成和部署！
每次推送到主分支或提交PR → 自动构建 & 测试（CI）✅ 手动触发工作流 → 版本管理 + 部署到内部测试渠道 🚀
必须通过所有检查后，才能标记此Skill为完成。

Completion Criteria

完成标准

Do NOT mark complete unless ALL are verified:
✅ Service Account Setup
  • Service account created in Google Cloud
  • JSON key downloaded and stored securely
  • Play Developer API enabled
  • Service account linked to Play Console
  • "Release" permission granted
✅ Store Metadata Structure
  • fastlane/metadata/android/en-US/ directory exists
  • At least en-US locale configured
  • Metadata files created (title, description, changelogs)
  • docs/PLAY_STORE_TRACKS.md documentation created
✅ API Validation
  • scripts/validate-playstore.py exists
  • Validation script runs successfully
  • API connection confirmed
  • Package access confirmed
✅ Documentation
  • PLAY_CONSOLE_SETUP.md exists (project root)
  • GITHUB_SECRETS.md exists (if needed)
除非所有项都已验证，否则不要标记为完成：
✅ 服务账号配置
  • 已在Google Cloud中创建服务账号
  • 已下载JSON密钥并安全存储
  • 已启用Play Developer API
  • 服务账号已关联到Play Console
  • 已授予"发布"权限
✅ 商店元数据结构
  • fastlane/metadata/android/en-US/目录已存在
  • 至少已配置en-US语言环境
  • 已创建元数据文件（标题、描述、更新日志）
  • 已创建docs/PLAY_STORE_TRACKS.md文档
✅ API验证
  • scripts/validate-playstore.py已存在
  • 验证脚本执行成功
  • API连接已确认
  • 包访问权限已确认
✅ 文档
  • PLAY_CONSOLE_SETUP.md已存在（项目根目录）
  • GITHUB_SECRETS.md已存在（如需要）

Summary Report

总结报告

After completion, provide this summary:
✅ Android Play Store Setup Complete!

🔐 Service Account:
  ✓ Created in Google Cloud
  ✓ JSON key downloaded
  ✓ Linked to Play Console
  ✓ Permissions granted

📝 Store Metadata:
  ✓ Structure created: fastlane/metadata/android/en-US/
  ✓ Locales configured
  ✓ Templates ready

✅ API Validation:
  ✓ Validation script created
  ✓ API connection tested
  ✓ Package access confirmed

📋 Next Steps:

  For GitHub:
    1. Add secrets (see GITHUB_SECRETS.md if it exists)
    2. Create "production" environment with reviewers

  For Deployment:
    1. Run: /devtools:android-playstore-publish
    2. Generate deployment workflows

⚠️  CRITICAL REMINDERS:
  - NEVER commit service account JSON to git
  - Store JSON key in password manager
  - Add all 5 secrets to GitHub before deploying
  - Wait 5-10 minutes after granting permissions
完成后，请提供以下总结：
✅ Android Play Store配置完成！

🔐 服务账号：
  ✓ 已在Google Cloud中创建
  ✓ JSON密钥已下载
  ✓ 已关联到Play Console
  ✓ 已授予权限

📝 商店元数据：
  ✓ 已创建结构：fastlane/metadata/android/en-US/
  ✓ 已配置语言环境
  ✓ 模板已准备就绪

✅ API验证：
  ✓ 已创建验证脚本
  ✓ API连接已测试
  ✓ 包访问权限已确认

📋 后续步骤：

  GitHub相关：
    1. 添加Secrets（如存在GITHUB_SECRETS.md请参考）
    2. 创建带审核人的"production"环境

  部署相关：
    1. 运行：/devtools:android-playstore-publish
    2. 生成部署工作流

⚠️ 重要提醒：
  - 切勿将服务账号JSON提交到git
  - 将JSON密钥存储在密码管理器中
  - 部署前将所有5个Secrets添加到GitHub
  - 授予权限后等待5-10分钟生效

Integration with Other Skills

与其他Skill的集成

This skill is prerequisite for:
  • android-playstore-publishing
    - Uses service account for deployment
  • android-playstore-pipeline
    - Complete pipeline setup
本Skill是以下Skill的前置条件：
  • android-playstore-publishing
    - 使用服务账号进行部署
  • android-playstore-pipeline
    - 完整的流水线设置

Troubleshooting

故障排除

If any skill fails:
  1. Fix the specific issue in that skill
  2. Re-run that skill until it completes
  3. Continue with remaining skills
  4. Run final verification
Common issues:
  • Service account not found → Check Google Cloud project
  • Permissions denied → Grant "Release" permission
  • API validation fails → Wait 5-10 minutes for propagation
如果任何Skill执行失败：
  1. 修复该Skill中的具体问题
  2. 重新运行该Skill直到完成
  3. 继续执行剩余Skill
  4. 运行最终验证
常见问题：
  • 服务账号未找到 → 检查Google Cloud项目
  • 权限被拒绝 → 授予"发布"权限
  • API验证失败 → 等待5-10分钟让权限生效
undefined