Android: release signing and AAB output
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- android, csharp
- Domain
- build-system, mobile-dev
Research direction
Read dependency #263 and the Android export implementation on the feat/android-platform branch. Trace how AndroidPlayerSettings and AndroidPackageFormat are handled, and where credentials are loaded; the issue does not name specific files or tests. Done means Release builds a signed AAB that passes bundletool validate, APK signing passes apksigner verify, and Release rejects the debug keystore.
Written by the indexing model from the issue text.
Description
Current State
Exports only produce debug-signed APKs; Google Play requires signed AABs.
Tasks
- Keystore from
AndroidPlayerSettings; passwords from~/.gaya/credentials.jsonor environment - Release refuses the debug keystore
-
AndroidPackageFormat=aabfor Release
Acceptance Criteria
- Signed AAB passes
bundletool validate; APK passesapksigner verify
Related
- Android plan task C6 · seniority Mid · local-only on
feat/android-platformuntil .NET 11 GA and CI support - Depends on: #263
- Platform roadmap: #100
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 45m
- Merged PRs (30d)
- 31
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MASS4ORG/Turian
-
c:assets p:low size:XS t:task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
c:engine c:scripting p:medium size:XL t:refactor
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
c:assets c:platform p:low size:M t:feature
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
c:platform c:scripting p:low size:M t:task
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
c:docs good first issue p:low size:S t:docs
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
Similar issues
-
python triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/semantic-kernel#14590 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nkdAgility/azure-devops-migration-tools#3226 ·
Maintainers usually reply within 1 day
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dotnet/maui#39362 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day