-
-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Cannot read property 'StopWatching' of undefined" #832
Comments
@arnohovhannisyan Can you look into this ? |
@shanalikhan sure |
@ActionCactus Is this happening constantly, or did it only happen once? |
It was constant and virtually instantaneous every time. I used multiple gists (in between resetting settings, of course) and tried with numerous code-sync settings (ranging from just a configured gist to multiple settings). As mentioned in the bug report I did revert to 3.2.7 and the problem doesn't exist with that version. |
Once I have a fix, will you be able to test it? |
Yeah, sure |
I met it when I try to use shift +alt + U to set Token Cannot read property 'StopWatching' of undefined |
@eojina If you are getting errors, create an issue and show the error. This way it can get fixed, and you won't get annoyed. |
@arnohovhannisyan This appears to be working, but I may have more info for you. To test the attachment you gave me I reset extension settings for code-sync and then uninstalled the extension. After that I reinstalled the extension from scratch and simply ran "Sync: Download Settings" without setting up a gist (previously this was a scenario which would trigger the error filed). Things worked fine...When I filed the issue I had only just installed code-settings-sync on this machine for the first time (having installed elsewhere before). Could the issues be related? Of course when I installed the package you gave me ( |
@ActionCactus I'm glad it worked, and thanks for testing!
I'm pretty sure that this just had to do with the auto-upload service being instantiated after the call. |
@shanalikhan I made a PR fixing this issue. |
I can confirm that a simple reinstall (uninstall, reload app, install extension again) fixes the problem. |
* Use handler methods to check if autoUploadService exists * Update incorrect function call * Use await before calling handlers
I just manually restarted VS Code and it fixed this issue. Didn't have to uninstall or reinstall or anything exotic like that. |
Can confirm: fresh install of VS Codium (VS Code without Microsoft's modifications), downloaded |
it work after restarted. |
Name: Settings Sync I have a same problem,and I try this:
but it doesn't work. I get same result. |
Have the same problem on new installation. After VSCode have been restarted problem was resolved. |
Same problem. Restart of VSCode fixed it with the 3.2.8 build already installed. |
I've just installed and got this error too. Restarting seemed to have solved this. |
I got this issue too, I was setting up for the first time ever and it threw an error like this. I was using VS Code 1.33.1. |
* Use handler methods to check if autoUploadService exists * Update incorrect function call * Use await before calling handlers
Released |
🐛 Describe the bug
When downloading
🌴 Visual Studio Code Version : 1.33.0
🌴 Code Settings Sync Version : 3.2.8
🌴 Standard or Insiders : Standard?
🌴 OSS or Portable : OSS?
🌴 Operating System : Win10
🌴 Occurs On: Download
🌴 Proxy Enabled: No
🌴 Gist Id: (irrelevant, tested with multiple valid and invalid tokens)
📰 To Reproduce
Steps to reproduce the behavior:
sync.gist
property in VS Code settingsSync: Download Settings
💪 Expected behavior
A successful synchronization of settings or a more meaningful, user-facing error.
📺 Console Error Log
📺 Additional context
I'm not well-versed in typescript and I don't know much about how async/promises work but the error occurs almost instantaneously after running the command which leads me to believe this is related to the
globalCommonService.autoUploadService.StopWatching()
call inSync.download
. I looked at the instantiation code and couldn't see anything obvious but perhaps the problem is there?I originally installed 3.2.8 from the VS-Code Marketplace but it looks like the latest tag you have here is 3.2.7. I installed 3.2.7 specifically in VS Code and the problem doesn't exist there.
The text was updated successfully, but these errors were encountered: