Fixed
Status Update
Comments
se...@google.com <se...@google.com>
br...@pappin.ca <br...@pappin.ca> #2
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?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
br...@pappin.ca <br...@pappin.ca> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ma...@google.com <ma...@google.com>
ma...@google.com <ma...@google.com>
ap...@google.com <ap...@google.com> #4
-
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.
Description
Observed Behaviour
The
PullToRefreshContainer
leaves an outline of the indeterminate indicator on the screen, even when the state is not refreshing.Expected Behaviour
The expected behaviour is that PullToRefreshContainer would hide all traces, including that outer box with a background colour, based on the PullToRefreshState state.
Steps to Reproduce
This is the outer Box in PullToRefreshContainer, which has the background colour set to
containerColor: Color = PullToRefreshDefaults.containerColor
, and does not get hidden when isRefreshing is false. See: PullToRefresh.kt:135To reproduce, and check this accuracy, simple set the containerColor on the PullToRefreshContainer, like this:
Other Notes
This is somewhat related to: https://issuetracker.google.com/issues/261760718