uber / uber/rides-android-sdk

Emulator Runner Not Supporting API 28+

Open
#188 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
293
Forks
132
PR merge metrics
No merged PRs in 30d

Description

https://github.com/ReactiveCircus/android-emulator-runner/issues/179

I have removed API 28+ from the testing matrix because of the above issue with the emulator.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the referenced android-emulator-runner issue 179 and the repository's testing matrix, since the report says API 28+ was removed because of that emulator problem. Done means determining a supported fix and restoring API 28+ coverage without the reported emulator failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.