Error: timeout of 240000ms exceeded when running getScreenshot

Issues/Bugs
1

Hi guys,
I’m running this Appium version Appium v1.22.1 on my simulator Apple OS: IOS 12.4
On my old macOS Big Sur > this configuration was running just fine - I was able to grab the screenshots
When I’ve upgraded to macOS Monterey I was starting to get these errors when I try to get any screenshot.

Can someone please point to a workaround for this issue?

Thanks!

[HTTP] <-- POST /wd/hub/session/dbtt54f5-eece-49fb-aad7-f61a1ffd383c/element 200 38 ms - 137
[HTTP]
[HTTP] --> GET /wd/hub/session/dbtt54f5-eece-49fb-aad7-f61a1ffd383c/screenshot
[HTTP] {}
[debug] [W3C (dbba65f5)] Calling AppiumDriver.getScreenshot() with args: [“dbtt54f5-eece-49fb-aad7-f61a1ffd383c”]
[debug] [XCUITest] Executing command ‘getScreenshot’
[debug] [XCUITest] Taking screenshot with WDA
[debug] [WD Proxy] Matched ‘/screenshot’ to command name ‘getScreenshot’
[debug] [WD Proxy] Proxying [GET /screenshot] to [GET http://125.0.0.5:8100/session/544DE671-B61A-4976-BF55-95B2C01F5D87/screenshot] with no body
[WD Proxy] Error: timeout of 240000ms exceeded
[WD Proxy] at createError (/Users/dgbt/git/brew/lib/node_modules/appium/node_modules/axios/lib/core/createError.js:16:15)
[WD Proxy] at RedirectableRequest.handleRequestTimeout (/Users/dgbt/git/brew/lib/node_modules/appium/node_modules/axios/lib/adapters/http.js:280:16)
[WD Proxy] at RedirectableRequest.emit (node:events:390:28)
[WD Proxy] at Timeout._onTimeout (/Users/dgbt/git/brew/lib/node_modules/appium/node_modules/follow-redirects/index.js:166:12)
[WD Proxy] at listOnTimeout (node:internal/timers:557:17)
[WD Proxy] at processTimers (node:internal/timers:500:7)
[XCUITest] Error getting screenshot: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to the remote server. Original error: timeout of 240000ms exceeded
[XCUITest] Falling back to ‘simctl io screenshot’ API
[debug] [W3C (dbba65f5)] Responding to client with driver.getScreenshot() result: "iVBORw0KGgoAAAANSUhEUgAAAu4AAAU2CAYAAADK1zMGAAAAAXNSR0IArs4c6QAAAERlWElmTU0AKgAAAAgAAYdpAAQAAAABAAAAGgAAAAAAA6ABAAMAAAABAAEAAKACAAQAAAABAAAC7qADAAQAAAABAAAFNgAAAACw0axrAABAAElEQVR4AezdB3gc1dXw8aPeu1XcK6aZblpICO0NBEhCSCOFFFK/N72HVNIT8qZTkpAeUkgjQEhC79VUYwPuTbZVrd7LfueMM2Ytr6TZ1a60e/d/n0eWtDs7M/d35d0zd869NyOkRSgIIIAAAggggAACCCCQ1AKZSX12nBwCCCCAAAIIIIAAAgh4AgTu/CEggAACCCCAAAIIIJACAgTuKdBInCICCCCAAAIIIIAAAgTu/A0ggAACCCCAAAIIIJACAgTuKdBInCICCCCAAAIIIIAAAgTu/A0ggAACCCCAAAIIIJACAgTuKdBInCICCCCAAAIIIIAAAgTu/A0ggAACCCCAAAIIIJACAtkpcI6cIgIIIIAAAggggIBDAqOjo7J+/XrZvHmz7NmzR/r7+8UeS4aSmZkp+fn5UllZKUuWLJHly5eLPZYMJYOVU5OhGYKfg/1RP/LII3L33XfLY489Jhs2bJBdu3ZJd3e3t5Pi4mKZPXu290d23HHHyWmnnSYnnXRS0vzBBa8pWyKAAAIIIICAiwK9vb1y++23S0NDQ0pUr66uTs466ywpLCyM2/ned9998pKXvCTq/cU1cLeGePrpp72TOOSQQ6SioiLqE5quF/zud7+Tq6++Wj772c/K+eefP12Hjfk427dvlyuuuEL+8Ic/eIG67UgvuibcX0ZGhvf8nDlz5I1vfKN84AMfkIULF074Gp5EAIGJBez/nf1/fP75572L5MMPP1yysrImftE0P7tt2zbv/FasWCFz586d5qNzOAQQQGB8AeuA/Oc//+kF7dbZuHLlSrE4paCgIGneS0dGRqSvr8+Lt6yT1DpHLXi3eDEePe8b…

2
3

Thanks!
Yeah, I’ve managed to find a working solution.
XCode Beta v13.2 beta 2 running on 15.2 simulator

I was able to refactor most of my Appium suite, but I’ve got only last thing that I can’t figure out:
driver.navigate().back() is not working in IOS anymore.

Do you guys have an workaround for tapping back in IOS, when buttons aren’t accessible?

4

Did it ever work in native context? iOS does not have back button like Android does, only the Home one.

5

I did a bit a thorough reading in the appium documentation and it looks like driver.navigate().back() is just for webview not native.

Thanks!