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

Verify the available device before run command #1670

Open
merbin2012 opened this issue Sep 22, 2023 · 1 comment
Open

Verify the available device before run command #1670

merbin2012 opened this issue Sep 22, 2023 · 1 comment

Comments

@merbin2012
Copy link

Most of the time the testing mobile disconnect automatically or other some reason, and when I try to run the app on the device it show this message "Could not find target matching { id: 'xxxxxxxx' }", I think must cordova run command should verify the available device then start the generating apk process. This should save developers time.

Thank you.

@merbin2012 merbin2012 changed the title Verify device after build and run Verify the available device before run command Sep 22, 2023
@breautek
Copy link
Contributor

I don't really have any rejection of adding this verification but... there needs to be an understanding that the ADB is just simply crap. In my experience the device can disconnect from ADB at any time, including between the verification check and the time it actually tries to deploy to the device. I've had devices disconnect from ADB while actively debugging. It's truly the most frustrating experience with Android development.

A co-worker of mine has a newer device than I do that has debugging over WiFi support and he says that is more stable than debugging over USB, but he still runs into this kind of problem occasionally, just not as frequently with USB cables.

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

No branches or pull requests

2 participants