{ "id": "171853", "key": "TIMOB-26166", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": null, "resolutiondate": null, "created": "2018-06-27T21:19:22.000+0000", "priority": { "name": "None", "id": "6" }, "labels": [], "versions": [ { "id": "14826", "description": "Release 5.1.0-remaining iOS9 features, Android M features", "name": "Release 5.1.0", "archived": false, "released": true, "releaseDate": "2015-11-20" } ], "issuelinks": [], "assignee": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "updated": "2020-09-28T14:35:43.000+0000", "status": { "description": "This issue is being actively worked on at the moment by the assignee.", "name": "In Progress", "id": "3", "statusCategory": { "id": 4, "key": "indeterminate", "colorName": "yellow", "name": "In Progress" } }, "components": [], "description": "h5. Steps to reproduce:\r\n1. Install studio versions mentioned in environment.\r\n2. After studio launches wait till it checks available update.\r\n3. Make sure you already have appc CLI installed.\r\n\r\nh5. Actual result:\r\n1. Studio will show update available for CLI with version {{N/A}}.\r\n2. Clicking install will error with:\r\n{code}\r\n!ENTRY com.aptana.core 1 0 2018-06-27 13:30:21.261\r\n!MESSAGE (Build 5.1.0.201806130735) [INFO] com.aptana.core/debug/shell/output Process Error Output:\r\nmodule.js:538\r\n throw err;\r\n ^\r\n\r\nError: Cannot find module 'chalk'\r\n at Function.Module._resolveFilename (module.js:536:15)\r\n at Function.Module._load (module.js:466:25)\r\n at Module.require (module.js:579:17)\r\n at require (internal/module.js:11:18)\r\n at Object. (C:\\Users\\Tester\\AppData\\Roaming\\npm\\node_modules\\appcelerator\\bin\\appc:11:13)\r\n at Module._compile (module.js:635:30)\r\n at Object.Module._extensions..js (module.js:646:10)\r\n at Module.load (module.js:554:32)\r\n at tryModuleLoad (module.js:497:12)\r\n at Function.Module._load (module.js:489:3)\r\n{code}\r\n3. This messes up the installed appc cli installation on my machine & now running {{appc -v}} gives me the error above.\r\n4. Also because of this what I am seeing is my android SDK on the dashboard does not get detected even though studio platform config shows everything is fine. I also see the error in studio console below:\r\n{code}\r\n[\"Unable to set property 'sdkInfo' of undefined or null reference\",\"https://appc-studio.appcelerator.com/?p=W&fg=000000&uid=null&bg=ffffff&ch=f0f0f0&v=5.1.0.201806130735&id=e5bfbe3c-fb49-4c5c-b8ba-2367290df534&subscription=-1&nl=en_US&ts=1530134459624\",198]\r\n{code}\r\n\r\nh5. Expected results:\r\n1. Studio should not prompt for appc CLI update when latest CLI version is already installed.", "attachment": [ { "id": "65305", "filename": "install.PNG", "author": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "created": "2018-06-28T14:49:15.000+0000", "size": 25780, "mimeType": "image/png" }, { "id": "65302", "filename": "studio_cli1.PNG", "author": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2018-06-27T21:18:38.000+0000", "size": 23278, "mimeType": "image/png" }, { "id": "65303", "filename": "studio.PNG", "author": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2018-06-27T21:18:30.000+0000", "size": 36815, "mimeType": "image/png" } ], "flagged": false, "summary": "5.1.0 RC Studio keeps on prompting CLI update even though CLI is installed & messes up current installation", "creator": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "Windows 10\r\nStudio: 5.1.0.201806130758 32 bit & 5.1.0.201806130735 64 bit\r\nJava 8 & 10.0.1\r\nCLI: 7.0.4\r\nAppc NPM : 4.2.13", "comment": { "comments": [ { "id": "438783", "author": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "body": "I experienced the same issue but with a different module error.\r\n\r\n{noformat}\r\nC:\\Users\\Josh\\appc\\test4>appc info\r\nmodule.js:538\r\n throw err;\r\n ^\r\n\r\nError: Cannot find module 'npm-install-checks'\r\n at Function.Module._resolveFilename (module.js:536:15)\r\n at Function.Module._load (module.js:466:25)\r\n at Module.require (module.js:579:17)\r\n at require (internal/module.js:11:18)\r\n at Object. (C:\\Users\\Josh\\AppData\\Roaming\\npm\\node_modules\\appcelerator\\lib\\install.js:24:18)\r\n at Module._compile (module.js:635:30)\r\n at Object.Module._extensions..js (module.js:646:10)\r\n at Module.load (module.js:554:32)\r\n at tryModuleLoad (module.js:497:12)\r\n at Function.Module._load (module.js:489:3)\r\n{noformat}\r\n", "updateAuthor": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "created": "2018-06-27T21:30:16.000+0000", "updated": "2018-06-27T21:30:16.000+0000" }, { "id": "438799", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "I tried reproducing this issue on Windows 10, with no CLI-7.0.4 installed. \r\nCLI installation always hangs for me, while fetching appcd module. Of the 5 attempts I made (both using windows command utility and using Studio), it always gets stuck on fetching appcd.\r\n\r\nThis for sure has got nothing to do with Studio, but an issue in installing dependent modules.\r\nWill try using a different internet connection and see if it goes through. \r\n", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-06-28T06:56:40.000+0000", "updated": "2018-06-28T06:56:40.000+0000" }, { "id": "438806", "author": { "name": "ssekhri", "key": "ssekhri", "displayName": "Satyam Sekhri", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Could not reproduce with following scenarios:\r\nEnv:\r\nOS: Win 10Pro\r\nStudio: 5.1.0.201806130758 (32 bit and 64 bit)\r\nSDK: 7.2.0.GA\r\nAppc CLI: 7.0.4\r\nJDK: 9.0.4, 10.0.1(64 bit) and 1.8.0_131(32 bit)\r\nNode: 8.9.1\r\nNPM: 5.5.1, 6.1.0\r\n\r\n1. Deleted all instance of appc core and npm installation from the system. Studio installer installed the 7.0.4 CLI. Upon launch and re-launch it did not prompt for CLI update.\r\n2. Again deleted all instance of appc core and npm installation from the system. Installed appc npm and core from command line. Installed studio. No CLI update shown upon studio launch\r\n3. With APPC CLI 7.0.2 already installed. Installed studio. Upon launch there was a prompt shown for CLI 7.0.4 update available. Updated CLI from studio. Again checked for updates. No updates shown. Restart studio. No updates shown", "updateAuthor": { "name": "ssekhri", "key": "ssekhri", "displayName": "Satyam Sekhri", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2018-06-28T08:11:21.000+0000", "updated": "2018-06-28T08:11:21.000+0000" }, { "id": "438812", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "I guess the first issue I mentioned was due to network. I could install CLI 7.0.4 via windows cmd util and via studio.\r\nThe Studio updater too worked fine for me, using npm 5.5.1 and 6.1.0, on Studio RC 5.1.0.201806130758.\r\n\r\nTrying to see if we can break installed 7.0.4 CLI such that I get a pop-up on Studio to install 7.0.4. \r\nWill update my findings as soon as I succeed in reproducing this exact case.", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-06-28T09:41:11.000+0000", "updated": "2018-06-28T09:41:11.000+0000" }, { "id": "438819", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "I tried reproducing the issue by deleting few files from the installed CLI 7.0.4 such that Studio finds the installed 7.0.4 missing.\r\nWhen I chose to update/install 7.0.4 from Studio, it did install CLI 7.0.4 without any issue in downloading/installing node modules.\r\n\r\nI suspect that, it could be an issue with npm installation while node package manager tried to fetch those modules (chalk and npm-install-checks). And its intermittent.\r\n\r\n[~fmiao], could you please take a peek? ", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-06-28T11:33:39.000+0000", "updated": "2018-06-28T11:33:39.000+0000" }, { "id": "438821", "author": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "body": "[~ppedduri] I am intermittently getting the issue but only when installing studio, I seem to get the error around 20% of the time, I just got it again. \r\n\r\n!install.PNG|thumbnail! \r\n\r\nI have the latest tools installed but studio is still trying to install the CLI", "updateAuthor": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "created": "2018-06-28T14:49:31.000+0000", "updated": "2018-06-28T14:51:04.000+0000" }, { "id": "438844", "author": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "body": "[~jlongton], any issue installing/using CLI through command line on Windows? ", "updateAuthor": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "created": "2018-06-28T23:02:42.000+0000", "updated": "2018-06-28T23:02:42.000+0000" }, { "id": "438847", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "[~jlongton]/[~lchoudhary], please try installing CLI 7.0.4 via CLI and let us know your observations. \r\nSince this issue is intermittent, please run the installation/uninstallation multiple times to see if you fall in same npm installation issue for modules *chalk* and *npm-install-checks*", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-06-28T23:38:19.000+0000", "updated": "2018-06-28T23:38:19.000+0000" }, { "id": "438890", "author": { "name": "ssekhri", "key": "ssekhri", "displayName": "Satyam Sekhri", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~fmiao] I just checked on the PC on which [~lchoudhary] was facing the issue. The same issue actually is shown even when trying to use appc commands from terminal.\r\n{code}\r\nC:\\Users\\Tester>appc\r\nmodule.js:538\r\n throw err;\r\n ^\r\n\r\nError: Cannot find module 'chalk'\r\n at Function.Module._resolveFilename (module.js:536:15)\r\n at Function.Module._load (module.js:466:25)\r\n at Module.require (module.js:579:17)\r\n at require (internal/module.js:11:18)\r\n at Object. (C:\\Users\\Tester\\AppData\\Roaming\\npm\\node_modules\\appcelerator\\bin\\appc:11:13)\r\n at Module._compile (module.js:635:30)\r\n at Object.Module._extensions..js (module.js:646:10)\r\n at Module.load (module.js:554:32)\r\n at tryModuleLoad (module.js:497:12)\r\n at Function.Module._load (module.js:489:3)\r\n{code}\r\n\r\nHence when we check for updates in studio it tries to run appc command in the background and the error is returned.", "updateAuthor": { "name": "ssekhri", "key": "ssekhri", "displayName": "Satyam Sekhri", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2018-07-02T02:25:29.000+0000", "updated": "2018-07-02T02:25:29.000+0000" }, { "id": "438896", "author": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "body": "[~ssekhri], from the error, it looks like a broken installation of appc npm. Try reinstalling the npm module. {{npm install appcelerator -g}}.", "updateAuthor": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "created": "2018-07-02T08:01:24.000+0000", "updated": "2018-07-02T08:01:24.000+0000" }, { "id": "438918", "author": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "body": "[~fmiao], [~ppedduri], I only ever experienced this issue when the appc npm was installed with the studio installer, I already had GA but studio is persistent that it is unable to find it and installs it anyway. I don't know if this could be why the module is not installed correctly.\r\n ", "updateAuthor": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "created": "2018-07-02T14:30:28.000+0000", "updated": "2018-07-02T14:31:20.000+0000" }, { "id": "438925", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "[~jlongton], Were you able to run through multiple attempts to install CLI 7.0.4 via terminal(cmd util) and it succeeds always w.r.t. appc npm installation? ", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-07-02T15:49:58.000+0000", "updated": "2018-07-02T15:49:58.000+0000" }, { "id": "438928", "author": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "body": "[~ppedduri] Yes I was able to install the CLI multiple times and appc npm multiple times successfully from cmd, from what I am seeing it is an issue with studio installing the appc npm, I am not able to reproduce this issue other than using studios installer.\r\n\r\n", "updateAuthor": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "created": "2018-07-02T16:02:25.000+0000", "updated": "2018-07-02T16:02:25.000+0000" }, { "id": "438929", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "[~jlongton], thanks for confirming that. Sorry that I had to ask you as we couldn't reproduce this issue locally, with many attempts.\r\nWe will further look into this issue and update here.", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-07-02T16:07:42.000+0000", "updated": "2018-07-02T16:07:42.000+0000" }, { "id": "438932", "author": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~fmiao],[~ssekhri], [~ppedduri], [~jlongton]'s comment above exactly describes what happens. The appc npm installation gets broken yes but only when studio installs it during the studio installation where it forces you to install appc npm even though installed.\r\nTo get out of the broken stage uninstalling & installing appc npm is the only way I have seen which has to be done manually.", "updateAuthor": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2018-07-02T16:19:26.000+0000", "updated": "2018-07-02T16:19:56.000+0000" }, { "id": "438959", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "[~ssekhri] and I just happened to run these scenarios again, with and without 7.0.4 preinstalled and still fail to reproduce this exact issue.\r\n\r\nFor us, post successful Studio installation it doesn't prompt any update of CLI if 7.0.4 is already available on the machine. \r\nAnd each installation of Studio succeed in installing appcelerator npm, with all dependent modules installed correctly.\r\n\r\n[~lchoudhary], [~jlongton] - in order for us to verify what's causing this issue on your machine (rather, what we are missing) we would need access to your machine.\r\nPlease let us know if we can get into a WebEx call. \r\n\r\nStudio windows-installer invokes the following 2 commands and doesn't seem like causing any breakage \r\n* npm install -g appcelerator\r\n* appcelerator use latest ", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-07-03T08:32:54.000+0000", "updated": "2018-07-03T08:32:54.000+0000" }, { "id": "438999", "author": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "body": "Thanks for sharing system credentials [~lchoudhary]. This surely helped us narrow down the issue.\r\n\r\nI confirm that the issue is not with Appcelerator Studio, but with appc npm.\r\n\r\nPlease follow below steps to reproduce the issue on shared windows machine.\r\n* make sure appc npm is clean. if you see errors the output of command *_$npm ls -g_*, please run *_$npm install -g appcelerator_* and be sure that *_npm ls -g_* doesn't show any errors\r\n* verify that npm is clean, with any appc command. (I 've used a simple *_$appc_* command and it worked fine)\r\n* now run the command *_$npm install -g appcelerator_* again and observe the output (It updates 1 package and adds 1 package this time)\r\n* run any appc command --> it now fails with the same error related to the module '*_chalk_*'\r\n\r\n----\r\n\r\nThe following sequence of commands that I ran (and the respective output) might help in understanding the above steps.\r\n\r\n{quote}C:\\Users\\Tester\\AppData\\Roaming\\npm>appc\r\nmodule.js:538\r\n throw err;\r\n ^\r\n\r\nError: Cannot find module 'chalk'\r\n at Function.Module._resolveFilename (module.js:536:15)\r\n at Function.Module._load (module.js:466:25)\r\n at Module.require (module.js:579:17)\r\n at require (internal/module.js:11:18)\r\n at Object. (C:\\Users\\Tester\\AppData\\Roaming\\npm\\node_modules\\appcelerator\\bin\\appc:11:13)\r\n at Module._compile (module.js:635:30)\r\n at Object.Module._extensions..js (module.js:646:10)\r\n at Module.load (module.js:554:32)\r\n at tryModuleLoad (module.js:497:12)\r\n at Function.Module._load (module.js:489:3)\r\n\r\nC:\\Users\\Tester\\AppData\\Roaming\\npm>npm install -g appcelerator\r\nC:\\Users\\Tester\\AppData\\Roaming\\npm\\appc -> C:\\Users\\Tester\\AppData\\Roaming\\npm\\node_modules\\appcelerator\\bin\\appc\r\nC:\\Users\\Tester\\AppData\\Roaming\\npm\\appcelerator -> C:\\Users\\Tester\\AppData\\Roaming\\npm\\node_modules\\appcelerator\\bin\\appc\r\n+ appcelerator@4.2.13\r\nadded 128 packages and updated 1 package in 2.766s\r\n\r\nC:\\Users\\Tester\\AppData\\Roaming\\npm>appc\r\nAppcelerator Command-Line Interface, version 7.0.4\r\nCopyright (c) 2014-2018, Appcelerator, Inc. All Rights Reserved.\r\n Usage: appc cmd [options]\r\n \r\n\r\nC:\\Users\\Tester\\AppData\\Roaming\\npm>npm install -g appcelerator\r\nC:\\Users\\Tester\\AppData\\Roaming\\npm\\appc -> C:\\Users\\Tester\\AppData\\Roaming\\npm\\node_modules\\appcelerator\\bin\\appc\r\nC:\\Users\\Tester\\AppData\\Roaming\\npm\\appcelerator -> C:\\Users\\Tester\\AppData\\Roaming\\npm\\node_modules\\appcelerator\\bin\\appc\r\n+ appcelerator@4.2.13\r\nadded 1 package and updated 1 package in 1.719s\r\n\r\nC:\\Users\\Tester\\AppData\\Roaming\\npm>appc\r\nmodule.js:538\r\n throw err;\r\n ^\r\n\r\nError: Cannot find module 'chalk'\r\n at Function.Module._resolveFilename (module.js:536:15)\r\n at Function.Module._load (module.js:466:25)\r\n at Module.require (module.js:579:17)\r\n at require (internal/module.js:11:18)\r\n at Object. (C:\\Users\\Tester\\AppData\\Roaming\\npm\\node_modules\\appcelerator\\bin\\appc:11:13)\r\n at Module._compile (module.js:635:30)\r\n at Object.Module._extensions..js (module.js:646:10)\r\n at Module.load (module.js:554:32)\r\n at tryModuleLoad (module.js:497:12)\r\n at Function.Module._load (module.js:489:3)\r\n{quote}\r\n\r\n[~fmiao] Requesting you to investigate further.", "updateAuthor": { "name": "ppedduri", "key": "ppeduri", "displayName": "Prashanth Pedduri", "active": false, "timeZone": "Asia/Singapore" }, "created": "2018-07-04T06:39:06.000+0000", "updated": "2018-07-04T06:39:22.000+0000" }, { "id": "439133", "author": { "name": "amukherjee", "key": "amukherjee", "displayName": "Abir Mukherjee", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~eharris] If you have cycles would you be able to look at this? It seems to be an appc npm bug on Windows only.", "updateAuthor": { "name": "amukherjee", "key": "amukherjee", "displayName": "Abir Mukherjee", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2018-07-11T17:54:07.000+0000", "updated": "2018-07-11T17:54:07.000+0000" }, { "id": "439166", "author": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "body": "I'm struggling to reproduce this, but I'm familiar with the error having seen it on other globally installed packages I use across OSX and Windows when running {{npm install -g}} when I already have the same version of the package installed (which seems to lead to npm re-sorting the package structure or nuking packages for no reason)\r\n\r\nI would not classify this as an error of ours or of the appc cli, it's an error of npm as it controls the validity of that package. There's a few things we could maybe do to \"fix\" this ourselves, in no order:\r\n\r\n# Publish a shrinkwrap with appc-install and hope that npm respects it (I wouldn't really want to do this)\r\n# Upgrade the version of node (and subsequently npm) distributed in Studio, anecdotally I've only ever seen this when using a 5.5.X npm, it's possible the problem doesn't occur in the newer version of npm distributed. An upgrade to 8.10.0 gets us 5.6.0 npm, where this issue might be alleviated.\r\n# Studio only installs the cli components when it knows an upgrade is there for sure (TISTUD-8645), probably not worth the engineering effort\r\n# We document as a known issue with instructions of how to fix manually\r\n# Studio handles that error and attempts to reinstall the package for a user", "updateAuthor": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "created": "2018-07-12T13:02:13.000+0000", "updated": "2018-07-12T13:02:13.000+0000" }, { "id": "456824", "author": { "name": "bitshftr", "key": "bitshftr", "displayName": "Shawn Lipscomb", "active": true, "timeZone": "America/New_York" }, "body": "Same problem persists now, with Studio 6.0.0.0. @Ewan Harris, what are the instructions for fixing this manually?\r\n\r\n{{npm ls -g}} yields this output:\r\nC:\\Users\\Shawn.Lipscomb\\AppData\\Roaming\\npm\r\n`-- appcelerator@5.0.0\r\n +-- ansi-regex@0.2.1\r\n +-- ansi-styles@1.1.0\r\n +-- assert-plus@1.0.0\r\n +-- UNMET DEPENDENCY async@^1.5.0\r\n +-- asynckit@0.4.0\r\n +-- aws-sign2@0.7.0\r\n +-- aws4@1.10.1\r\n +-- bytes@3.1.0\r\n +-- caseless@0.12.0\r\n +-- UNMET DEPENDENCY chalk@0.5.1\r\n +-- chownr@1.1.4\r\n +-- co@4.6.0\r\n +-- UNMET DEPENDENCY debug@^2.1.1\r\n +-- UNMET DEPENDENCY npm-install-checks@^3.0.0\r\n +-- UNMET DEPENDENCY pac-proxy-agent@^3.0.0\r\n +-- UNMET DEPENDENCY progress@1.1.8\r\n +-- UNMET DEPENDENCY request@^2.87.0\r\n +-- UNMET DEPENDENCY semver@^6.0.0\r\n `-- UNMET DEPENDENCY tar@^4.4.4\r\n\r\nnpm ERR! missing: async@^1.5.0, required by appcelerator@5.0.0\r\nnpm ERR! missing: chalk@0.5.1, required by appcelerator@5.0.0\r\nnpm ERR! missing: debug@^2.1.1, required by appcelerator@5.0.0\r\nnpm ERR! missing: npm-install-checks@^3.0.0, required by appcelerator@5.0.0\r\nnpm ERR! missing: pac-proxy-agent@^3.0.0, required by appcelerator@5.0.0\r\nnpm ERR! missing: progress@1.1.8, required by appcelerator@5.0.0\r\nnpm ERR! missing: request@^2.87.0, required by appcelerator@5.0.0\r\nnpm ERR! missing: semver@^6.0.0, required by appcelerator@5.0.0\r\nnpm ERR! missing: tar@^4.4.4, required by appcelerator@5.0.0\r\n", "updateAuthor": { "name": "bitshftr", "key": "bitshftr", "displayName": "Shawn Lipscomb", "active": true, "timeZone": "America/New_York" }, "created": "2020-09-10T15:25:13.000+0000", "updated": "2020-09-10T15:26:39.000+0000" }, { "id": "457052", "author": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "body": "[~bitshftr] I _think_ reinstalling the {{appcelerator}} using {{npm i -g appcelerator}} npm package should fix that error. If that still fails, reinstall Node (I recommend 12.x if you're using newer SDKs i.e. 9+, 10.x if you're still rocking 8.x) and retry", "updateAuthor": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "created": "2020-09-28T14:35:43.000+0000", "updated": "2020-09-28T14:35:43.000+0000" } ], "maxResults": 22, "total": 22, "startAt": 0 } } }