ReadYouApp / ReadYouApp/ReadYou
crash report
Open
Nobody has claimed this yet.
bug
untriaged
- Dominant language
- Kotlin
- Stars
- 7.5k
- Forks
- 330
- PR merge metrics
- No merged PRs in 30d
Description
Checklist
- I've already searched in existing issues and haven't found a similar problem reported.
- I'm using the latest version of the app
- This error caused the app to crash
- This error is reproducible
Which category best fits this error?
Feed Sync
App version
0.16.1
Reproduction steps
...
Crash report
Version: 0.16.1
Device: motorola moto g54 5G
System: Android 15 (API 35)
Stack trace:
.lang.NullPointerException: Attempt to invoke interface method 'java.lang.Object kotlinx.coroutines.flow.Flow.collect(kotlinx.coroutines.flow.FlowCollector, kotlin.coroutines.Continuation)' on a null object reference
at kotlinx.coroutines.flow.internal.CombineKt$combineInternal$2$1.invokeSuspend(Combine.kt:45)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:112)
at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:8)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:3)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:93)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@3761c4c, Dispatchers.Default]
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 Feed Sync path and the stack trace's coroutine Flow combine call; determine which flow is null on Android 15 with version 0.16.1. The issue provides no source file, reproduction steps, or test entry point, so first establish a reproducible sync scenario. Done means the crash no longer occurs and the affected scenario is covered by a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100