# Appium UI inspector not working after xcode upgrade **URL:** \ **Category:** Support\ **Created:** [January 4, 2022, 11:47am UTC](https://discuss.appium.io/t/appium-ui-inspector-not-working-after-xcode-upgrade/35353 "2022-01-04T11:47:27Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ShruthiSowmya](https://discuss.appium.io/user_avatar/discuss.appium.io/shruthisowmya/32/8665_2.png) [@ShruthiSowmya](https://discuss.appium.io/u/ShruthiSowmya)\ **Post date:** [January 4, 2022, 11:47am UTC](https://discuss.appium.io/t/appium-ui-inspector-not-working-after-xcode-upgrade/35353/1 "2022-01-04T11:47:27Z")
UI inspector does not load after xcode upgrade on an iOS 15 real device. Please find logs below: [WD Proxy] Proxying [GET /screenshot] to [GET [http://127.0.0.1:8100/session/58E3A011-8F89-45C6-B83F-15A045F3A0B0/screenshot](http://127.0.0.1:8100/session/58E3A011-8F89-45C6-B83F-15A045F3A0B0/screenshot)] with no body [WD Proxy] Got response with status 500: {“value”:{“error”:“unknown error”,“message”:"-[XCUIScreen screenshotDataForQuality:rect:error:]: unrecognized selector sent to instance 0x281ced580",“traceback”:"(\n\t0 CoreFoundation 0x00000001805e9cc0 FE94D75F-5F1D-3127-BA50-0161D8817EE6 + 597184\n\t1 libobjc.A.dylib 0x0000000197659758 objc\_exception\_throw + 56\n\t2 CoreFoundation 0x00000001806b96d0 FE94D75F-5F1D-3127-BA50-0161D8817EE6 + 1447632\n\t3 CoreFoundation 0x0000000180583edc FE94D75F-5F1D-3127-BA50-0161D8817EE6 + 179932\n\t4 CoreFoundation 0x000000018058314c \_CF\_forwarding\_prep\_0 + 92\n\t5 WebDriverAgentLib 0x0000000106ba0130 -[XCUIDevice(FBHelpers) fb\_rawScreenshotWithQuality:error:] + 152\n\t6 WebDriverAgentLib 0x0000000106ba0010 -[XCUIDevice(FBHelpers) fb\_screenshotWithError:] + 76\n\t7 WebDriverAgentLib 0x0000000106b45254 +[FBScreenshotCommands handleGetScreenshot:] + 10… [W3C] Matched W3C error code ‘unknown error’ to UnknownError [XCUITest] Taking screenshot with WDA [WD Proxy] Matched ‘/screenshot’ to command name ‘getScreenshot’ [WD Proxy] Proxying [GET /screenshot] to [GET [http://127.0.0.1:8100/session/58E3A011-8F89-45C6-B83F-15A045F3A0B0/screenshot](http://127.0.0.1:8100/session/58E3A011-8F89-45C6-B83F-15A045F3A0B0/screenshot)] with no body [WD Proxy] Got response with status 500: {“value”:{“error”:“unknown error”,“message”:"-[XCUIScreen screenshotDataForQuality:rect:error:]: unrecognized selector sent to instance 0x281cea9c0",“traceback”:"(\n\t0 CoreFoundation 0x00000001805e9cc0 FE94D75F-5F1D-3127-BA50-0161D8817EE6 + 597184\n\t1 libobjc.A.dylib 0x0000000197659758 objc\_exception\_throw + 56\n\t2 CoreFoundation 0x00000001806b96d0 FE94D75F-5F1D-3127-BA50-0161D8817EE6 + 1447632\n\t3 CoreFoundation 0x0000000180583edc FE94D75F-5F1D-3127-BA50-0161D8817EE6 + 179932\n\t4 CoreFoundation 0x000000018058314c \_CF\_forwarding\_prep\_0 + 92\n\t5 WebDriverAgentLib 0x0000000106ba0130 -[XCUIDevice(FBHelpers) fb\_rawScreenshotWithQuality:error:] + 152\n\t6 WebDriverAgentLib 0x0000000106ba0010 -[XCUIDevice(FBHelpers) fb\_screenshotWithError:] + 76\n\t7 WebDriverAgentLib 0x0000000106b45254 +[FBScreenshotCommands handleGetScreenshot:] + 10… [W3C] Matched W3C error code ‘unknown error’ to UnknownError [MJSONWP (b389f418)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: -[XCUIScreen screenshotDataForQuality:rect:error:]: unrecognized selector sent to instance 0x281cea9c0 [MJSONWP (b389f418)] at errorFromW3CJsonCode (/Applications/Appium.app/Contents/Resources/app/node\_modules/appium/node\_modules/appium-base-driver/lib/protocol/errors.js:780:25) [MJSONWP (b389f418)] at ProxyRequestError.getActualError (/Applications/Appium.app/Contents/Resources/app/node\_modules/appium/node\_modules/appium-base-driver/lib/protocol/errors.js:663:14) [MJSONWP (b389f418)] at JWProxy.command (/Applications/Appium.app/Contents/Resources/app/node\_modules/appium/node\_modules/appium-base-driver/lib/jsonwp-proxy/proxy.js:273:19) [MJSONWP (b389f418)] at runMicrotasks () [MJSONWP (b389f418)] at processTicksAndRejections (internal/process/task\_queues.js:85:5) [HTTP] \<-- GET /wd/hub/session/b389f418-c951-43aa-b430-354328852b5c/screenshot 500 1059 ms - 273 [HTTP] ---
**Author:** ![wreed](https://discuss.appium.io/letter_avatar_proxy/v4/letter/w/919ad9/32.png) [@wreed](https://discuss.appium.io/u/wreed)\ **Post date:** [January 4, 2022, 4:04pm UTC](https://discuss.appium.io/t/appium-ui-inspector-not-working-after-xcode-upgrade/35353/2 "2022-01-04T16:04:18Z")
> [@ShruthiSowmya](#): > > after xcode upgrade You don’t list the version of inspector or xcode you are using. Probably just need to update inspector. ---
**Author:** ![ShruthiSowmya](https://discuss.appium.io/user_avatar/discuss.appium.io/shruthisowmya/32/8665_2.png) [@ShruthiSowmya](https://discuss.appium.io/u/ShruthiSowmya)\ **Post date:** [January 5, 2022, 4:54am UTC](https://discuss.appium.io/t/appium-ui-inspector-not-working-after-xcode-upgrade/35353/3 "2022-01-05T04:54:10Z")
Hi Wreed, I use Appium desktop with below specifications. - **App Version: 1.20.2** - **Electron: 7.2.4** - **Node.js: 12.8.1** Xcode version - Version 13.2 (13C90) When I check for updates, Appium says the application is upto date even though next versions are available. Thanks, Shruthi ---
**Author:** ![wreed](https://discuss.appium.io/letter_avatar_proxy/v4/letter/w/919ad9/32.png) [@wreed](https://discuss.appium.io/u/wreed)\ **Post date:** [January 5, 2022, 4:09pm UTC](https://discuss.appium.io/t/appium-ui-inspector-not-working-after-xcode-upgrade/35353/4 "2022-01-05T16:09:26Z")
> [@ShruthiSowmya](#): > > Xcode version - Version 13.2 (13C90) Use Appium Server GUI 1.22 for Xcode 13: > **[Releases · appium/appium-desktop](https://github.com/appium/appium-desktop/releases)** > > Appium Server in Desktop GUIs for Mac, Windows, and Linux - appium/appium-desktop Note that the inspector is now a separate download: > **[Releases · appium/appium-inspector](https://github.com/appium/appium-inspector/releases)** > > A GUI inspector for mobile apps and more, powered by a (separately installed) Appium server - appium/appium-inspector Start the server first and then start the inspector. ---
**Author:** ![ShruthiSowmya](https://discuss.appium.io/user_avatar/discuss.appium.io/shruthisowmya/32/8665_2.png) [@ShruthiSowmya](https://discuss.appium.io/u/ShruthiSowmya)\ **Post date:** [January 6, 2022, 1:53pm UTC](https://discuss.appium.io/t/appium-ui-inspector-not-working-after-xcode-upgrade/35353/5 "2022-01-06T13:53:49Z")
Hi Wreed, Thank you for the suggestion . But after starting session from inspector., it throws below error. ![18%20PM](https://discuss.appium.io/uploads/default/original/2X/6/64a1dc96a2bc27f8e3f2ce5f57ac0df9f43f8499.png) ---
**Author:** ![wreed](https://discuss.appium.io/letter_avatar_proxy/v4/letter/w/919ad9/32.png) [@wreed](https://discuss.appium.io/u/wreed)\ **Post date:** [January 6, 2022, 3:49pm UTC](https://discuss.appium.io/t/appium-ui-inspector-not-working-after-xcode-upgrade/35353/6 "2022-01-06T15:49:38Z")
Please examine the link I had posted above: > **[Releases · appium/appium-desktop](https://github.com/appium/appium-desktop/releases)** > > Appium Server in Desktop GUIs for Mac, Windows, and Linux - appium/appium-desktop Release notes state: > The version still expects to have /wd/hub prefix as Remote Path Did you do that? It should be set in Inspector. I think that Appium 2.X won’t need that path. ---
**Author:** ![ShruthiSowmya](https://discuss.appium.io/user_avatar/discuss.appium.io/shruthisowmya/32/8665_2.png) [@ShruthiSowmya](https://discuss.appium.io/u/ShruthiSowmya)\ **Post date:** [January 7, 2022, 6:25am UTC](https://discuss.appium.io/t/appium-ui-inspector-not-working-after-xcode-upgrade/35353/7 "2022-01-07T06:25:44Z")
Hi Wreed, Thank you so much for all the help. It works now. But when I move around the pages it says below error. Connection was refused to port 8100 [WD Proxy] socket hang up [W3C (fd7221ee)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to the remote server. Original error: socket hang up [W3C (fd7221ee)] at JWProxy.command (/Applications/Appium Server GUI.app/Contents/Resources/app/node\_modules/appium/node\_modules/appium-base-driver/lib/jsonwp-proxy/proxy.js:274:13) [W3C (fd7221ee)] at processTicksAndRejections (internal/process/task\_queues.js:85:5) [HTTP] \<-- GET /wd/hub/session/fd7221ee-e3ff-4782-abd6-002c5220127b/source 500 8 ms - 641 Like it works only for first page on the app.Second one its errored out with socket hang up Thanks again , Shruthi ---
**Author:** ![wreed](https://discuss.appium.io/letter_avatar_proxy/v4/letter/w/919ad9/32.png) [@wreed](https://discuss.appium.io/u/wreed)\ **Post date:** [January 7, 2022, 7:11pm UTC](https://discuss.appium.io/t/appium-ui-inspector-not-working-after-xcode-upgrade/35353/8 "2022-01-07T19:11:21Z")
Hi Shruthi, I’m not familiar with this error. Is the app you are testing a Native iOS app, or is there something unusual about it (like ReactNative)? I don’t know if you use the CLI for running your tests, but if you aren’t seeing this issue in CLI you should think about filing a bug here: [https://github.com/appium/appium-desktop/issues](https://github.com/appium/appium-desktop/issues) Of course I’m happy to continue here but this may be deeper than my experience.