#Testing on Android device over ADB?
18 messages ยท Page 1 of 1 (latest)
Obviously this is because web dev server is not running on android device
Does anyone have a proposed solution or how can I go about testing this with local device as described?
I could open ports on localhost web server, then point Tauri at the IP address in my local network to that web server/ip where it is running (and connect android device to local network)
But was wondering if maybe there was a better way anyone knew of where I could just run tauri run android dev and it will shoot the web server/app over ADB
in theory there's adb port forwarding or whatever it was called, but we don't rely on that anymore because it never really worked on windows
your issue btw sounds like a misconfiguration of your frontend. It has to be configured to listen to the local network and not just localhost.
you can btw test create-tauri-app templates, which all should work out of the box
p.s. i exclusively use real devices over adb. i hate simulators.
i set the dev server command to be "dev": "vite dev --host", so it exposes server to local network, and that is working okay
but from device, on the Tauri app it is still looking for 192.168.1.168, on the device itself
which means web server would have to be running on the device?
im trying to get here ๐ i love being able to physically test the app on my own device
getting real tired of the java + qemu hogging my resources just for testing
I just see white screen xd
that url sounds more like it's trying to connect to your computer.
unless of course that's the url of your phone, but seeing 127.0.0.1 would be more likely then
Like i've said during the live, maybe your should check your logs with adb first