fix: fix typo in mobile clipboard commands #1056

KazuCocoa · 2025-03-17T02:09:25Z

The main typo fix is set's one. The type caused:

[HTTP] --> POST /session/be6b7c51-e619-4631-9e2e-0eb116629592/execute/sync
[HTTP] {"script":"mobile:setClipboard","args":[{"contentType":"plaintext","content":"aGFwcHkgdGVzdGluZw==","label":"Note"}]}
[EspressoDriver@9cd6 (be6b7c51)] Calling AppiumDriver.execute() with args: ["mobile:setClipboard",[{"contentType":"plaintext","content":"aGFwcHkgdGVzdGluZw==","label":"Note"}],"be6b7c51-e619-4631-9e2e-0eb116629592"]
[EspressoDriver@9cd6 (be6b7c51)] Encountered internal error running command: TypeError: Cannot read properties of undefined (reading 'call')
[EspressoDriver@9cd6 (be6b7c51)]     at EspressoDriver.executeMethod (/Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/node_modules/@appium/base-driver/lib/basedriver/commands/execute.ts:36:26)
[EspressoDriver@9cd6 (be6b7c51)]     at EspressoDriver.execute (/Users/kazu/.appium/node_modules/appium-espresso-driver/node_modules/appium-android-driver/lib/commands/execute.js:17:23)
[EspressoDriver@9cd6 (be6b7c51)]     at commandExecutor (/Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/node_modules/@appium/base-driver/lib/basedriver/driver.ts:106:18)
[EspressoDriver@9cd6 (be6b7c51)]     at /Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/node_modules/async-lock/lib/index.js:171:12
[EspressoDriver@9cd6 (be6b7c51)]     at AsyncLock._promiseTry (/Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/node_modules/async-lock/lib/index.js:306:31)
[EspressoDriver@9cd6 (be6b7c51)]     at exec (/Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/node_modules/async-lock/lib/index.js:170:9)
[EspressoDriver@9cd6 (be6b7c51)]     at AsyncLock.acquire (/Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/node_modules/async-lock/lib/index.js:189:3)
[EspressoDriver@9cd6 (be6b7c51)]     at EspressoDriver.executeCommand (/Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/node_modules/@appium/base-driver/lib/basedriver/driver.ts:122:39)
[EspressoDriver@9cd6 (be6b7c51)]     at processTicksAndRejections (node:internal/process/task_queues:95:5)
[EspressoDriver@9cd6 (be6b7c51)]     at defaultBehavior (/Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/lib/appium.js:1109:14)
[EspressoDriver@9cd6 (be6b7c51)]     at AppiumDriver.executeWrappedCommand (/Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/lib/appium.js:1215:16)
[EspressoDriver@9cd6 (be6b7c51)]     at AppiumDriver.executeCommand (/Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/lib/appium.js:1121:17)
[EspressoDriver@9cd6 (be6b7c51)]     at asyncHandler (/Users/kazu/.nvm/versions/node/v18.20.2/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:393:19)
[HTTP] <-- POST /session/be6b7c51-e619-4631-9e2e-0eb116629592/execute/sync 500 1 ms - 662

KazuCocoa · 2025-03-17T04:12:27Z

server side log:

�[38;5;148m[4f8b232e]�[0m�[38;5;86m[HTTP]�[0m <-- POST /session 200 27420 ms - 611 
�[38;5;148m[4f8b232e]�[0m�[38;5;86m[HTTP]�[0m �[37m-->�[39m �[37mPOST�[39m �[37m/session/4f8b232e-4b41-4f07-84ef-0bf235b3a012/element�[39m {"using":"xpath","value":"//*[@text='Clickable Component']"}
�[38;5;148m[4f8b232e]�[0m�[38;5;188m[EspressoDriver@83c6]�[0m Driver proxy active, passing request on via HTTP proxy
�[38;5;148m[4f8b232e]�[0m�[38;5;188m[EspressoDriver@83c6]�[0m Matched '/session/4f8b232e-4b41-4f07-84ef-0bf235b3a012/element' to command name 'findElement'
�[38;5;148m[4f8b232e]�[0m�[38;5;188m[EspressoDriver@83c6]�[0m Proxying [POST /session/4f8b232e-4b41-4f07-84ef-0bf235b3a012/element] to [POST http://127.0.0.1:8300/session/efac08d7-5c9c-47a1-a55f-4e78e5e340db/element] with body: {"using":"xpath","value":"//*[@text='Clickable Component']"}
�[38;5;148m[4f8b232e]�[0m�[38;5;188m[EspressoDriver@83c6]�[0m Got response with status 200: {"id":"e6f1ed58-7aac-4713-98d2-79fb786f4741","sessionId":"efac08d7-5c9c-47a1-a55f-4e78e5e340db","value":{"ELEMENT":"16925591-153f-4bf8-84c8-defa9759828a"}}
�[38;5;148m[4f8b232e]�[0m�[38;5;188m[EspressoDriver@83c6]�[0m Replacing sessionId efac08d7-5c9c-47a1-a55f-4e78e5e340db with 4f8b232e-4b41-4f07-84ef-0bf235b3a012
�[38;5;148m[4f8b232e]�[0m�[38;5;86m[HTTP]�[0m <-- POST /session/4f8b232e-4b41-4f07-84ef-0bf235b3a012/element 200 131 ms - 232

Hm, probably the client side error...?

  1) compose node attributes
       compose getAttribute
         should get attributes of a View:
     Error: WebDriverError: Request failed with error code HPE_UNEXPECTED_CONTENT_LENGTH when running "element" with method "POST" and args "{"using":"xpath","value":"//*[@text='Clickable Component']"}"
      at FetchRequest._libRequest (file:///home/runner/work/appium-espresso-driver/appium-espresso-driver/node_modules/webdriver/build/node.js:1746:13)
      at async FetchRequest._request (file:///home/runner/work/appium-espresso-driver/appium-espresso-driver/node_modules/webdriver/build/node.js:1756:20)
      at async Browser.wrapCommandFn (file:///home/runner/work/appium-espresso-driver/appium-espresso-driver/node_modules/@wdio/utils/build/index.js:902:23)
      at async Browser.$ (file:///home/runner/work/appium-espresso-driver/appium-espresso-driver/node_modules/webdriverio/build/node.js:971:15)
      at async Browser.wrapCommandFn (file:///home/runner/work/appium-espresso-driver/appium-espresso-driver/node_modules/@wdio/utils/build/index.js:902:23)
      at async Context.<anonymous> (test/functional/commands/jetpack-compose-attributes-e2e-specs.js:46:18)

This change itself worked on my local with ruby client

mykola-mokhnach · 2025-03-17T08:19:38Z

server side log:

�[38;5;148m[4f8b232e]�[0m�[38;5;86m[HTTP]�[0m <-- POST /session 200 27420 ms - 611 
�[38;5;148m[4f8b232e]�[0m�[38;5;86m[HTTP]�[0m �[37m-->�[39m �[37mPOST�[39m �[37m/session/4f8b232e-4b41-4f07-84ef-0bf235b3a012/element�[39m {"using":"xpath","value":"//*[@text='Clickable Component']"}
�[38;5;148m[4f8b232e]�[0m�[38;5;188m[EspressoDriver@83c6]�[0m Driver proxy active, passing request on via HTTP proxy
�[38;5;148m[4f8b232e]�[0m�[38;5;188m[EspressoDriver@83c6]�[0m Matched '/session/4f8b232e-4b41-4f07-84ef-0bf235b3a012/element' to command name 'findElement'
�[38;5;148m[4f8b232e]�[0m�[38;5;188m[EspressoDriver@83c6]�[0m Proxying [POST /session/4f8b232e-4b41-4f07-84ef-0bf235b3a012/element] to [POST http://127.0.0.1:8300/session/efac08d7-5c9c-47a1-a55f-4e78e5e340db/element] with body: {"using":"xpath","value":"//*[@text='Clickable Component']"}
�[38;5;148m[4f8b232e]�[0m�[38;5;188m[EspressoDriver@83c6]�[0m Got response with status 200: {"id":"e6f1ed58-7aac-4713-98d2-79fb786f4741","sessionId":"efac08d7-5c9c-47a1-a55f-4e78e5e340db","value":{"ELEMENT":"16925591-153f-4bf8-84c8-defa9759828a"}}
�[38;5;148m[4f8b232e]�[0m�[38;5;188m[EspressoDriver@83c6]�[0m Replacing sessionId efac08d7-5c9c-47a1-a55f-4e78e5e340db with 4f8b232e-4b41-4f07-84ef-0bf235b3a012
�[38;5;148m[4f8b232e]�[0m�[38;5;86m[HTTP]�[0m <-- POST /session/4f8b232e-4b41-4f07-84ef-0bf235b3a012/element 200 131 ms - 232

Hm, probably the client side error...?

  1) compose node attributes
       compose getAttribute
         should get attributes of a View:
     Error: WebDriverError: Request failed with error code HPE_UNEXPECTED_CONTENT_LENGTH when running "element" with method "POST" and args "{"using":"xpath","value":"//*[@text='Clickable Component']"}"
      at FetchRequest._libRequest (file:///home/runner/work/appium-espresso-driver/appium-espresso-driver/node_modules/webdriver/build/node.js:1746:13)
      at async FetchRequest._request (file:///home/runner/work/appium-espresso-driver/appium-espresso-driver/node_modules/webdriver/build/node.js:1756:20)
      at async Browser.wrapCommandFn (file:///home/runner/work/appium-espresso-driver/appium-espresso-driver/node_modules/@wdio/utils/build/index.js:902:23)
      at async Browser.$ (file:///home/runner/work/appium-espresso-driver/appium-espresso-driver/node_modules/webdriverio/build/node.js:971:15)
      at async Browser.wrapCommandFn (file:///home/runner/work/appium-espresso-driver/appium-espresso-driver/node_modules/@wdio/utils/build/index.js:902:23)
      at async Context.<anonymous> (test/functional/commands/jetpack-compose-attributes-e2e-specs.js:46:18)

This change itself worked on my local with ruby client

This looks like a result of the recent webdriverio update. Would it be possible to debug headers that the server sends in response to this request? Maybe a new bug has been introduced with the recent wdio update and we need to report about it?

KazuCocoa · 2025-03-17T08:54:12Z

Yea, it would take time, but will try to take a look at that issue later

## [4.1.3](v4.1.2...v4.1.3) (2025-03-17) ### Bug Fixes * fix typo in mobile clipboard commands ([#1056](#1056)) ([7f8a88e](7f8a88e))

github-actions · 2025-03-17T08:56:29Z

🎉 This PR is included in version 4.1.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

fix: fix typo in mobile clipboard commands

1a4f60a

KazuCocoa requested a review from mykola-mokhnach March 17, 2025 02:10

mykola-mokhnach approved these changes Mar 17, 2025

View reviewed changes

KazuCocoa merged commit 7f8a88e into master Mar 17, 2025
7 of 11 checks passed

KazuCocoa deleted the fix-typo branch March 17, 2025 08:54

github-actions bot pushed a commit that referenced this pull request Mar 17, 2025

chore(release): 4.1.3 [skip ci]

a74d465

## [4.1.3](v4.1.2...v4.1.3) (2025-03-17) ### Bug Fixes * fix typo in mobile clipboard commands ([#1056](#1056)) ([7f8a88e](7f8a88e))

github-actions bot added the released label Mar 17, 2025

mykola-mokhnach mentioned this pull request Mar 17, 2025

fix(base-driver): Exclude proxied headers from the server response appium/appium#21120

Merged

4 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: fix typo in mobile clipboard commands #1056

fix: fix typo in mobile clipboard commands #1056

KazuCocoa commented Mar 17, 2025 •

edited

Loading

KazuCocoa commented Mar 17, 2025 •

edited

Loading

mykola-mokhnach commented Mar 17, 2025

KazuCocoa commented Mar 17, 2025

github-actions bot commented Mar 17, 2025

fix: fix typo in mobile clipboard commands #1056

fix: fix typo in mobile clipboard commands #1056

Conversation

KazuCocoa commented Mar 17, 2025 • edited Loading

KazuCocoa commented Mar 17, 2025 • edited Loading

mykola-mokhnach commented Mar 17, 2025

KazuCocoa commented Mar 17, 2025

github-actions bot commented Mar 17, 2025

KazuCocoa commented Mar 17, 2025 •

edited

Loading

KazuCocoa commented Mar 17, 2025 •

edited

Loading