I don’t believe it’s the wifi connection either. I’ve even tried running the live reload process manually:
ANGULAR CLI LIVERELOAD NOT WORKING MAC
I’ve uninstall and reinstall almost everything on my mac except for the macOS and using a time machine back up. Re-running this command with the -verbose flag may provide more information.
ANGULAR CLI LIVERELOAD NOT WORKING CODE
An error occurred while running subprocess capacitor.Ĭapacitor run ios -no-sync -target 00008020-001964CA2679002E exited with exit code 1. at Pipe.onStreamRead (internal/stream_base_commons.js:188:23) at (internal/streams/readable.js:223:10) at readableAddChunk (internal/streams/readable.js:284:9) at addChunk (internal/streams/readable.js:309:12) at LockdownProtocolReader.onData (/node_modules/native-run/dist/ios/lib/protocol/protocol.js:53:26) at LockdownProtocolReader.callback (/node_modules/native-run/dist/ios/lib/protocol/protocol.js:93:21) at /node_modules/native-run/dist/ios/lib/client/installation_proxy.js:72:24 Error: There was an error installing app When I run ionic cap run ios -l -external -consolelogs, this is the output: Build at: T01:46:15.309Z - Hash: 569f125ecf0bc0a0 - Time: 28248ms When I run npx cap run ios, xcodes opens, and I can run my app on my iphone. My ios certs have expired, and I have tried following these instructions to generated the certs: To establish a secure context you can use the -ssl argument to use HTTPS.Ionic CLI : 6.20.8 (/usr/local/lib/node_modules/ Framework : : : : : 6.1.0Ĭordova-res (update available: 0.15.4) : 0.15.3 Live reload will use HTTP by default which will cause web APIs that require a secure context (like web crypto) to fail. You can also setup the adb bridge over TCP such that subsequent deploys no longer need a USB cable. With port forwarding set up, an external address would no longer be required. For Android, it is possible to configure adb to always forward ports while the adb server is running (see adb reverse).
You can separate the dev server process and the deploy process by using ionic serve and the -livereload-url option of ionic cordova run or ionic capacitor run.Use the -list option to list all targets. With Cordova, use the -device, -emulator, and -target options to narrow down target devices.Remember, with the -external option, others on your Wi-Fi network will be able to access your app. Then, you'll need to specify that you want to use an external IP address for the dev server using the -external flag. To use Live Reload with Capacitor, make sure you're either using a virtual device or a hardware device connected to the same Wi-Fi network as your computer. The difference is the Ionic CLI configures the Web View to load your app from the dev server on your computer. Since Live Reload requires the Web View to load your app from a URL hosted by your computer instead of just reading files on the device, setting up live-reload for hardware devices can be tricky.Īs with regular device deploys, you will need a cable to connect your device to your computer. Live Reload can also be used with Capacitor and Cordova to provide the same experience on virtual and hardware devices, which eliminates the need for re-deploying a native binary. With ionic serve, Live Reload just refers to reloading the browser when changes are made. This is particularly useful for developing using hardware devices. Using the Live Reload option will reload the browser or Web View when you change your app's code in your development environment.
0 kommentar(er)
