search

ProgressNS / sidekick-feedback

This repository is for feedback regarding NativeScript Sidekick. Use the issues system here to submit feature requests or vote for existing ones.
45 stars 9 forks source link

Version: 1.10.3-v.2018.6.26.1 (latest) Can no longer get debug to run #220

Closed mrwrighty closed 6 years ago

mrwrighty commented 6 years ago

Please, provide the details below:

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

Yes

Tell us about the problem

Since upgrading to the latest version I am having trouble running the debug console. I have tried deleting the app, re-compiling with Start Debugger, Tried clicking the Bug icon. Each time it errors telling me the App is not installed or not built with debugging enabled, even though Build Configuration is Debug, Start Debugger is Ticked.

Which platform(s) does the issue occur on?

iOS at the moment, haven't tried Android.

Provide the following version numbers that the issue occurs with:

Version: 1.10.3-v.2018.6.26.1 (latest) Nativescript 4.1.0

You can obtain the requested information by following the steps outlined below.

  • In NativeScript Sidekick
    Launch Sidekick and select Help → About from the top menu
  • In NativeScript Sidekick for Visual Studio 2017
    Launch Visual Studio and inspect the NativeScript Sidekick output in the Output window.

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

  1. Start the application ..
  2. Open Application
  3. Run on Device with debug options set.

Does this issue happen every time?

Yes

Send the client logs

The client logs can help us identify what is causing the issue. You can create a gist with the app logs.

You can access the logs by following the steps outlined below.

  • In NativeScript Sidekick
    Launch Sidekick and select Help → Show Logs from the top menu.
  • In NativeScript Sidekick for Visual Studio 2017
    Launch Visual Studio and select Sidekick → Show Logs from the main menu.
mrwrighty commented 6 years ago

Oddly after closing Nativescript SideKick, re-compiling the app and letting it run, clicking the Bug icon did load the debug console, but seems hit and miss.

tsvetie commented 6 years ago

Hey @mrwrighty,

Let me explain what happened. When you run your application on the device, we try starting it as soon as we deploy it. However, in order to achieve this for an iPhone, the device needs to have a mounted developer disk image. Otherwise, we cannot start the application automatically. You should have a message in the Output, similar to the following:

Unable to start application org.nativescript.testdebug on device 2761bcbb03698a1ccb2fa30cdc6190ad41c1dd6d. Try starting it manually.

This alone does not lead to any problems - at this point, the application has been deployed on the device successfully and LiveSync is enabled. The only step that failed was that we could not automatically start the application on the device.

Now, in order to start the debugger for a given application, the application should be built in Debug, should be deployed on the device and it should be running. In your case, since the application is not running, starting the debugger fails. You can start the application manually and then use the Bug icon to attach the debugger.

ggarabedian commented 6 years ago

Closing the issue due to inactivity. Please, consider opening a new issue if you continue to experience the problem with the latest version of NativeScript Sidekick.