Device Build Hangs after (False) 'Failed to Uninstall'

[EdJones]

Please, provide the details below:

On deploying to my iPhone 8 (iOS 12), build downloads to Windows, and begins installation but gives error
Failed to uninstall com.edwincjones.reading on device with identifier...
However, the previous version (a TestFlight install) was actually uninstalled.

There should be a way to stop this and begin installation without closing and restarting SideKick..

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

_Yes

Tell us about the problem

Give us a concise description of the feature you suggest or the issue you report.

Would be nice if app did not just stop there. If it does hang, shoukd be a way to restart install without closing and restarting SideKick.

Which platform(s) does the issue occur on?

_iOS

_Windows/

Provide the following version numbers that the issue occurs with:

• **NativeScript Sidekick: 1.19.2-v-2019.11.18.2
• **NativeScript CLI: 6.2.1
• **CLI extension nativescript-cloud: 1.19.3
• **CLI extension nativescript-starter-kits: 0.3.5

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

1. Start the application ..
2. Cloud build for deploy to device

Does this issue happen every time?

Not sure

Send the client logs

_
Download step completed. [19-11-24 14:57:34.977] (CLI) The result of Cloud build of 'C:\Sites\ScienceOfReading', platform: 'iOS', configuration: 'Debug' successfully downloaded. OutputFilePath: C:\Sites\ScienceOfReading\.cloud\ios\device\ScienceOfReading.ipa [19-11-24 14:57:37.001] (CLI) Installing on device 8e65bcxxxxx... [19-11-24 14:57:39.058] (CLI) Failed to uninstall com.edwincjones.reading on device with identifier 8e65bcxxxxx...

[EdJones]

Update: This is still a fairly annoying issue.
Most of my other connectivity issues have (largely) gone away, either after the 6.3.2 and 6.3.3 updates, or with Frontier finally giving us somewhat-steady service, or with removing a bunch of other apps from my test device. But this one consistently appears.

I don't even mind that it gets this error so much, as that Sidekick must be completely closed, then restarted, then run the test again.