Android: turian devices and turian deploy over adb
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- android, csharp
- Domain
- devtools, mobile-dev
Research direction
Start by reading the Android plan task B6 and the dependency issues #254 and #260, then trace how the toolchain is resolved. Implement the listed device discovery and deploy flow, including install, launch, log output, stopping, and device error handling. Done means an end-to-end deploy works on a Galaxy S24 FE; the issue says to keep this local on feat/android-platform until .NET 11 GA and CI support.
Written by the indexing model from the issue text.
Description
Current State
Exports cannot reach a device; the editor has no device concept.
Tasks
- Locate adb through the toolchain resolution
-
turian devices;turian deploy <proj> --profile Android [--device] - Install (
install -r --streaming), launch (am start -W), taillogcat --pid, stop on Ctrl+C (force-stop) - Clear errors: no device, unauthorized, several devices without
--device
Acceptance Criteria
- End to end on the Galaxy S24 FE
Related
- Android plan task B6 · seniority Mid · local-only on
feat/android-platformuntil .NET 11 GA and CI support - Depends on: #254, #260
- Platform roadmap: #100
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 48m
- Merged PRs (30d)
- 30
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:docs p:high size:S t:docs
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
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
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
代理地址输入框的示例提示容易被误认为已配置代理Possibly taken @jay23606 claimed this today. Openbug
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
kookxiang/jellyfin-plugin-bangumi#297 ·
Maintainers usually reply within 1 day
-
A numeric literal is parsed in the host's culture, so 1.5 is 15 in a made EXE on a comma-decimal OSOpenbug interpreter silently-wrong small
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day