Closed itslenny closed 7 years ago
Update
I've realized this only happens in live reload mode (with the -l
flag). Everything seems fine without that. Maybe this is the intended behavior (although it's kinda annoying to need to have to totally restart the emulator for any change).
Is there any way to support live reload and have cordova be recognized?
If not this should at least be explained in the documentation.
Hello, thanks for opening an issue with us! I am going to close this issue as a duplicate of https://github.com/driftyco/ionic-app-scripts/issues/467.
Yes i have the same issue and i can confirm it's only working without live reloading option -l , i hope there is some fix soon :)
@morfobin90
You on droid??
Yes :+1:
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.
Ionic version: (check one with "x") [ ] 1.x [x] 2.x
I'm submitting a ... (check one with "x") [x] bug report [ ] feature request [ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Getting a cordova not available error with a brand new app running in the android emulator.
Expected behavior: Cordova to "just work" when a new ionic app is created.
Steps to reproduce:
Related code:
Other information:
Console output from
chrome://inspect
:Ionic info: (run
ionic info
from a terminal/cmd prompt and paste output below):