Skip to content

Wasted Appium round trips: captureTrace runs on native sessions #350

Description

@vishnuv688

Three call sites reach SessionCapturer.captureTrace and only one asks whether the session is native. The other two run a page-side browser.execute against a native app, which cannot answer.

Measured on a real Pixel 7: 5 failures per run, each a round trip to the device plus an ERROR @wdio/devtools-service:SessionCapturer: Failed to capture trace: WebDriverError: Method is not implemented line in the user's output.

Part of the slowdown @leo reported, and pure noise in the log.

Fix: guard inside captureTrace itself rather than at each call site — the guard belongs where the assumption lives.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingmobileAppium / native mobile capture and playback

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions