fix: Ensure Appium Protocol is included when attaching to a session id #208
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is currently a difference in drivers when a session is started through the Appium inspector and when a session is attached.
The
commandList
are different which is a result of differentuserPrototypes
being set up in webdriver.https://github.com/webdriverio/webdriverio/blob/e2aa001ecbf240e5240ce551acbfb19f6d004973/packages/webdriver/src/utils.ts#L182
When starting a session, webdriver will determine device type and configure the userPrototypes accordingly. However, when attaching to a session, webdriver doesn't do this which results in the difference in drivers. Since we are attaching to a session in the Appium Inspector, we can assume that the use cases are devices that are mobile so we set
isMobile = true
in the server options.