Geoff, can you help me debug this? We either need to figure out why android.py doesn't like this new adb version or pin ourselves to the last stable release for now (hard to say if this is a bug with the new adb or something we'll need to deal with eventually).
Bug 1822171 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Geoff, can you help me debug this? We either need to figure out why android.py doesn't like this new adb version or pin ourselves to the last known-good release for now (hard to say if this is a bug with the new adb or something we'll need to deal with eventually).
Geoff, can you help me debug this? We either need to figure out why android.py doesn't like this new adb version or pin ourselves to the last known-good 34.0.5 release for now (hard to say if this is a bug with the new adb or something we'll need to deal with eventually).
Geoff, can you help me debug this? We either need to figure out why android.py doesn't like this new adb version or pin ourselves to the last known-good 34.0.5 release for now (hard to say if this is a bug with the new adb that will get fixed down the road or a real behavior change we'll need to deal with eventually).