Build Lifecycle
Use this skill when uploading builds, waiting for processing, managing APKs/bundles, or uploading deobfuscation files.
Bundles (AAB)
Upload bundle
gpc bundles upload --file app.aab --track internal --package com.example.appList uploaded bundles
gpc bundles list --package com.example.appFind bundle by version code
gpc bundles find --version-code 42 --package com.example.appWait for processing
gpc bundles wait --version-code 42 --package com.example.app
gpc bundles wait --version-code 42 --timeout 600 --interval 30 --package com.example.appAPKs (legacy)
Upload APK
gpc apks upload --file app.apk --package com.example.appList APKs
gpc apks list --package com.example.appDeobfuscation files
Upload ProGuard mapping
gpc deobfuscation upload --version-code 42 --file mapping.txt --type proguard --package com.example.appUpload native debug symbols
gpc deobfuscation upload --version-code 42 --file symbols.zip --type native-code --package com.example.appCI/CD build pipeline
Typical CI flow:
# 1. Upload bundle
gpc bundles upload --file app.aab --track internal --commit --package com.example.app
# 2. Wait for processing
gpc bundles wait --version-code $VERSION_CODE --timeout 600 --package com.example.app
# 3. Upload ProGuard mapping for crash symbolication
gpc deobfuscation upload --version-code $VERSION_CODE --file mapping.txt --type proguard --package com.example.app
# 4. Promote to beta
gpc tracks promote --from internal --to beta --package com.example.appAgent behavior
- Always use AAB format over APK (APK upload is deprecated).
- Upload deobfuscation files immediately after build upload.
- Use
gpc bundles waitin CI to block until processing completes. - Show bundle list after upload to confirm success.
Notes
- AAB is required for new apps; APK support is for legacy apps.
- ProGuard mappings enable readable crash stacks in Android Vitals.
- Native debug symbols enable symbolicated native crash reports.
- See
gpc-release-flowskill for track promotion after upload.