You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Did you verify whether this issue has already been reported here?
No
Tell us about the problem
When you click run on device there is simply no way to kill or stop the process. Settings like WebPack are hence stuck saying You cannot enable, disable or configure the webpack option while LiveSync is active for any connected device. Before you can make any changes to webpack, you need to stop the LiveSync for all devices.
Which platform(s) does the issue occur on?
Multiple
Provide the following version numbers that the issue occurs with:
NativeScript Sidekick Desktop
NativeScript CLI: latest
Tell us how to recreate the issue in as much detail as possible
Start the application ..
... You can never stop it 🗡
Does this issue happen every time?
Yes
The text was updated successfully, but these errors were encountered:
You are absolutely right. The only way that you can currently stop LiveSync is to close the app in Sidekick (go to Recent apps) or disconnect and connect the device. It is not a very good solution to ask of our users to use either of these options as a permanent solution, so we added a task to add a Stop LiveSync button somewhere in the UI. We are currently focusing on other exciting features, but we should get to this one in the next couple of months.
Did you verify whether this issue has already been reported here?
No
Tell us about the problem
When you click run on device there is simply no way to kill or stop the process. Settings like WebPack are hence stuck saying
You cannot enable, disable or configure the webpack option while LiveSync is active for any connected device. Before you can make any changes to webpack, you need to stop the LiveSync for all devices.
Which platform(s) does the issue occur on?
Multiple
Provide the following version numbers that the issue occurs with:
Tell us how to recreate the issue in as much detail as possible
Does this issue happen every time?
Yes
The text was updated successfully, but these errors were encountered: