菜单
Android Capacitor guidance for diplicity-react — build workflow, ADB setup, Firebase Cloud Messaging, Google Sign-In, keystore management, SHA-1 fingerprints, and Fastlane releases. Use when building, deploying, or debugging the Android app, or managing Android credentials.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | android |
| description | Android Capacitor guidance for diplicity-react — build workflow, ADB setup, Firebase Cloud Messaging, Google Sign-In, keystore management, SHA-1 fingerprints, and Fastlane releases. Use when building, deploying, or debugging the Android app, or managing Android credentials. |
| allowed-tools | Bash, Read, Glob, Grep |
Always use the physical Pixel 8a — do not use the emulator (too much RAM).
com.diplicityreact.apppackages/web/android/46101JEKB13333sudo apt install openjdk-21-jdk (Java 17 is not sufficient for Capacitor Android 8)sudo snap install android-studio --classic (includes SDK, build-tools, ADB)ANDROID_HOME: add to ~/.bashrc:
export ANDROID_HOME="$HOME/Android/Sdk"
export PATH="$ANDROID_HOME/platform-tools:$PATH"
echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"' | sudo tee /etc/udev/rules.d/51-android.rules
sudo udevadm control --reload-rules && sudo udevadm trigger
sudo usermod -aG plugdev $USER
# Log out and back in, then unplug/replug device
adb kill-server && adb devices
# Accept "Allow USB debugging" on the phone
All Capacitor commands must run from packages/web/ — capacitor.config.ts is there.
cd packages/web
npm run build
ANDROID_HOME=$HOME/Android/Sdk npx cap sync android
ANDROID_HOME=$HOME/Android/Sdk npx cap run android --target 46101JEKB13333
Version management: versionName comes from package.json version field; versionCode is a Unix timestamp auto-generated per build. Both set in android/app/build.gradle — no manual editing needed.
Uses @capacitor-firebase/messaging. Requires google-services.json at packages/web/android/app/google-services.json (gitignored).
Setup: Firebase console → project diplicity-react → Project settings → Add app → Android → package name com.diplicityreact.app → download google-services.json.
android/app/build.gradle conditionally applies com.google.gms.google-services when the file exists. Runtime POST_NOTIFICATIONS permission (Android 13+) is handled by FirebaseMessaging.requestPermissions() in messaging-native.ts.
Uses VITE_GOOGLE_CLIENT_ID (web client ID) as webClientId in SocialLogin.initialize(). No separate Android client ID needed in app code.
An Android OAuth client must be registered in Google Cloud Console (Credentials page, same project as web client) with package name com.diplicityreact.app and the appropriate SHA-1 fingerprint.
| Keystore | SHA-1 | Purpose |
|---|---|---|
~/.android/debug.keystore (androiddebugkey) | 6F:9D:E2:20:2F:35:17:10:8C:41:28:B2:61:F5:4F:DE:7F:B1:0E:38 | Local dev / debug builds |
diplicity-android-upload.keystore (upload) | 6A:39:8D:D3:B4:43:12:22:0C:4C:FA:08:93:B7:AD:19:58:D2:E0:0E | Release builds |
| Play App Signing certificate | 17:CF:46:81:F1:B2:95:8E:16:25:4A:9E:3E:85:F9:84:17:42:AD:58 | Play Store / CI |
# Re-extract debug SHA-1
keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
| Item | Value |
|---|---|
| File | diplicity-android-upload.keystore (repo root, gitignored) |
| Alias | upload |
| Validity | 10,000 days (expires 2053-10-11) |
| Password | See password manager: "diplicity-android-upload.keystore" |
Required env vars for release builds:
ANDROID_KEYSTORE_PATH=/path/to/diplicity-android-upload.keystore
ANDROID_KEYSTORE_PASSWORD=<password>
ANDROID_KEY_ALIAS=upload
ANDROID_KEY_PASSWORD=<password>
Local release build:
cd packages/web/android
ANDROID_HOME=$HOME/Android/Sdk \
ANDROID_KEYSTORE_PATH="$(git rev-parse --show-toplevel)/diplicity-android-upload.keystore" \
ANDROID_KEYSTORE_PASSWORD="..." \
ANDROID_KEY_ALIAS="upload" \
ANDROID_KEY_PASSWORD="..." \
./gradlew bundleRelease
If the keystore is lost, generate a new one and submit via "Upload new key" in Play Console App Signing settings — Google holds the actual distribution signing key.
Run from packages/web/:
# Full release to Play Console internal track
VITE_DIPLICITY_API_BASE_URL=https://diplicity-react-production.up.railway.app \
npm run build && npx cap sync android && bundle exec fastlane android release
# PR build
PR_NUMBER=42 PR_TITLE="My feature" bundle exec fastlane android pr_build
Required env vars: ANDROID_KEYSTORE_PATH, ANDROID_KEYSTORE_PASSWORD, ANDROID_KEY_ALIAS, ANDROID_KEY_PASSWORD, PLAY_SERVICE_ACCOUNT_JSON (optional — upload skipped if unset).
android-release.yml (or similar): triggers on push to main when packages/web/** changesANDROID_KEYSTORE_BASE64, ANDROID_KEYSTORE_PASSWORD, ANDROID_KEY_ALIAS, ANDROID_KEY_PASSWORD, PLAY_SERVICE_ACCOUNT_JSON| File | Purpose |
|---|---|
diplicity-android-upload.keystore | Android upload keystore |
packages/web/android/app/google-services.json | Firebase Android config |
Django backend guidance for diplicity-react — views, serializers, models, permissions, constants, transactions, and codegen. Use when implementing or reviewing backend features, modifying the Django service, or debugging API behavior.
React frontend guidance for diplicity-react — components, state management, forms, data loading, routing, mock data, screenshots, and testing. Use when implementing or reviewing React features, refactoring frontend code, or taking PR screenshots.
iOS Capacitor guidance for diplicity-react — build workflow, Xcode project setup, APNs and ASC credentials, code signing strategy, Fastlane releases, and GitHub Actions. Use when building, deploying, or debugging the iOS app, or managing iOS credentials.
Metabase analytics guidance for diplicity-react — native SQL patterns for multi-hop joins, base64 encoding workflow, and schema gotchas in the diplicity production database. Use when writing Metabase queries or working around schema limitations.
Production debugging guidance for diplicity-react — Railway CLI token conflict pattern, pgweb queries, write safety rules, and staging environments. Use when debugging production issues, querying the production database, or deploying PR staging environments.
Testing guidance for diplicity-react — frontend Vitest and backend pytest patterns, fixtures, conftest organisation, MSW mocks, and performance tips. Use when writing or running tests, setting up fixtures, or reviewing test code.