mobile-dev-inc / mobile-dev-inc/dadb
dadb.install fails when abb_exec is not available
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
When abb_exec isn't available, the install method falls back to pushing the apk file to the remote device in the /data/local/tmp/ folder and then using 'shell pm install' to try to install it from there. However this will fail with "java.lang.IllegalArgumentException: Error: Can't open file" because the required permissions are missing. After pushing the apk file and before installing there needs to be a further step, something like: shell("chmod 705 "$remotePath"")
Contributor 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.
Research direction
Start at the dadb.install entry point and inspect its fallback path when abb_exec is unavailable. Reproduce installation on a remote Android device, then verify that the pushed APK can be installed with shell pm install after the required permission step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- devtools, mobile-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100