Infinite loading wheel in Appium inspector

Support
1

Hi everyone,

I’ve installed Appium 1.13.0 on my Mac running 10.14.4 macOS version in order to use it to catch apps xpath. The following is the JSON file I’m using:

{
“automationName”: “XCUITest”,
“platformName”: “iOS”,
“platformVersion”: “10.0”,
“deviceName”: “iPhone di Francesco”,
“udid”: “xxxxxxxxxxxxxxxxxxxx”,
“xcodeOrgId”: “xxxxxxxx”,
“xcodeSigningId”: “iPhone Developer”,
“isAvailable”: “true”,
“noReset”: “false”,
“bundleId”: “com.facebook.Facebook”
}

This is the error displayed on Appium server:

[MJSONWP] Matched JSONWP error code 13 to UnknownError
[iProxy] recv failed: Connection reset by peer
[iProxy] recv failed: Operation not permitted
[MJSONWP (a3315e31)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: -[XCApplicationQuery elementSnapshotForDebugDescription]: unrecognized selector sent to instance 0x1705afe0
[MJSONWP (a3315e31)]
[MJSONWP (a3315e31)] (
[MJSONWP (a3315e31)] 0 CoreFoundation 0x1d9afb55 + 152
[MJSONWP (a3315e31)] 1 libobjc.A.dylib 0x1cc37067 objc_exception_throw + 38
[MJSONWP (a3315e31)] 2 CoreFoundation 0x1d9b4fd1 + 0
[MJSONWP (a3315e31)] 3 CoreFoundation 0x1d9b30c3 + 696
[MJSONWP (a3315e31)] 4 CoreFoundation 0x1d8dbdc8 _CF_forwarding_prep_0 + 24
[MJSONWP (a3315e31)] 5 WebDriverAgentLib 0x021dccbd -[XCUIElement(FBUtilities) fb_lastSnapshot] + 52
[MJSONWP (a3315e31)] 6 WebDriverAgentLib 0x021d52b5 -[XCUIElement(WebDriverAttributesForwarding) fb_snapshotForAttributeName:] + 748
[MJSONWP (a3315e31)] 7 WebDriverAgentLib 0x021d547b -[XCUIElement(WebDriverAttributesForwarding) forwardingTargetForSelector:] + 150
[MJSONWP (a3315e31)] 8 CoreFoundation 0x1d9b2e5f + 84
[MJSONWP (a3315e31)] 9 CoreFoundation 0x1d9b42c8 + 24
[MJSONWP (a3315e31)] 10 WebDriverAgentLib 0x021f8467 +[FBElementCommands handleGetWindowSize:] + 182
[MJSONWP (a3315e31)] 11 WebDriverAgentLib 0x021c8911 -[FBRoute_TargetAction mountRequest:intoResponse:] + 176
[MJSONWP (a3315e31)] 12 WebDriverAgentLib 0x021b8b0d __37-[FBWebServer registerRouteHandlers:]_block_invoke + 600
[MJSONWP (a3315e31)] 13 RoutingHTTPServer 0x02300b99 -[RoutingHTTPServer handleRoute:withRequest:response:] + 94
[MJSONWP (a3315e31)] 14 RoutingHTTPServer 0x023011ff __72-[RoutingHTTPServer routeMethod:withPath:parameters:request:connection:]_block_invoke + 40
[MJSONWP (a3315e31)] 15 libdispatch.dylib 0x1d08cd77 + 222
[MJSONWP (a3315e31)] 16 libdispatch.dylib 0x1d07d783 + 22
[MJSONWP (a3315e31)] 17 libdispatch.dylib 0x1d081d05 _dispatch_main_queue_callback_4CF + 902
[MJSONWP (a3315e31)] 18 CoreFoundation 0x1d96bd69 + 8
[MJSONWP (a3315e31)] 19 CoreFoundation 0x1d969e19 + 848
[MJSONWP (a3315e31)] 20 CoreFoundation 0x1d8bd1af CFRunLoopRunSpecific + 470
[MJSONWP (a3315e31)] 21 CoreFoundation 0x1d8bcfd1 CFRunLoopRunInMode + 104
[MJSONWP (a3315e31)] 22 Foundation 0x1e211af5 + 258
[MJSONWP (a3315e31)] 23 WebDriverAgentLib 0x021b74fb -[FBWebServer startServing] + 532
[MJSONWP (a3315e31)] 24 WebDriverAgentRunner 0x0219dc05 -[UITestingUITests testRunner] + 146
[MJSONWP (a3315e31)] 25 CoreFoundation 0x1d9b4354 + 68
[MJSONWP (a3315e31)] 26 CoreFoundation 0x1d8d82b9 + 300
[MJSONWP (a3315e31)] 27 XCTest 0x002a26b3 __24-[XCTestCase invokeTest]_block_invoke_2.212 + 52
[MJSONWP (a3315e31)] 28 XCTest 0x00305cc1 -[XCTMemoryChecker _assertInvalidObjectsDeallocatedAfterScope:] + 52
[MJSONWP (a3315e31)] 29 XCTest 0x002acac1 -[XCTestCase assertInvalidObjectsDeallocatedAfterScope:] + 86
[MJSONWP (a3315e31)] 30 XCTest 0x002a265f __24-[XCTestCase invokeTest]_block_invoke.206 + 172
[MJSONWP (a3315e31)] 31 XCTest 0x002f046b -[XCTestCase(Failures) performFailableBlock:testCaseRun:shouldInterruptTest:] + 106
[MJSONWP (a3315e31)] 32 XCTest 0x002f035f -[XCTestCase(Failures) _performTurningExceptionsIntoFailuresInterruptAfterHandling:block:] + 84
[MJSONWP (a3315e31)] 33 XCTest 0x002a20ab __24-[XCTestCase invokeTest]_block_invoke + 1286
[MJSONWP (a3315e31)] 34 XCTest 0x002f57db -[XCUITestContext performInScope:] + 198
[MJSONWP (a3315e31)] 35 XCTest 0x002a1b05 -[XCTestCase testContextPerformInScope:] + 168
[MJSONWP (a3315e31)] 36 XCTest 0x002a1ba1 -[XCTestCase invokeTest] + 126
[MJSONWP (a3315e31)] 37 XCTest 0x002a3797 __26-[XCTestCase performTest:]_block_invoke_2 + 30
[MJSONWP (a3315e31)] 38 XCTest 0x002f046b -[XCTestCase(Failures) performFailableBlock:testCaseRun:shouldInterruptTest:] + 106
[MJSONWP (a3315e31)] 39 XCTest 0x002f035f -[XCTestCase(Failures) _performTurningExceptionsIntoFailuresInterruptAfterHandling:block:] + 84
[MJSONWP (a3315e31)] 40 XCTest 0x002a36d3 __26-[XCTestCase performTest:]_block_invoke.340 + 80
[MJSONWP (a3315e31)] 41 XCTest 0x002ff923 +[XCTContext runInContextForTestCase:block:] + 278
[MJSONWP (a3315e31)] 42 XCTest 0x002a2fd7 -[XCTestCase performTest:] + 618
[MJSONWP (a3315e31)] 43 XCTest 0x002df16f -[XCTest runTest] + 50
[MJSONWP (a3315e31)] 44 XCTest 0x0029e1b9 __27-[XCTestSuite performTest:]_block_invoke + 368
[MJSONWP (a3315e31)] 45 XCTest 0x0029d879 -[XCTestSuite _performProtectedSectionForTest:testSection:] + 104
[MJSONWP (a3315e31)] 46 XCTest 0x0029dc27 -[XCTestSuite performTest:] + 390
[MJSONWP (a3315e31)] 47 XCTest 0x002df16f -[XCTest runTest] + 50
[MJSONWP (a3315e31)] 48 XCTest 0x0029e1b9 __27-[XCTestSuite performTest:]_block_invoke + 368
[MJSONWP (a3315e31)] 49 XCTest 0x0029d879 -[XCTestSuite _performProtectedSectionForTest:testSection:] + 104
[MJSONWP (a3315e31)] 50 XCTest 0x0029dc27 -[XCTestSuite performTest:] + 390
[MJSONWP (a3315e31)] 51 XCTest 0x002df16f -[XCTest runTest] + 50
[MJSONWP (a3315e31)] 52 XCTest 0x0029e1b9 __27-[XCTestSuite performTest:]_block_invoke + 368
[MJSONWP (a3315e31)] 53 XCTest 0x0029d879 -[XCTestSuite _performProtectedSectionForTest:testSection:] + 104
[MJSONWP (a3315e31)] 54 XCTest 0x0029dc27 -[XCTestSuite performTest:] + 390
[MJSONWP (a3315e31)] 55 XCTest 0x002df16f -[XCTest runTest] + 50
[MJSONWP (a3315e31)] 56 XCTest 0x0030f52b __44-[XCTTestRunSession runTestsAndReturnError:]_block_invoke + 166
[MJSONWP (a3315e31)] 57 XCTest 0x0030f603 __44-[XCTTestRunSession runTestsAndReturnError:]_block_invoke.80 + 84
[MJSONWP (a3315e31)] 58 XCTest 0x002b618f -[XCTestObservationCenter _observeTestExecutionForBlock:] + 586
[MJSONWP (a3315e31)] 59 XCTest 0x0030f29b -[XCTTestRunSession runTestsAndReturnError:] + 786
[MJSONWP (a3315e31)] 60 XCTest 0x00284af5 -[XCTestDriver runTestsAndReturnError:] + 394
[MJSONWP (a3315e31)] 61 XCTest 0x002fc7ad _XCTestMain + 2270
[MJSONWP (a3315e31)] 62 WebDriverAgentRunner-Runner 0x000505cf -[_XCTRunnerAppDelegate applicationWillResignActive:] + 0
[MJSONWP (a3315e31)] 63 WebDriverAgentRunner-Runner 0x000504ed _XCTRunnerRunTests + 0
[MJSONWP (a3315e31)] 64 CoreFoundation 0x1d96bf15 + 10
[MJSONWP (a3315e31)] 65 CoreFoundation 0x1d96b925 + 230
[MJSONWP (a3315e31)] 66 CoreFoundation 0x1d969f47 + 1150
[MJSONWP (a3315e31)] 67 CoreFoundation 0x1d8bd1af CFRunLoopRunSpecific + 470
[MJSONWP (a3315e31)] 68 CoreFoundation 0x1d8bcfd1 CFRunLoopRunInMode + 104
[MJSONWP (a3315e31)] 69 GraphicsServices 0x1f067b41 GSEventRunModal + 80
[MJSONWP (a3315e31)] 70 UIKit 0x22c45a53 UIApplicationMain + 150
[MJSONWP (a3315e31)] 71 WebDriverAgentRunner-Runner 0x00050757 main + 164
[MJSONWP (a3315e31)] 72 libdyld.dylib 0x1d0aa4eb + 2
[MJSONWP (a3315e31)] )
[MJSONWP (a3315e31)] at errorFromMJSONWPStatusCode (/Applications/Appium.app/Contents/Resources/app/node_modules/appium/node_modules/appium-base-driver/lib/protocol/errors.js:789:10)
[MJSONWP (a3315e31)] at ProxyRequestError.errorFromMJSONWPStatusCode [as getActualError] (/Applications/Appium.app/Contents/Resources/app/node_modules/appium/node_modules/appium-base-driver/lib/protocol/errors.js:683:14)
[MJSONWP (a3315e31)] at JWProxy.getActualError [as command] (/Applications/Appium.app/Contents/Resources/app/node_modules/appium/node_modules/appium-base-driver/lib/jsonwp-proxy/proxy.js:235:19)
[HTTP] <-- GET /wd/hub/session/a3315e31-50c3-4b9a-8bd8-97655f6f8e79/window/current/size 500 1262 ms - 7242
[HTTP]

Could you kindly help me to understand why the result I have is an infinite loading wheel? Appium seems to can’t catch the device screen. Honestly speaking, I don’t know what’s happening.

Regards,
Francesco

2
3

I’ve followed the steps reported in this thread, but I continue having this error message:

Taking screenshot with ‘idevicescreenshot’

[iProxy] recv failed: Connection reset by peer

[iProxy] recv failed: Operation not permitted

[WD Proxy] Matched ‘/orientation’ to command name ‘getOrientation’

[WD Proxy] Proxying [GET /orientation] to [GET http://localhost:8100/session/E0EA974D-145D-4EBB-AFAB-FA9F8D96B1A9/orientation] with no body

[WD Proxy] Got response with status 200: “{\n “sessionId” : “E0EA974D-145D-4EBB-AFAB-FA9F8D96B1A9”,\n “value” : “PORTRAIT”,\n “status” : 0\n}”

[iProxy] recv failed: Connection reset by peer

[iProxy] recv failed: Operation not permitted

[MJSONWP (9ee3a1bd)] Responding to client with driver.getScreenshot() result: "iVBORw0KGgoAAAANSUhEUgAAAoAAAARwCAIAAAD17XJXAAAABGdBTUEAALGPC/xhBQAAACBjSFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AABAAElEQVR4Aey9CbQsyVnfmXd57/W+SN3q1o52IbUagQCtSAIJSWa1WCxACGN5BjPDDMvYnjnj8YbtOV7n2J7DGI6NB2yMDQyLMdIIxDYYmk1CIIGQ2JEaqdWbeu/X7717b80v8quKm1WVmZVVuUVE/uPUqcrKjIz44v9FxD++LyIy91755V9123t/I5vN3OfkJFMQAkJACAgBISAE+kfgcJ7F3l5mH2NivhWEgBAQAkJACAiB3hDYX0oZDt7fdx8OFISAEBACQkAICIHeEFgmYMsG9j04cB8FISAEhIAQEAJCoB8EygjYcjIalincD+5KVQgIASEgBCaOQDUBA4w3hUXDE68mKr4QEAJCQAh0jUAtAVtmRsOaGO4aeqUnBISAEBACU0ZgsQp6IwYQMIF9SrZMemN8RRACQkAICAEhIASqEWhgARdvtjXSRsbF8zoWAkJACAgBISAEtkFgSwImaTzSEPDhobYqbYOz4goBISAEhIAQWEJgewL2t7NPCSbW+iwPiA6EgBAQAkJACFx4rCEGjeeAS9ODgP2Ts/TwrFKIVk4eH2VHR27UcnjGDV8CDOjx4mMZFejSBSfqyXF2Msv2c7fHwZns7Lns7GXZucs08NpddSB86aK7/czZzTAS+ehSRrU5OHR1ZrDx7uzEad/lyyMBQq2ru+tAd0aCwPlHsocfcO1l+Gcznj2bXXlNdsVVWyOFtI896jrJBmEbAr7zz7JLl7Jrrsuuuf40ZXoEPnQTfB5+MHvwvuyyK7LrHn8aQUcgwOK1Rx50Nen0adt7TkMgCaUVA5q7/1538nFPOD19zx2uFz5zLnv8TacnS4/u+UR2dDE7PJvdcHPp9bqT9LZo8PzD2fHxajQ4GMnpkS+cd5f2D1y9vOoa…

[HTTP] <-- GET /wd/hub/session/9ee3a1bd-be63-417c-bb60-720f44ce8e4c/screenshot 200 1125 ms - 69522

Any suggest?

4

I’m stuck on the same thing and a failure trying to get appium to work on a newly installed box. I’m about giving up on trying to set this up with our framework. Someone needs to put up an install process that works. What good is a tool if it is a crapshoot to set up all the pieces from three different vendors.

I’ve set it up on a previous box but constantly run into problems where Appium says “It’s not our problem” and closes the ticket. Pretty frustrating trying to get this working when I have zero problem getting cucumber/ruby to work. Try to put the appium piece in especially with live iOS devices is a chore to say the least. Still don’t know how I got it to work on my last machine.

1 Like
5

Hey Candyman,

We are also facing the same issue after the forced update on XCODE (now 11). The loading wheel is taking infinite time to gather the screenshot in appium inspector.
Waiting for the resolution.
Meanwhile if you are able to fix it, keep us posted

6

There is workaround =) you need Appium v1.15.0-beta.1 (command line version):

  1. start desktop appium > start inspector > stop appium server
  2. start appium server v1.15.0-beta.1 (e.g. appium -p 4723) from terminal/cli > start inspector session on the port
7

there is 1.15 inspector already -> https://github.com/appium/appium-desktop/releases/tag/v1.15.0