[Quasar/Cordova] Random error on physical device "net::ERR_ADDRESS_UNREACHABLE"
-
Hello !
May be this issue is related to Cordova rather than Quasar, but someone may have encountered this issue too, so any help is welcomed
.
After building and deploying my app to my physical device (“quasar dev -m cordova -T android”), I sometimes get a “net::ERR_ADDRESS_UNREACHABLE” error, saying that my PC’s local address couldn’t reached.
I don’t know what is trigerring this error, since it sometimes disappear once I re-deploy my app. Sometimes I have to wait few hours…Is there any network config that can fix this issue ?
I already tried to deactivate my firewall, but it does not seem to work.Thanks for your help
Emmanuel
-
@EmmanuelJego quasar dev is not deployment, it’s
dev, if you want to test your apk without attaching your mobile device to your dev pc, then runquasar build -m android --debugnotice the--debugflag, it will create a debug signed apk that you can install into your device.
-
@metalsadman Thanks for your response!
Sorry I wasn’t clear, when I said “deploying” I didn’t mean deployment in the “build an APK” meaning, but “send the debug app to my device”, with my device wired to my PC. As you can imagine, I don’t want to build an APK each time I change a line of code to test my app.
So I don’t think that I’m wrong using the “quasar dev -m cordova -T android” command there.
It just fails to connect to my PC’s local IP address sometimes. And I can’t figure out why.
Thanks
-
@EmmanuelJego non that I can think of other than a loose usb connection.
-
From my router settings, I added NAT/PAT rights in order to make my Android device able to access the 8080 port. It seems to work for now, may be it’s just luck, I’ll tell you if it finally didn’t fix my issue.
-
Well, it worked for few hours, but the issue finally came back.
-
@EmmanuelJego i’ve experienced that myself, it’s an intermittent issue and is out of reach for quasar https://github.com/webpack/webpack-dev-server/issues/2633.
-
Here’s someone that claims to have found a way around this bug: use adb over wireless networks instead of using usb cable:
-
@dobbel Thanks for the help! Actually this solution does not fix the issue, but it can help sometimes to recover the connection, and I found that it is more stable while using adb over wireless networks.
