(v 2) Error is: Could not start device session

[EdJones]

Please, provide the details below:

Did you verify whether this issue has already been reported here?

_Yes

Tell us about the problem

Could not start device log.log

This is the next step in the same morning work session as Issue #466. What's different is that all those communications errors are not showing up in the logs. It just will not run:
(CLI) Unable to apply changes on device: 8e65bc83cf810add8e7a0c99b2132b8304e02861. Error is: Failed to install C:\Sites\ScienceOfReading\.cloud\ios\device\ScienceOfReading.ipa on device with identifier 8e65bc83cf810add8e7a0c99b2132b8304e02861. Error is: Could not start device session. [20-01-22 08:46:41.785]
Tried four times now. Restarted Sidekick. Deleted app from phone. Rebooted Windows machine. Keeps doing it.

Note that only change to my code was to reverse the order of two layout items.

Which platform(s) does the issue occur on?

iOS/Android/Both (if applicable, tell us the specific version of the platform)

Windows/macOS/Linux/Multiple (if applicable, tell us the specific version of the platform)

Provide the following version numbers that the issue occurs with:

• NativeScript Sidekick:
• NativeScript CLI:
• CLI extension nativescript-cloud:
• CLI extension nativescript-starter-kits:

How to obtain this information is explained in the Gather information about your development environment section.

Tell us how to recreate the issue in as much detail as possible

1. Start the application ..
2. ...

Does this issue happen every time?

No_

Send the client logs

Could not start device log.log

[NickIliev]

@EdJones this issue is most likely closely related to the other issues opened recently (like #466). A

Can you verify that you are having a stable connection to the device (no SIdekick involved - just USB connection to your Windows environment) - as noted in another issue, sometimes the connection might be lost due to faulty USB cable? Here is a logged issue that illustrates when the above error is usually appearing.

[EdJones]

@NickIliev I believe my cable/connection is OK. I have a couple different cables, one just out of the Apple box, and one of a make I find more reliable than Apple.

Similar work issues have been the norm for me since I started using Sidekick more or less daily last August.