Trying to set appium proxy
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 752
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 8
Description
Description
We are trying to set a proxy to launch appium tests using httpCommandExecutor and we have an issue.
httpCommandExecutor seems to work not correctly (same for appiumCommandExecutor).
Without httpCommandExecutor the test works correctly.
Environment
- appium java client 5.0.4:
- Appium v1.6.5 (Desktop)
- Windows 10
- Node.js v6.11.5
- Android 4.4:
- Android Studio:
Code To Reproduce Issue
Simplified code :
capabilities are correctly defined in the code with following values
https://gist.github.com/ryltar/002f7021077297bb82d48ca0b795b448
Exception stacktraces
https://gist.github.com/ryltar/7e7372540a6c1ed568bf69d815d80230
org.openqa.selenium.UnsupportedCommandException: getSession
Link to Appium logs
https://gist.github.com/ryltar/4d039fcca29ec46752ca6bbe16b5076b
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked reproduction code, exception stacktrace, and Appium logs, then compare behavior with and without httpCommandExecutor. Trace the getSession failure across the Java client, Appium 1.6.5, and the proxy setup. Done means the proxy-enabled launch works without the UnsupportedCommandException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- mobile, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100