huntersilikon.blogg.se - Ionic run livereload not working

#IONIC RUN LIVERELOAD NOT WORKING FULL#
#IONIC RUN LIVERELOAD NOT WORKING ANDROID#
#IONIC RUN LIVERELOAD NOT WORKING CODE#
#IONIC RUN LIVERELOAD NOT WORKING WINDOWS#

The port was taken on the host 10.0.0.210 - using port 8000 instead

In essence, -livereload is outright ignored. So now you have two platforms, and none of the two is being updated for changes. It looks like since v2.1.5, this conflict issue has been mitigated by disabling -livereload on ionic emulate.

#IONIC RUN LIVERELOAD NOT WORKING CODE#

Now what happens if you make a change to the /src source code ? Logically you end up with two conflicting builds : the one on the emulator is still based on the old code, while the one on the browser has been updated with the new code base.Can't see the need for the dev server when emulating. So now you have two different testing platforms.

#IONIC RUN LIVERELOAD NOT WORKING FULL#

If you think about it, this means that you are launching a full build for the emulator, and simultaneously spawning a separate dev server with -livereload ability.

In the end, what does it mean to type ionic emulate -livereload ? If ionic emulate -livereload sounds bad, maybe you could implement something like ionic emulate -watch ? A side note I strongly believe that the tooling would be greatly improved by adding the ability to streamline the coding/webpack/cordova process when testing against the emulator or the device. Improving the dev toolsīut ultimately, if I run ionic emulate -livereload I don't expect changes to be pushed to the browser, do I ? However I do expect changes to be pushed to the emulator. It was always intended to be a parameter for the dev server, not for the cordova buids. That's why I think the -livereload terminology is confusing. However the problem is that while ionic emulate -livereload pushes changes to the browser, it does not push them to the simulator. it watches for changes in src/ and pushes them to www/ and then updates the browser. With hindsight I believe there is confusion about the -livereload terminology because ionic serve -livereload works exactly as expected, i.e. The first one deals with webpack (src/ -> -livereload is a parameter for the dev server This means that building involves two different steps. You can check the target name of your device/emulator running $ adb devices.I think the main point is : in Ionic 2 we are working off src/, not www/ If a device is not found it'll then deploy to an emulator/simulator. chrome://inspect/#devicesĭeploys the Ionic app on specified platform devices. Type following command in address bar of the chrome browser.

#IONIC RUN LIVERELOAD NOT WORKING WINDOWS#

Windows: $ ionic emulate windows ĭuring emulating app in AVD or mobiles, you can inspect that app in chrome browser.

#IONIC RUN LIVERELOAD NOT WORKING ANDROID#

This is simply an alias for run -emulator.Īndroid: $ ionic emulate android Quit or q to shutdown the server and exitĭeploys the Ionic app on specified platform emulator. Serverlogs or s to enable/disable server log output Goto or g and a url to have the app navigate to the given urlĬonsolelogs or c to enable/disable console log output While the server is running for live reload, you can use the following commands within the CLI: restart or r to restart the client app from the root Live Reload port (35729 default, live reload req.) Dev server HTTP port (8100 default, live reload req.)

Print dev server logs to Ionic CLI (live reload req.) Print app console logs to Ionic CLI (live reload req.) Live Reload app dev files from the device (beta) Command-line flags/options for run and emulate. Additionally, the development server’s request logs can be printed out using -serverlogs or -s options. With live reload enabled, an app’s console logs can also be printed to the terminal/command prompt by including the -consolelogs or -c option. For live reload to work, the dev machine and device must be on the same local network, and the device must support web sockets. However, any changes to plugins will still require a full rebuild. This reduces the requirement to constantly rebuild the app for small changes. The live reload functionality is similar to ionic serve, but instead of developing and debugging an app using a standard browser, the compiled hybrid app itself is watching for any changes to its files and reloading the app when needed. You can also run live reload on the specified platform device by adding the -livereload option. The run or emulate command will deploy the app to the specified platform devices/emulators. Live Reload App During Development (beta) Run Ionic App on Emulator or on your Phone 1.