Can not specify default-capabilities on Windows
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 752
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 8
Description
appium java client 7.5.1 on windows platform
appiume server:1.21.0,
AppiumServiceBuilder serviceBuilder = new AppiumServiceBuilder();
......
DesiredCapabilities caps = new DesiredCapabilities();
caps.setCapability("noSign", true);
serviceBuilder.withCapabilities(caps);
AppiumDriverLocalService server = AppiumDriverLocalService.buildService(serviceBuilder);
server.start();
appium: error: argument -dc/--default-capabilities: invalid parseDefaultCaps value: '{noReset:true,noSign:true}'
Disconnected from the target VM, address: '127.0.0.1:50313', transport: 'socket'
according to following link , java client need fix this
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 by reproducing the AppiumServiceBuilder.withCapabilities case on Windows with Appium Java client 7.5.1 and Appium server 1.21.0. Inspect how default capabilities are serialized into the -dc/--default-capabilities argument, compare the linked Appium issue, and verify that server.start() no longer reports an invalid parseDefaultCaps value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- mobile-dev, operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100