bug: ERR_NO_DEVICE: with cli 5.0.1 #4022
Labels
Comments
|
I have tried:
|
|
Can you try updating to latest version of native-run? (0.2.3) |
|
Let me try those things. also, Android Studio did detect the phone was connected. |
|
I was facing the same issue. Adding |
|
@ctfrancia What is the output of |
|
|
Oh, so it's finding the device ( Could I also see the verbose logs for Please also make sure you're on the latest version of native-run, there's been a few updates to both Android and iOS: |
|
Here's my output of |
|
Oh, forgot to mention, I have Windows 7 64-bit Sifting through the verbose log, there is no "usb" anywhere, only "transport_id: 2" (the number changes depending on which USB port I plug into). So it must be the peculiarity of adb on windows and how native-run checks for hardware vs. the emulator (quick glance reveals it just searches for "usb" in adb report). I hacked file 'C:\nodejs\node_modules\native-run\dist\android\utils\adb.js' to have: ...
// const type = 'usb' in properties || isIP ? 'hardware' : 'emulator';
const isWinAdbTransport = true; // TODO: sophisticated test for "windows" && ('transport' in properties)
const type = 'usb' in properties || isIP || isWinAdbTransport ? 'hardware' : 'emulator';and then the command |
|
@iva2k Thanks for diving deep into that stuff. From the sound of it, it kinda ties into this issue: ionic-team/native-run#36 |
|
I have just upgraded to 5.0.2 and the issue has came back and making connecting to the device very very difficult to do. |
imhoffd
added a commit
to ionic-team/native-run
that referenced
this issue
Jun 25, 2019
|
@ctfrancia @iva2k Please give the latest native-run a try to see if the issue is fixed. Thanks for your patience.
|
|
@dwieeb no problem, I understand it's not always so easy 😅 . I currently have installed ionic cli 5.1.0 / native-run@0.2.7 and I am still wrestling with it. Chrome inspector detects it (I know this is a different subject). I know you guys are working on it. |
|
@ctfrancia The changes in the latest version of Can I see the output of |
|
|
Sometimes it works on the first time. But, by large I constantly have to unplug, plug, restart the device and it's never garanteed that it will be recognized. I changed phones to a more recent one to see if that has changed anything, but, it still has a problem recognizing it. |
|
Do you have |
|
these are my globals from npm: |
|
It's not installed with npm. It may have been installed with homebrew or by simply downloading it. Could you post the output of |
@dwieeb I checked - native-run@latest now lists my phone in "Connected Devices" |
|
@dwieeb after |
Great to hear 👏 @ctfrancia I am calling this issue fixed. From your description here:
This is a lower-level adb issue. I get this with a newer Android phone as well. As far as I know, we just have to wait for adb and the Android tooling to fix these kinds of stability issues. Thanks for your help debugging this. 👍 |
|
👍 hopefully the native run will improve because it still works a lot better without using native run 🤷♂️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Ionic version:
[x] 4.x
Current behavior:
Ever since upgrading to ionic cli 5 running my ionic app on my Android device is nearly impossible as I consistantly get the error
I am not sure if this is a 'native-run' issue but since i need it to launch the app on the Android device I thought here was the more appropriate.
I have had to go back to cli 4. so I can launch the app.
Expected behavior:
for my app to launch natively
Steps to reproduce:
$ ionic cordova run android --device --livereloadRelated code:
Other information:
Ionic info:
The text was updated successfully, but these errors were encountered: