Ionic CLI unexpectedly exists

Hi all,
directly after running ‘ionic serve’ , the cli exists without any error message, and stops serving content to the frontend.

I have had this problem since a few weeks since I upgraded the framework.

$ ionic start testabc
$ cd testabc/
$ ionic setup sass
$ ionic serve
Gulp startup tasks: [ ‘sass’, ‘watch’ ]
Running dev server: http://localhost:8100
Running live reload server: http://localhost:35729
Watching : [ ‘www//*’, '!www/lib//*’ ]
Ionic server commands, enter:
restart or r to restart the client app from the root
goto or g and a url to have the app navigate to the given url
consolelogs or c to enable/disable console log output
serverlogs or s to enable/disable server log output
quit or q to shutdown the server and exit

ionic $ MacBook-Pro:testabc me$

Is there a way to determine the cause of this ? Anyone else having this problem ?
What are the dependencies of running ionic serve ?

These are the versions of the dependencies I see:
$ ionic -v
$ node -v
$ bower -v
$ sass -v
Sass 3.4.13 (Selective Steve)


Hey @sponnet, did you find a solution to this?

@msive1 haven’t looked further into it yet. Next step would be to debug the cli to see where it fails.

Hey @sponnet, this problem is now gone! I’m not sure why, the only things i’ve changed are:

  • installed cordova whitelist plugin -
  • added my api and a couple of other domains to config.xml whitelist
  • added Content Security Metatag
    That seemed to solve the problem and ‘ionic serve’ works now.
    Best of luck.