Retry does not work after initial load [160194384]

Fixed

Bug

Status Update

No update yet.

Description

ma...@justpinch.com

created issue #1

Jun 30, 2020 04:17PM

Component used: Paging 3.0.0
Version used: alpha02
Devices/Android versions reproduced on: Nokia 7.1/Android 10

Steps to reproduce:

Clone the paging codelab on branch step11_loading_state: https://github.com/googlecodelabs/android-paging/tree/step11_loading_state
Update to the paging version to alpha02
Compile & launch sample app
Make the data load that fetches the 2nd page of Github repos fail (e.g. throw an IOException, use airplane mode etc)
Scroll all the way down to the "Retry" button
Observe nothing appears to happen when tapping the retry button

Sample project illustrating the problem attached for convenience.

I've confirmed the retry call makes it all the way up to PageFetcherSnapshot and is collected from retryChannel. From there I got lost in the world of suspend functions and breakpoints without any useful context...

Further observations:

Could not reproduce this issue with version alpha01.
Retry works as expected when the initial data load fails (set FAIL to ON_INITIAL_LOAD in GithubPagingSource to confirm)

android-paging-sample-retry-broken-on-alpha02.zip

166 KB

Download

Comments

du...@google.com <du...@google.com> #2Jun 30, 2020 09:17PM

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

ap...@google.com <ap...@google.com> #3Jul 1, 2020 06:31PM

Marked as fixed.

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

ma...@justpinch.com <ma...@justpinch.com> #4Jul 2, 2020 06:13AM

Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
Dynamic features are not used in the application.

As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.

Issue 160194384

Description

Issue summary

Comments

du...@google.com <du...@google.com> #2Jun 30, 2020 09:17PM

ap...@google.com <ap...@google.com> #3Jul 1, 2020 06:31PM

ma...@justpinch.com <ma...@justpinch.com> #4Jul 2, 2020 06:13AM

Add comment

Issue metadata