vscode: Javascript Error when trying to launch Exploration version
Does this issue occur when all extensions are disabled?: Yes/No Yes
-
VS Code Version: Latest Exploration Version
-
Version 1.58.0-exploration (1.58.0-exploration)
-
e2f8e14895669fd22065879145825338f4c19cf5
-
2021-06-29T14:33:19.229Z
-
OS Version: MacOS 11.4
Steps to Reproduce:
- Attempt to launch latest Exploration version after update
- Crash dialog:
Uncaught Exception:
Error: submitURL must be specified when uploadToServer is true
at CrashReporter.start (electron/js2c/browser_init.js:41:472)
at configureCrashReporter (/Applications/Visual Studio Code - Exploration.app/Contents/Resources/app/out/main.js:2:1779)
at Object.<anonymous> (/Applications/Visual Studio Code - Exploration.app/Contents/Resources/app/out/main.js:1:851)
at Module._compile (internal/modules/cjs/loader.js:1078:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1108:10)
at Module.load (internal/modules/cjs/loader.js:935:32)
at Module._load (internal/modules/cjs/loader.js:776:14)
at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
at Object.<anonymous> (electron/js2c/browser_init.js:193:3237)
at Object../lib/browser/init.ts (electron/js2c/browser_init.js:193:3441)
at __webpack_require__ (electron/js2c/browser_init.js:1:128)
at electron/js2c/browser_init.js:1:1200
at electron/js2c/browser_init.js:1:1267
at NativeModule.compileForInternalLoader (internal/bootstrap/loaders.js:283:7)
at NativeModule.compileForPublicLoader (internal/bootstrap/loaders.js:225:10)
at loadNativeModule (internal/modules/cjs/helpers.js:35:9)
at Module._load (internal/modules/cjs/loader.js:747:15)
at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 18 (5 by maintainers)
Thanks for the report, please start with
--disable-crash-reporter
as temporary workaround.Issue persists in 1.59.0. Not sure why this was closed. Are there product.json changes that need to be done for those using open source builds to resolve this? Wasn’t problematic prior to 1.59.0 (using 1.58.0 stable).
From 1.59.0: