npx cap run android doesn't seem to do anything

[Harvtronix]

Hello! I'm super excited to be using the capacitor and ionic frameworks. I got my first capacitor app running on both android and ios in under an hour, which was awesome!

I'm having a bit of an issue though, so I'm curious if I'm doing something incorrectly or if perhaps I've hit a legitimate bug.

I'm using Capacitor 3.0.0-beta.3.

When I run npx cap run android, I get the following output:

(geodude)% npx cap run android
✔ Copying web assets from build to android/app/src/main/assets/public in 11.65ms
✔ Creating capacitor.config.json in android/app/src/main/assets in 1.56ms
✔ copy android in 29.75ms
✔ Updating Android plugins in 3.91ms
✔ update android in 39.89ms
(geodude)% 

But then the terminal prompt just returns and nothing else ever happens. When I do the same for ios, it prompts me to select a virtual device and then launches the app in it. I'm not seeing the same sort of thing for android.

npx cap open android works as expected and I can click the green "run" button in there to launch the app in a virtual device with no issues.

For fun, I saw there was a --target command line option to cap run, so I tried passing my virtual device's id to it:

(geodude)% npx cap run --target Pixel_3a_API_30 android
✔ Copying web assets from build to android/app/src/main/assets/public in 14.54ms
✔ Creating capacitor.config.json in android/app/src/main/assets in 1.78ms
✔ copy android in 32.80ms
✔ Updating Android plugins in 4.46ms
✔ update android in 43.30ms
[error] Invalid target ID: Pixel_3a_API_30.
        Valid targets are:
(geodude)% 

I also just tried listing the virtual devices from the command line via advmanager (not sure if this is now cap is doing it), and my device does indeed show up in the list.

Any help would be appreciated!

I didn't see any debug-type arguments for cap, but if they are available, I'm more than happy to turn them on for additional info.

[alanxp]

i get gradle errors aswell

[thelement115]

did you find a solution?, I am getting the same error

[alanxp]

did you find a solution?, I am getting the same error

Downgraded to v2. So many problems with 3.0

[Feffy]

I had the same issue. Installing the latest capacitor cli version and then running npx cap sync fixed it. Hope this helps.

[Danbardo]

I had a similar problem, I just left mine for about 5 minutes and it asked to select a device.

[c-y-q]

change java jdk version, clean as and restore as, l have tired it ,is ok

[dsuttonpreece]

@Harvtronix I'm also having this issue. Device list is empty when npx cap run --list android, but avdmanager list returns a long list of devices…

Do you intend on raising this as an issue?

[brunocrosier]

Same issue, running npx cap run --list android doesn't seem to do anything. I think the docs might benefit from a bit more detail here

[Harvtronix]

Looks like someone opened issue #4571 for this. Looks related to Android SDK 30 vs 29. I'll monitor that and hope for a solution soon!

[jcesarmobile]

this was a bug in native-run, has been fixed in latest version (1.4.0)

since native-run is a dependency of @capacitor/cli, you can try to reinstall the CLI and it should pick the latest version, but make sure that was the case by checking the installed version in package-lock.json
If not updated, you can force update the dependency with npm update native-run --depth 6

[ravithb]

Can confirm that it still happens even with native-run 1.4.0

[jcesarmobile]

Update capacitor CLI to 3.0.1 and try again.
It included some improvements to show native-run errors.
This was fixed in 1.4.0, so should be something else.