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

Problem installing and running standalone and plugin Sidekick on Win7 x64 machine. #251

Closed rob-j47 closed 6 years ago

rob-j47 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

I have NativeScript CLI installed and running fine, it passes the tns doctor checks. I created a project from a template. I did a build, deploy and run on a connect Android device. All works fine.

I have issued the tns proxy command and there is NO proxy configured. I have successfully run the tns login command and logged in with my Telerik account.

I have tried to install and run both NativeScript Sidekick and NativeScript Sidekick plugin in VS2017. I do not have any success.

When I click on the standalone Sidekick app, it opens to a dialog box. Although I see the application in the Task Manager, I have a hidden / blank window. I have left this dialog open for over 4 hours but have never successfully launched the application. Uninstall / reinstall has no effect.

I tried installing the plugin for VS2017. I have VS2017 Enterprise. I can go to new solution, choose NativeScript project, choose a templates, give project a name and start to create the project. After an hour or so VS2017 is locked up hard with the Sidekick dialog. The only way to abort is killing VS2017 from the task manager.

Which platform(s) does the issue occur on?

_iOS/Android/Both NOT APPLICABLE
Windows 7 Professional, Service Pack 1, x64. 32GB memory.

Provide the following version numbers that the issue occurs with:

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

I cannot run the Sidekick (standalone) to launch any kind of menu or about boxes. I pulled the plugin version from VS2017 About box. CLI version is as reported by tns --version.

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

Standalone:

  1. Start the application.
  2. Dialog box appears but then turns completely transparent/invisible. Sometimes switching with Alt-Tab key to the application will show the dialog, most times not though.
  3. Wait 4 hours while nothing happens.
  4. Kill app from Task manager after it is apparent nothing is ever going to happen.
  5. This happens all the time.

VS2017 Plugin

  1. File, New Project
  2. NativeScript, General, Javascript.
  3. Choose Tab Navigation project template.
  4. Browse to c:\temp\NativeScript
  5. Enter project name "Test1"
  6. Click OK
  7. Dialog with no frame or buttons appears.
  8. Folder for project is created in correct location.
  9. VS2017 is now locked up until killed with the Task Manager, no way to cancel or about, no modal dialog to switch to. No pop-up error or message in Output tab of VS.

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.

I cannot run the Sidekick (standalone or plugin) to launch any kind of menu or about boxes. Your log files should not be in hidden AppData folder (which is where I found them) - tell me which ones you need and I will reinstall, try to run and get them and upload them.

Thanks in advance for your assistance,

Rob

ggarabedian commented 6 years ago

Hello @rob-j47,

The reported behavior might be related to your proxy configuration or an antivirus program that blocks some of the requests made by Sidekick. To avoid speculating as to what is causing the issue, I would ask you to share the logs. As you have already found out they are located in the AppData folder, which is the location where most applications place their cache, configuration and log files. I understand that in your case those files are hard to discover, but through the UI interface they can be accessed quite easily. Here are the locations of the logs and which files you should share.

rob-j47 commented 6 years ago

Garo,

Thanks for responding. I found the logs you requested. I also included a SquirrelUpdate log and some screen grabs taken during the install / run process. I zipped them all up and attached a zip file to this post.

The problem was indeed an antivirus issue. I am running Kaspersky Total Security 17.0.0.611 and it includes a system wide proxy of all traffic in and out of the machine. With it disabled I had a much better experience. I guess the issue then is why the software locks up and can not display any dialogs or messages to the user due to this. Also, the software does not time out in a reasonable amount of time, so the "lockup" is the most frustrating part of it all. Watching carefully it appears that the error occurs while checking if a proxy exists, I think if it skipped and just made it's connections this step it would be fine. I run proxy tools, like Fiddler4 and it happily daisy chains itself in line with the Kaspersky software. No other software I run seems to mind or be aware of the proxy at all. I tried configuring an exclusion in Kaspersky for the Sidekick and Sidekick VS extension but I might not chosen the correct location as it had no affect.

I would be glad to run any test program you can devise and collect the necessary data to improve this aspect of the software.

Thanks, Rob NativeScript_Issue251.zip

rob-j47 commented 6 years ago

Just bumping this thread. Turning off my antivirus completely (including all network monitoring) and Sidekick still does not run on Win7 x64. Dialog box is there but hidden. Running Node command prompt "tns doctor" reports all is well. NativeScriptSidekick shows up in task manager, but it cannot display modal window for some reason. Looking in AppData folders I see it downloaded a new version, right now I think it is asking for me to update something but I cannot see full dialog to click and proceed.

I have running on my personal Win10x64 box but would like to get this going on my development machine.

Rob

ggarabedian commented 6 years ago

Hello Rob,

Thank you for sharing the requested logs and for taking the time to capture images of the issue. My apologies for the delayed response, I was left under the impression that disabling the antivirus works out for you.

We were not able to reproduce the described behavior when testing locally and we cannot find any error messages in the provided logs that would explain this behavior. The only error is the "Error: self signed certificate in certificate chain" , which might be related to the proxy, or to the Fiddler instance you have running (in case you had it running while using Sidekick). If you were not running Fiddler at this moment, you could try setting the NODE_TLS_REJECT_UNAUTHORIZED variable to 0. Below are the steps on how you can achieve this: 1) Open the Environment Variables window. To fastest way to do this is to type "env" in the Windows 10 search bar and select "Edit environment variables for your account". 2) Select New under "User variables for username". 3) For Variable name, enter NODE_TLS_REJECT_UNAUTHORIZED. 4) For Variable value, enter 0. 5) Click OK.

If the above does not help, can you please enable the verbose logging for Sidekick and share the produced logs again. Here are the steps to achieve that: 1) Ensure that Sidekick is not running (in the task manager as well) and delete the old files in %appdata%\NativeScriptSidekick\Logs. 2) Navigate to %appdata%/npm/node_modules/nativescript/config and open the config.json file that is in this folder. 3) Change "DEBUG": false to "DEBUG": true. 4) Start Sidekick, reproduce the problem and then completely stop Sidekick (from the task manager). 5) Send us the newly created log files

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.