Android: AndroidPlayerSettings DataAsset
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
Start with the implementation of ProjectAsset and the BuildProfile model, then review dependency #254 and the Android platform roadmap task C1. Trace how generated projects and manifests are produced; done means Android settings can be registered and overridden per profile, feed both outputs, and keep passwords out of assets, with tests covering the generated csproj and manifest.
Written by the indexing model from the issue text.
Description
Current State
Android options (package format, ABIs, version code, orientation, keystore, permissions, icon, trim mode) have no home; BuildProfile stays platform-neutral.
Tasks
-
AndroidPlayerSettingsDataAsset registered inProjectAsset, overridable per build profile - Feed the generated project and manifest
- Keystore path and alias only; passwords never stored in assets
Acceptance Criteria
- Tests on the generated csproj and manifest
Related
- Android plan task C1 · seniority Mid · local-only on
feat/android-platformuntil .NET 11 GA and CI support - Depends on: #254
- Platform roadmap: #100
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 34m
- Merged PRs (30d)
- 35
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:build c:editor p:medium size:XL t:feature
Difficulty 5/5 Over a week Newbie friendliness 5/100
Maintainers usually reply within 1 day
-
c:build p:medium size:XL t:refactor
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
c:build c:ui p:low size:L t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
c:assets c:build p:low size:S t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
Similar issues
-
bug misleading tooling trivial
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Docs example projects pinned to a literal library version instead of 3.*Possibly taken @DaveSkender claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
facioquo/stock-indicators-dotnet#2372 ·
Maintainers usually reply within 1 day
-
[辞書] 「ショタ」の追加Open辞書
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yksr-melt/Meltype#653 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-area
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Azure/typespec-azure#5695 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
svenhb/GRBL-Plotter#483 ·