Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to run on specific device when there are more than 1 device connect to the system #2104

Open
1 task done
EricJr005 opened this issue Oct 21, 2024 · 2 comments
Open
1 task done
Labels

Comments

@EricJr005
Copy link

Is there an existing issue for this?

  • I have searched the existing issues and didn't find mine.

Steps to reproduce

  1. Having more than 1 devices plug into a system
  2. Use --device to specify a device to run test on.
  3. Observe errored results

Actual results

Hello,

I have 2 Android devices connect to my linux system (Ubuntu 20.04.6 LTS) and I am trying to use to suggested solution on targeting specific devices to run test https://maestro.mobile.dev/advanced/specify-a-device. However, I am unable to run test as it shows on the screenshot that devices it is not connected.

*Interesting note, I can run test if I only have one device connect to my system but that defeats the purpose specifying a device.

Screenshot 2024-10-21 at 2 11 07 PM

Expected results

Based on your instruction, I would expect that I can specific a device to run test on.

About app

it is on the Bell TV app which is support both IOS and Android. It is however closed source.

About environment

Ubuntu 20.04.6 LTS

Logs

Logs
<!-- Replace this line with your logs. *DO NOT* remove the backticks! -->

Maestro version

1.39.0

How did you install Maestro?

other (please specify in the text area below)

Anything else?

curl -fsSL "https://get.maestro.mobile.dev" | bash
-pre your instruction https://maestro.mobile.dev/getting-started/installing-maestro

@herval herval added the Maestro label Nov 27, 2024 — with Linear
@Fishbowler
Copy link
Contributor

I can't reproduce this using emulators, which suggests that this issue is specific to either the local environment, or has been fixed in a more recent version of Maestro.

Were you able to make any progress?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants