
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2023 08:50 AM
I've been using the ServiceNow VS Code extension for years and love it. As of yesterday, the extension stopped working and I see this message when I toggle the developer tools with the help menu.
Activating extension 'ServiceNow.now-vscode' failed: Cannot find module 'keytar'
If I try to activate the Extension (cmd-shift-p Activate Now Extension), I get this error.
I did make a few changes yesterday to my system and they may be related but I'm not finding any solutions for this on the web, communities, etc. Here is my system details and what I've done recently that may be related to my issue.
- I upgraded my Macmini yesterday MacOS to Sonoma yesterday. I also restarted VS Code as it asked me to update as well. Therefore, my system is fully up to date with latest MacOS, VS Code, the SN Extension and the extension dependencies.
- I completely removed VS Code from my system and reinstalled. Still getting same error.
- I completely uninstalled extensions and reinstalled. Still getting same error.
- Version of Extension: ServiceNow® Extension for VS Codev1.6.1
- Version of VS Code:Version: 1.83.0 (Universal)
Here is a very interesting detail as well. I have a Macbook Pro computer too and work on that just the same. I did all the exact same upgrades on my Macbook Pro that I did on my Macmini. However, my Macbook Pro does NOT have this problem after the upgrade. That is, the SN VS Code extension works perfectly on my Macbook Pro while it's broken on my Macmini. Any help is greatly appreciated.
Todd
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2023 12:06 PM
I started getting the error after VScode updated to its September release. Once I installed the August 2023 version the extension started working again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2023 08:55 AM
@Tobias Persson_ I can't give your exact date but we are planning to fix and release a working extension by November month.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2023 05:46 AM - edited 12-07-2023 05:49 AM
Hi @Todd O ,
Thrilled to announce the arrival of our latest update, Vscode ServiceNow extension (v1.7.0), where we've tackled that pesky issue head-on!
https://marketplace.visualstudio.com/items?itemName=ServiceNow.now-vscode
Please mark the answer correct/helpful based on impact.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2023 11:51 AM
Hello,
I found something similar in the below post:-
Please mark answer correct/helpful based on impact.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2023 03:06 PM
Hi, I reviewed the solution as well as requirements and dependencies with the CLI. I found that the CLI is not a requirement to use the VS Code plugin. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2023 12:01 PM
Heyo - I starting getting the same error after VScode updated to its September 2023 release. Installing the August 2023 version of vscode seem to fix the issue for now

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2023 03:22 PM - edited 10-05-2023 03:47 PM
Hi @chrisf, thanks for suggestion. I was trying to avoid that but it looks like my only option at this point. I just downloaded the older version and it's working. Therefore, something is broken with the SN Plugin when using VS Code 1.83 for some reason. I'll leave this post open for a bit yet before marking solution. I'm hoping someone will have a root cause and fix - maybe from the plugin dev team. Avoiding the upgrade is a temporary solution. Thanks again for your time.