0x192 / 0x192/universal-android-debloater
UAD fail to detect ADB and devices. 🔥
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
OS: Mac
UAD binary saved in the same directory as adb, and chmod +X done.
using terminal `adb devices` list the device.
While running UAD ( standalone or from the same terminal) fails to detect ADB.
GUI launches fine, and trying to search device.
similar issue: #751
**Expected behavior**
ADB should work as expected and located the adb placed next to it.
**You have a solution?**
nope.
probably release a script to be run via adb console instead of relying on GUI
something like `./adb shell pm uninstall -k --user 0 com.sec.android.app.popupcalculator`
**UAD log**
Upload the logfile generated by UAD.
[UAD_20230612.log](https://github.com/0x192/universal-android-debloater/files/11722193/UAD_20230612.log)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue is about ADB detection failure on macOS. Start by examining the ADB detection logic in the Rust codebase, likely in a module handling device discovery or ADB path resolution. Look for environment variable checks or path searching. The log file attached may contain clues about the failure. Testing involves running the GUI and checking console output on a macOS system with ADB installed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, shell
- Domain
- cli, devtools, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100