Appium Inspector Windows -Call to ‘switchContext’ failed

I get the below error on Windows Appium Inspector

Call to ‘switchContext’ failed

An unknown server-side error occurred while processing the command. Original error: invalid argument: cannot parse capability: goog:chromeOptions from invalid argument: unrecognized chrome option: androidDeviceSerial

Below is the log

info] e[35m[Chromedriver]e[39m Spawning chromedriver with: /AppData/Local/Programs/Appium Server GUI/resources/app/node_modules/appium/node_modules/appium-chromedriver/chromedriver/win/chromedriver_win32_v83.0.4103.39.exe --url-base=wd/hub --port=8000 --adb-port=5037 --verbose
[debug] e[35m[Chromedriver]e[39m Chromedriver version: ‘83.0.4103.39’
[debug] e[35m[WD Proxy]e[39m Matched ‘/status’ to command name ‘getStatus’
[debug] e[35m[WD Proxy]e[39m Proxying [GET /status] to [GET http://127.0.0.1:8000/wd/hub/status] with no body[debug] e[35m[WD Proxy]e[39m Got response with status 200: {“value”:{“build”:{“version”:“83.0.4103.39 (ccbf011cb2d2b19b506d844400483861342c20cd-refs/branch-heads/[email protected]{#416})”},“message”:“ChromeDriver ready for new sessions.”,“os”:{“arch”:“x86_64”,“name”:“Windows NT”,“version”:“10.0.19044”},“ready”:true}}
[info] e[35m[Chromedriver]e[39m Starting W3C Chromedriver session with capabilities: {
[info] e[35m[Chromedriver]e[39m “capabilities”: {
[info] e[35m[Chromedriver]e[39m “alwaysMatch”: {
[info] e[35m[Chromedriver]e[39m “goog:chromeOptions”: {
[info] e[35m[Chromedriver]e[39m “androidUseRunningApp”: true,
[info] e[35m[Chromedriver]e[39m “androidProcess”: “com.bluebird.mobile”,
[info] e[35m[Chromedriver]e[39m “androidDeviceSerial”: “emulator-5554”
[info] e[35m[Chromedriver]e[39m },
[info] e[35m[Chromedriver]e[39m “goog:loggingPrefs”: {
[info] e[35m[Chromedriver]e[39m “browser”: “ALL”
[info] e[35m[Chromedriver]e[39m }
[info] e[35m[Chromedriver]e[39m }
[info] e[35m[Chromedriver]e[39m }
[info] e[35m[Chromedriver]e[39m }
[debug] e[35m[WD Proxy]e[39m Matched ‘/session’ to command name ‘createSession’
[debug] e[35m[WD Proxy]e[39m Proxying [POST /session] to [POST http://127.0.0.1:8000/wd/hub/session] with body: {“capabilities”:{“alwaysMatch”:{“goog:chromeOptions”:{“androidUseRunningApp”:true,“androidProcess”:“com.bluebird.mobile”,“androidDeviceSerial”:“emulator-5554”},“goog:loggingPrefs”:{“browser”:“ALL”}}}}
[info] e[35m[WD Proxy]e[39m Got response with status 400: {“value”:{“error”:“invalid argument”,“message”:“invalid argument: cannot parse capability: goog:chromeOptions\nfrom invalid argument: unrecognized chrome option: androidDeviceSerial”,“stacktrace”:"Backtrace:\n\tOrdinal0 [0x00489563+2725219]\n\tOrdinal0 [0x00388551+1672529]\n\tOrdinal0 [0x00270359+525145]\n\tOrdinal0 [0x001F82AF+33455]\n\tOrdinal0 [0x001FA4E4+42212]\n\tOrdinal0 [0x001F603E+24638]\n\tOrdinal0 [0x0021BE2A+179754]\n\tOrdinal0 [0x0021BBC7+179143]\n\tOrdinal0 [0x0021CAD0+182992]\n\tOrdinal0 [0x0021CA3D+182845]\n\tOrdinal0 [0x0021A94B+174411]\n\tOrdinal0 [0x00202528+75048]\n\tOrdinal0 [0x002035A0+79264]\n\tOrdinal0 [0x00203539+79161]\n\tOrdinal0 [0x0039D607+1758727]\n\tGetHandleVerifier [0x005A6546+1050150]\n\tGetHandleVerifier [0x005A6291+1049457]\n\tGetHandleVerifier [0x005B10D7+1094071]\n\tGetHandleVerifier [0x005A6B46+1051686]\n\tOrdinal0 [0x00395B06+1727238]\n\tOrdinal0 [0x0039EB7B+1764219]\n\tOrdinal0 [0x0039ECE3+1764579]\n\tOrdinal0 [0x003B4C05+1854469]\n\tBaseThreadInitThunk [0x773CFEF9+2…
[debug] e[35m[W3C]e[39m Matched W3C error code ‘invalid argument’ to InvalidArgumentError
[debug] e[35m[Chromedriver]e[39m InvalidArgumentError: invalid argument: cannot parse capability: goog:chromeOptions
[debug] e[35m[Chromedriver]e[39m from invalid argument: unrecognized chrome option: androidDeviceSerial
[debug] e[35m[Chromedriver]e[39m at errorFromW3CJsonCode (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:780:25)
[debug] e[35m[Chromedriver]e[39m at ProxyRequestError.getActualError (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:663:14)
[debug] e[35m[Chromedriver]e[39m at JWProxy.command (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:272:19)
[debug] e[35m[Chromedriver]e[39m at processTicksAndRejections (internal/process/task_queues.js:97:5)
[debug] e[35m[Chromedriver]e[39m at Chromedriver.startSession (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-chromedriver\lib\chromedriver.js:589:5)
[debug] e[35m[Chromedriver]e[39m at Chromedriver.start (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-chromedriver\lib\chromedriver.js:520:7)
[debug] e[35m[Chromedriver]e[39m at AndroidUiautomator2Driver.setupNewChromedriver (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:472:3)
[debug] e[35m[Chromedriver]e[39m at AndroidUiautomator2Driver.startChromedriverProxy (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:221:10)
[debug] e[35m[Chromedriver]e[39m at AndroidUiautomator2Driver.switchContext (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:128:5)
[debug] e[35m[Chromedriver]e[39m at AndroidUiautomator2Driver.setContext (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:54:3)
[error] e[35m[Chromedriver]e[39m Chromedriver exited unexpectedly with code null, signal SIGTERM
[debug] e[35m[Chromedriver]e[39m Changed state to ‘stopped’
[error] e[35m[Chromedriver]e[39m invalid argument: cannot parse capability: goog:chromeOptions
[error] e[35m[Chromedriver]e[39m from invalid argument: unrecognized chrome option: androidDeviceSerial
[debug] e[35m[W3C (6613ed62)]e[39m Encountered internal error running command: Error: invalid argument: cannot parse capability: goog:chromeOptions
[debug] e[35m[W3C (6613ed62)]e[39m from invalid argument: unrecognized chrome option: androidDeviceSerial
[debug] e[35m[W3C (6613ed62)]e[39m at Object.errorAndThrow (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:94:35)
[debug] e[35m[W3C (6613ed62)]e[39m at Chromedriver.start (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-chromedriver\lib\chromedriver.js:541:11)
[debug] e[35m[W3C (6613ed62)]e[39m at AndroidUiautomator2Driver.setupNewChromedriver (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:472:3)
[debug] e[35m[W3C (6613ed62)]e[39m at AndroidUiautomator2Driver.startChromedriverProxy (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:221:10)
[debug] e[35m[W3C (6613ed62)]e[39m at AndroidUiautomator2Driver.switchContext (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:128:5)
[debug] e[35m[W3C (6613ed62)]e[39m at AndroidUiautomator2Driver.setContext (\AppData\Local\Programs\Appium Server GUI\resources\app\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:54:3)
[info] e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session/6613ed62-8662-44db-8dbb-64c6a0ece883/context e[39me[31m500e[39m e[90m2153 ms - 911e[39m
[info] e[35m[HTTP]e[39m e[90me[39m[info] e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/session/6613ed62-8662-44db-8dbb-64c6a0ece883/timeoutse[39m