microg companion crashes with unexpected field encoding
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Describe the bug
Unfortunately I don't know how to reproduce it. All I know is that MicroG companion crashed with the following stack trace.
System
Android Version: 15
Custom ROM: CalyxOS 6.2.3
Additional context
FATAL EXCEPTION: main
Process: com.android.vending, PID: 20222
java.net.ProtocolException: Unexpected field encoding: 6
at com.squareup.wire.ProtoReader.skipGroup(SourceFile:58)
at com.squareup.wire.ProtoReader.nextTag(SourceFile:84)
at com.google.android.finsky.ExpressFilePB$Companion$ADAPTER$1.decode(SourceFile:15)
at com.squareup.wire.ProtoAdapter.decode(SourceFile:1)
at com.google.android.finsky.IntegrityExtensionsKt$updateExpressSessionTime$2.invokeSuspend(SourceFile:42)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(Unknown Source:8)
at kotlinx.coroutines.DispatchedTask.run(Unknown Source:96)
at androidx.fragment.app.Fragment$4.run(SourceFile:13)
at kotlinx.coroutines.scheduling.TaskImpl.run(Unknown Source:2)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(SourceFile:92)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@6fa3a94, Dispatchers.Main.immediate]
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 stack trace around com.squareup.wire.ProtoReader.skipGroup and nextTag, then trace ExpressFilePB and IntegrityExtensionsKt.updateExpressSessionTime. The report provides no reproduction steps, so first determine what produces field encoding 6 on Android 15 and establish a way to validate that the crash no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100