wip: Instrument calls to refresh the cached timeline
A user report shows what appears to be spurious / unexpected calls to refresh the cached timeline occuring while scrolling. Have confirmed these calls aren't coming from any Pachli code, so adding additional instrumentation that can be included in a custom APK to debug further.
This commit is contained in:
parent
69c258365b
commit
447abfee90
|
@ -71,6 +71,7 @@ class CachedTimelineRemoteMediator(
|
||||||
return try {
|
return try {
|
||||||
val response = when (loadType) {
|
val response = when (loadType) {
|
||||||
LoadType.REFRESH -> {
|
LoadType.REFRESH -> {
|
||||||
|
Timber.e(RuntimeException(), "Stack trace for LoadType.REFRESH")
|
||||||
val closestItem = state.anchorPosition?.let {
|
val closestItem = state.anchorPosition?.let {
|
||||||
state.closestItemToPosition(maxOf(0, it - (state.config.pageSize / 2)))
|
state.closestItemToPosition(maxOf(0, it - (state.config.pageSize / 2)))
|
||||||
}?.status?.serverId
|
}?.status?.serverId
|
||||||
|
|
Loading…
Reference in New Issue