bug:: TypeError: Cannot perform 'get' on a proxy that has been revoked #20290
Comments
gointoit
added
Bug
|
This is most likely happening because the
capability is enabled. Are you sure the system version of the device under test is 16? |
mykola-mokhnach
added
Needs Info
I am sure, all configurations are absolutely normal, WDA was also pre installed on the phone， Not only iOS 16.0, but also iOS 16.6 and iOS 16.3.1 are all the same errors，I suspect there may be compatibility issues under xcode 15.4? |
|
Why do I use xcode 15? It's because I want to test ios17, But before testing ios17, I want to verify if ios16 works properly in xcode 15, but it runs abnormally. 😭 |
You are right, this might be the culprit. Since iOS 17 Apple has completely changed the way the preinstalled WDA feature works, so we have switched to use of devicectl tool. Although this tool does not work for iOS devices running os version 16. As a workaround you may:
|
mykola-mokhnach
added
ThirdParty
|
FYI @KazuCocoa |
Thank you very much for your suggestion，I will verify ios17 on xcode15 |
I still fail when using iOS 17, but the error message has changed |
Are you sure the prebuilt WDA works on the target device? Maybe try to manually run it using the command from the log: and then verify it's listening using |
|
Also check https://github.com/appium/appium-xcuitest-driver/blob/master/docs/guides/run-preinstalled-wda.md |
|
for the first attached. I haven't seen the error case, but it looks like launching WDA succeeded once but it ended immediately. for #20290 (comment) , it didn't have ios log, but I guess the mykola's link is the reason. I wondered if the for iOS 17 thing also helps for Xcode 15 x iOS 16 |
|
Based on the above method, I tested iOS 17.5.1 and encountered a new issue where there may occasionally be permanent blocking when establishing a connection,then it couldn't be restored (maybe restarting the phone will restore it) with showIOSLog = true, The complete log information is attached below. If the appium server is not closed, this log will continue to refresh, appearing like a dead end loop without showIOSLog = false, It will always block here and there will be no timeout exceptions and also there is no other log information available |
It looks like an issue with Apple's devicectl tool. Although it should not be freezing, I would rather expect it to timeout instead. |
|
Agree, it looks like the devicectl tool related. Perhaps the command didn't issue any launching app command itself (based on the shared iOS log). I wondered if the devicectl messed up before sending launching app command to the device. |
|
In order to find a stable testing solution for iOS 17，i try to use Attach to a Running WebDriverAgent as described in the document , { and the appium log is: |
|
If you haven't started the WDA process with environment variables, the port will be the default one. Then, I guess you might need to use default |
Do I have the most recent component updates?
Is the component officially supported by the Appium team?
Is there an existing issue for this?
Current Behavior
Expected Behavior
can connect success
Minimal Reproducible Example
xcode 15.4
{ "platformName": "ios", "appium:platformVersion": "16.0", "appium:deviceName": "iPhone 13", "appium:noReset": true, "appium:bundleId": "com.apple.mobilesafari", "appium:automationName": "XCuiTest", "settings:snapshotMaxDepth": 40, "appium:udid": "00008110-001404C12622801E", "appium:wdaLocalPort": "8102", "appium:usePreinstalledWDA": true, "appium:updatedWDABundleId": "com.shopee.infra.automation.WebDriverAgentRunner" }I have changed several phones and all of them have this problem. Accompanied by this error, appium will exit abnormally
Environment
appium --version): 2.10.3appium driver list): [email protected]appium plugin list): [email protected]node --version): v22.2.0npmversion (output ofnpm --version): 10.7.0Link to Appium Logs
No response
Further Information
appium.log
After the error occurred, appium exited abnormally
The text was updated successfully, but these errors were encountered: