Android Emulator is not able to open application in dev mode (doesn't see Vite server) #17725
Labels
Comments
github-actions
bot
added
bug/1-repro-available
|
I encountered the same issue and haven't found the root cause yet. My guess is that Quasar might not have successfully created the service in Capacitor mode. However, you can achieve the desired functionality indirectly using the following steps: 1.Start the app service with a specified port(same port as the second command) |
yusufkandemir
added
bug/2-confirmed
|
Cannot reproduce. |
rstoenescu
removed
the
bug/2-confirmed
|
Hello, I have no explanation why it stopped working, then why it started working again :( My config:
EDIT 01/07 In fact, this does not work. The dev server does not start |
|
I've run into the same issue:
It appears to me as if the dev server doesn't start. The first output is the result of running curl on my machines local ip address after I started up EDIT: What I want to show with the last picture: The server is up and running after calling
|
|
I have the same problem after upgrading to
EDIT: This comment originally had information about reproducing the error with a brand new quasar app but after rebooting my machine the dev server for the new quasar app now works correctly. Unfortunately my app is still broken with the same error.
|
|
This can be reproduced on both Windows and Linux on a brand new Quasar project.
Repeat the same command except pick Vite 2 on the first step, and the app will connect to the dev server successfully. |
|
@rstoenescu Besides GitHub, on Quasar Discord, many people say experiencing the same bug.
Brand new template: Then: Then: I've pushed the resulting repro there, so you can see all the dependencies in package.json: https://github.com/nicobao/quasar-repro-capacitor-dev-issue Android Studio Version: OS: Debian GNU/Linux 12 (bookworm) Android Studio logcat logs (Pixel 3a emulated app): |
|
Seems the actual problem with the emulator comes from the fact that the dev server is actually not being started or bound to port 9500 - |
|
|
there is no service listening on port 9500. I opened a browser on no, I don't have any firewall that blocks, but again - as I mentioned, there is no service that listens on port 9500 after running ss -tunl | grep 9500shows nothing. Same result with: lsof -i -P -n | grep LISTENIf I run |
|
just to mention - this was working just fine couple of weeks ago on my system. Today I upgraded Quasar (and quasar/app-vite) to the latest versions and now it doesn't work. |
|
Can you downgrade to the version that was working and tell me which that is, pls? |
|
hm.... I downgraded to quasar 2.17.4 with app-vite 2.0.0 but observe the same problem. Are there any logs that I could check (on linux)? Alternatively, how can I run the vite dev server on the command line - the one quasar is invoking when running |
|
unfortunately I'm not able to revert to a working setup. The strange thing is that My setup is:
I have also tried running |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
When I start application for mobile development using this command:
Android Studio opens, but I get error following error:
What did you expect to happen?
App should open inside Android Emulator.
Reproduction URL
https://codepen.io/rstoenescu/pen/xxEvBLR
How to reproduce?
quasar dev -m capacitor -T androidFlavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Capacitor Mode
Platforms/Browsers
Android
Quasar info output
No response
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: