activateApp endpoint always points to the bundleId
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 752
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 8
Description
Environment
- Java client build version or git revision if you use some snapshot:
7.2.0 - Appium server version or git revision if you use some snapshot:
1.13.0 - Desktop OS/version used to run Appium if necessary:
MacOS 10.14.6 - Node.js version (unless using Appium.app|exe) or Appium CLI or Appium.app|exe:
- Mobile platform/version under test: Android
- Real device or emulator/simulator:
Real device
Details
I would like to activate an app on Android device. However, it always points to the bundleId, and I don't know how to add param BaseActivateApplicationOptions as the second param.
Code To Reproduce Issue [ Good To Have ]
driver.activateApp("com.android.chrome");
Output
{
"bundleId": "com.android.chrome"
}
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 at the Java client's activateApp entry point and the BaseActivateApplicationOptions overload mentioned in the report. Reproduce the call with driver.activateApp("com.android.chrome") on Android, then verify that the endpoint receives the intended application options rather than only bundleId.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- api, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100