FakeStore random crash
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Describe the bug
FakeStore usually crashes randomly
To Reproduce
Steps to reproduce the behavior:
- Open 'LogFox' and start logging
- Wait for 30-40 minutes
- See crash report
Expected behavior
There should be no random crash
Screenshots
System
Android Version: 13
Custom ROM: InterstellarUI 1.1 (RisingOS fork)
Additional context
Crash log:
FATAL EXCEPTION: main
Process: com.android.vending, PID: 7888
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1441)
at java.util.HashMap$KeyIterator.next(HashMap.java:1465)
at org.microg.gms.common.MultiConnectionKeeper$Connection$1.onServiceConnected(SourceFile:53)
at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:2188)
at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:2221)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7943)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:848)
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 with the crash log and inspect org.microg.gms.common.MultiConnectionKeeper, especially Connection$1.onServiceConnected, where the ConcurrentModificationException is reported. Reproduce by opening LogFox and logging for 30–40 minutes on Android 13, then trace the connection collection handling. Done means the reported random crash no longer occurs and the relevant behavior is covered by verification.
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
- 35/100