-
|
While using genymotion emulators I'm getting this error when trying to use any of the emulated android devices: STFagent is installed automatically but I'm also getting the errors in the docker log after app startup like this: devicehub-provider | 2025-03-20T12:38:42.617Z INF/device:plugins:identity 44749 [192.168.242.112:5555] Solving identity The workers on those devices seems to periodically restart, emulator screen goes dark for a few second, wakes up and cycle through. Is there any way to have ability to use emulators beside real phones. It's showing emulated phones in adb devices list and I also can connect to them via scrcpy app, but no luck with device hub. Can I also contact you elsewhere beside vk? Can't seems to get it working. Can I please get your contacts please, maybe telegram, discord, email? Would like to discuss the possibility of partnership |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments
-
|
Hi! As per another way to contact us: At the moment it's either github discussions/issues or the VK chat. Sorry.. |
Beta Was this translation helpful? Give feedback.
-
Because my setup is about running adb host and farm host on different machines (it's okay on running physical phones), this is my docker-compose-prod.yaml: |
Beta Was this translation helpful? Give feedback.
-
|
The compose file lost it's identation. Next time surround it in ticks : ` |
Beta Was this translation helpful? Give feedback.
-
It's actually the original file just + my options, didn't delete anything, I'll try |
Beta Was this translation helpful? Give feedback.
-
Now with |
Beta Was this translation helpful? Give feedback.
-
|
To me it sounds more like a deployment issue, rather than code issue. The error handling when something is not set up properly is not the best, but it should work when setup properly. Make sure the string that is assembled using |
Beta Was this translation helpful? Give feedback.
-
It's all good on my side. The files you mentioned is okay and was never edited, only thing that was touched is "docker-compose-prod.yaml" and "variables.env". It's installing a stfagent on the emulators but can't get that image right (and that beside blinking\locking screen periodically). Maybe some errors on the emulators side would help to clarify what is going on? If so, point please what I'm looking for so I can provide it |
Beta Was this translation helpful? Give feedback.
-
|
You should look for provider logs If you can send them to us via something like pastebin or hastebin - we could hepl you. I'm transitioning this issue to a discussion for noe. |
Beta Was this translation helpful? Give feedback.

To me it sounds more like a deployment issue, rather than code issue. The error handling when something is not set up properly is not the best, but it should work when setup properly. Make sure the string that is assembled using
--screen-ws-url-patternparameter and device parameters resolves to aws://url that is accessible from the browser. Here is where it's assembled. This pattern must allow the browser to connect to the publicHost:publicPort of the provider. See the example in the docker-compose-prod.yaml. When resolved the url will connect to the nginx which will then proxy it to the provider using this part of the config