Improve error handling and logging (exposure notification)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem? Please describe.
Yes, post-mortem of https://github.com/microg/GmsCore/issues/1708
Describe the solution you'd like
The error handling should be improved by:
- logging stuff that is relevant
- showing more relevant/specific error messages
Describe alternatives you've considered
N/A
Additional context
In the issue, there was a missing permission, but the error it yielded was sth. about some interface not being connected.
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 reviewing the post-mortem in issue 1708 and tracing the exposure-notification failure described there. Identify where the missing-permission failure becomes an interface-not-connected error; done means relevant details are logged and the user receives a specific error message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100