search

DeviceFarmer / adbkit

A pure Node.js client for the Android Debug Bridge.
Other
239 stars 56 forks source link

TcpIP sometimes throws an empty error #527

Open YishaiYosifov opened 6 months ago

YishaiYosifov commented 6 months ago

Calling device.tcpip() will sometimes throw an empty error:

Error
    at E:\Projects\adb\node_modules\@devicefarmer\adbkit\src\adb\command\host-transport\tcpip.ts:17:21
    at tryCatcher (E:\Projects\adb\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (E:\Projects\adb\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (E:\Projects\adb\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (E:\Projects\adb\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (E:\Projects\adb\node_modules\bluebird\js\release\promise.js:729:18)
    at _drainQueueStep (E:\Projects\adb\node_modules\bluebird\js\release\async.js:93:12)
    at _drainQueue (E:\Projects\adb\node_modules\bluebird\js\release\async.js:86:9)
    at Async._drainQueues (E:\Projects\adb\node_modules\bluebird\js\release\async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (E:\Projects\adb\node_modules\bluebird\js\release\async.js:15:14)
    at processImmediate (node:internal/timers:478:21)

This is caused by adb tcpip sometimes, instead of outputting restarting in TCP mode port: xxxx, not outputting anything, yet the device is still restarted in tcp mode.