[RemoteDebugger] WebKitRPCWarning: Did not find handler for the message
See original GitHub issueThe problem
When switching from Native context to Web view context, an error message is being thrown, since it is not handled terminates the session, resulting in test cases failing.
Seen this issue on iOS only. iOSCapabilities.setCapability(“startIWDP”,true); iOSCapabilities.setCapability(“autoWebview”, true); iOSCapabilities.setCapability(“autoWebviewTimeout”, 7000);
Environment
- Appium version (or git revision) that exhibits the issue: 1.8.2 Beta
- Desktop OS/version used to run Appium: MAC OS 10.13.6
- Mobile platform/version under test: 11.4.1
- Real device or emulator/simulator: iPhone 6
- Appium CLI or Appium.app|exe:
Details
2018-07-31 08:19:49:534 - [RemoteDebugger] WebKitRPCWarning: Did not find handler for the message
2018-07-31 08:19:49:534 - [RemoteDebugger] at WebKitRpcClient.receive (/usr/local/lib/node_modules/appium/node_modules/appium-remote-debugger/lib/webkit-rpc-client.js:142:25)
2018-07-31 08:19:49:535 - [RemoteDebugger] at WebSocket.emit (events.js:180:13)
2018-07-31 08:19:49:535 - [RemoteDebugger] at Receiver.receiverOnMessage (/usr/local/lib/node_modules/appium/node_modules/ws/lib/websocket.js:720:20)
2018-07-31 08:19:49:535 - [RemoteDebugger] at Receiver.emit (events.js:180:13)
2018-07-31 08:19:49:535 - [RemoteDebugger] at Receiver.dataMessage (/usr/local/lib/node_modules/appium/node_modules/ws/lib/receiver.js:414:14)
2018-07-31 08:19:49:535 - [RemoteDebugger] at Receiver.getData (/usr/local/lib/node_modules/appium/node_modules/ws/lib/receiver.js:346:17)
2018-07-31 08:19:49:535 - [RemoteDebugger] at Receiver.startLoop (/usr/local/lib/node_modules/appium/node_modules/ws/lib/receiver.js:133:22)
2018-07-31 08:19:49:535 - [RemoteDebugger] at Receiver._write (/usr/local/lib/node_modules/appium/node_modules/ws/lib/receiver.js:69:10)
2018-07-31 08:19:49:535 - [RemoteDebugger] at doWrite (_stream_writable.js:410:12)
2018-07-31 08:19:49:535 - [RemoteDebugger] at writeOrBuffer (_stream_writable.js:396:5)
2018-07-31 08:19:49:535 - [RemoteDebugger] at Receiver.Writable.write (_stream_writable.js:294:11)
2018-07-31 08:19:49:535 - [RemoteDebugger] at Socket.socketOnData (/usr/local/lib/node_modules/appium/node_modules/ws/lib/websocket.js:795:35)
2018-07-31 08:19:49:536 - [RemoteDebugger] at Socket.emit (events.js:180:13)
2018-07-31 08:19:49:536 - [RemoteDebugger] at addChunk (_stream_readable.js:274:12)
2018-07-31 08:19:49:536 - [RemoteDebugger] at readableAddChunk (_stream_readable.js:261:11)
2018-07-31 08:19:49:536 - [RemoteDebugger] at Socket.Readable.push (_stream_readable.js:218:10)
2018-07-31 08:19:49:536 - [RemoteDebugger] at TCP.onread (net.js:581:20)
2018-07-31 08:19:49:539 - uncaughtException: Did not find handler for the message
Link to Appium logs
Gist link: https://gist.github.com/mayureshshirodkar/4d99d2971a820fbe75e4fe4c6beb4cbb
Code To Reproduce Issue [ Good To Have ]
getWebDriver().context(“WEBVIEW_1”);
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (1 by maintainers)
Top Results From Across the Web
Did not find handler method Error - Spring Boot - Stack Overflow
There is nothing wrong with your code and the request mapping is fine. This message is most likely presented by the spring-boot-actuator module...
Read more >RequestMappingHandlerMapping - Did not find handler method
Using the "/.html" pattern inside the @RequestMapping annotation, Spring find the mapping with my say() method and all run well !
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Please try the patch from https://github.com/appium/appium-remote-debugger/pull/91
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.