com.google.android.gms, microG GMS fatal exception error on Logcat
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Affected app
Name: microG GMS
Package id: com.google.android.gms
Describe the bug
After getting help from microG Telegram group, the friend there found a Fatal Exception line on my Logcat referring microG.
To Reproduce
I can't seem to reproduce it.
Expected behavior
As stated above, I couldn't reproduce it yet. So, don't know it's culprit nor the way it is occurred. Only updated to the latest GMS apk from here. Then it happened after using npem command, after a while afterwards.
Screenshots
No screenshots
System
Android Version: 11
Custom ROM: ArrowOS RQ3A.211001.001
microG
microG Core version: 0.2.24.214816
microG Self-Check results: All ticked
Additional context
Logcat (filtered with "FATAL EXCEPTION"):
https://pastebin.com/VxfxHnLL
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 reading the linked Logcat paste and checking the reported fatal exception against the microG GMS package. The report provides no reproduction steps, source files, or tests; progress would require identifying a reproducible trigger and the responsible component before defining a fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100