-
Notifications
You must be signed in to change notification settings - Fork 655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to run multiple instances of livereload simultaneously #1866
Comments
For others looking for this, the workaround can be found here: |
trsrm
added a commit
to powwowinc/ionic-app-scripts-tiny
that referenced
this issue
Jan 2, 2019
3.1.9: * fix(2889): fix build error with --prod * fix(serve): start listening when watch is ready * fix(live-server): update android platform path (ionic-team#1407) * docs(changelog): 3.1.9 3.1.10: * Update node-sass dependency (ionic-team#1435) Updating node-sass dependency from 4.7.2 to 4.9.0 to make it works with node 10 on windows (build fail with ionic start) * chore(package): bump deps (ionic-team#1421) * chore(deps): no package lock * chore(changelog): 3.1.10 3.1.11: * fix(serve): fix EADDRINUSE issue with dev logger server fixes ionic-team/ionic-cli#3368 fixes ionic-team/ionic-cli#1678 fixes ionic-team/ionic-cli#1830 fixes ionic-team/ionic-cli#1721 fixes ionic-team/ionic-cli#1866 fixes ionic-team/ionic-cli#1808 fixes ionic-team/ionic-cli#3022 * docs(changelog): 3.1.11 changes 3.2.0: * feat(environments): configuration via process.env.VAR replacement (ionic-team#1471) * fix(sass): remove PostCSS warning (ionic-team#1364) This removes following warning: Remove warning: Without `from` option PostCSS could generate wrong source map or do not find Browserslist config. Set it to CSS file path or to `undefined` to prevent this warning `from: the input file name (most runners set it automatically).` Source: https://github.com/postcss/postcss Fixes ionic-team#1359 #13763 ionic-team#1359 ionic-team/ionic-framework#13763 * fix(serve): use wss protocol for secure websocket when page is using https (ionic-team#1358) * docs(changelog): 3.2.0 3.2.1: * docs(readme): add note about existing declaration addresses ionic-team/ionic-cli#3541 * chore(deps): update webpack to 3.12.0 (ionic-team#1477) * chore(deps): bump node-sass to 4.9.3 to fix security warnings (ionic-team#1483) * chore(deps): bump node-sass to 4.10.0 to fix security warnings (ionic-team#1493) * docs(changelog): 3.2.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @sarahsga on January 20, 2017 15:44
Ionic version:
[ ] 1.x
[ x] 2.x
I'm submitting a ...
[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:
unable to simultaneously run livereload on ios, android and browser.
Expected behavior:
expected to simultaneously be able to run livereload on ios, android and browser, to be able to test on multiple platforms simultaneously. This worked flawlessly with ionic 1.x
Steps to reproduce:
Step 1: ionic run ios -l -c --device
This will run livereload on ios device connected to the machine.
Step 2: ionic run android -l -c
This will give an error
This happens because the address "192.168.8.102" is already in use by livereload running on ios. I have tried changing port (--port), livereload-port (--livereload-port), nothing's working.
Other information:
I was able to run multiple instances of livereload on one address "192.168.8.102" simultaneously while developing ionic 1.x applications
This issue ionic-team/ionic-framework#9425 addresses this problem, but it does not address how to run multiple livereload instances simultaneously.
Ionic info:
Copied from original issue: ionic-team/ionic-framework#10114
The text was updated successfully, but these errors were encountered: