Stf: adb connect xx.xx.xx.xx:port fails to prepare device for connection

[jagsme]

What is the issue or idea you have?
adb connect xx.xx.xx.xx:7409 dies immediately after preparing device for connection

Does it only happen on a specific device? Please run adb devices -l and paste the corresponding row.

• happens on all the devices
  adb devices -l
  device usb:336855040X product:bullhead model:Nexus_5X device:bullhead transport_id:3

Please provide the steps to reproduce the issue.
perform
1) stf local --public-ip --allow-remote
2) remote connect a device
3) perform automation using the adb devices - remote url

What is the expected behavior?
device should launch the app when automation is triggered

Do you see errors or warnings in the stf local output? If so, please paste them or the full log here.

9-11-13T11:26:29.923Z ERR/provider 25844 [] Device worker "xx:xx:xx:xx:7401" died with code 1
2019-11-13T11:26:29.923Z INF/provider 25844 [] Restarting device worker "xx:xx:xx:xx:7401"
2019-11-13T11:26:30.671Z INF/device:support:push 25901 [xx:xx:xx:xx:7401] Sending output to "tcp://127.0.0.1:7116"
2019-11-13T11:26:30.673Z INF/device 25901 [xx:xx:xx:xx:7401] Preparing device
2019-11-13T11:26:30.947Z INF/device:support:sub 25901 [xx:xx:xx:xx:7401] Receiving input from "tcp://127.0.0.1:7114"
2019-11-13T11:26:30.948Z INF/device:support:sub 25901 [xx:xx:xx:xx:7401] Subscribing to permanent channel "*ALL"
2019-11-13T11:26:30.958Z FTL/device 25901 [xx:xx:xx:xx:7401] Setup had an error FailError: Failure: 'device offline'
at /Users/jagsme/.nvm/versions/node/v8.9.4/lib/node_modules/stf/node_modules/adbkit/lib/adb/parser.js:183:29
at runCallback (timers.js:789:20)
at tryOnImmediate (timers.js:751:5)
at processImmediate [as _immediateCallback] (timers.js:722:5)

stf doctor
2019-11-13T11:24:59.509Z INF/cli:doctor 25814 [] OS Arch: x64
2019-11-13T11:24:59.510Z INF/cli:doctor 25814 [] OS Platform: darwin
2019-11-13T11:24:59.510Z INF/cli:doctor 25814 [] OS Platform: 18.7.0
2019-11-13T11:24:59.510Z INF/cli:doctor 25814 [] Using Node 8.9.4
2019-11-13T11:24:59.527Z INF/cli:doctor 25814 [] Using ZeroMQ 4.3.2
2019-11-13T11:24:59.541Z INF/cli:doctor 25814 [] Using ADB 1.0.41
2019-11-13T11:24:59.542Z INF/cli:doctor 25814 [] Using GraphicsMagick 1.3.33
2019-11-13T11:24:59.547Z INF/cli:doctor 25814 [] Using RethinkDB 2.3.6
2019-11-13T11:24:59.632Z INF/cli:doctor 25814 [*] Using ProtoBuf 3.10.0

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.85. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[jagsme]

Any updated on this?

[ryoyakawai]

Just an information what is happening on my environment.
My situation is like this:

• Android 10 over Pixel 4: Fires this issue😢
• Android 8.1.0 over Nexus 6s: No problem 😊
• Android 7.1.1 on Nexus 6: No problem 😊

STF environment:
Using this docker-compose to build the STF environment on Ubuntu 18.04.3 LTS.

• nikosch86/stf-poc: single host deployment of STF for PoC purposes or when scaling to 14 devices is sufficient for you

The ADB version Inside container:

# adb version
Android Debug Bridge version 1.0.41
Version 29.0.5-5949299

And all devices including Android 10 is listed by adb devices as same as Android 7&8 devices.

I am not researching this issue in deep, so I am not sure exactly what is happening. However, I can guess there is something different things, such as spec changed on Android side, is happening around the combination of STF and ADB from this light research.

I hope this information helps to resolve the problem.

[Extra Research Information]

• Manual install of STFService.apk could not make any changes the issue

[koral--]

• Android 10 over Pixel 4

STF does not yet support Android 10.

[jagsme]

hey @ryoyakawai @koral-- I am using nexus - which has Android 8. Still no success, I have tried it in other devices as well, like Android 9.