(Request) Support wildcard *.apk naming in App Capability with local absolute path
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 752
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 8
Description
Description
I have a script which build an apk and has variable info such as the build#, commit hash, or date/time when copied appended to the name. It would be awesome if there was support for finding/specifying the app capability with e.g. /path/to/*.apk, and would potentially throw an error if multiple apks were found in that directory.
Environment
n/a
Details
n/a
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 locating how the Java client resolves the App capability when given a local absolute APK path, then inspect any related capability tests. Define the wildcard behavior for paths such as /path/to/*.apk, including the error case when multiple APKs are found; done means the selected APK is accepted and ambiguous matches are rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100