Fixed
Status Update
No update yet.
Comments
ra...@google.com
We are not able to reproduce this issue on Nexus 6P, NPF26F build with plaid app version=0.9.9
Can you provide the below requested information to better understand the issue:
Android build
Which Android build are you using? (e.g. KVT49L)
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Also please mention the Plaid app version.
Can you provide the below requested information to better understand the issue:
Android build
Which Android build are you using? (e.g. KVT49L)
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Also please mention the Plaid app version.
st...@baramundi.de
I'm also using Nexus 6P with NPF26F and plaid 0.9.9 installed from the play store.
It happens 100% of the time but the RecyclerView has to be positioned in such a way that the animation would make the bottom comment drop off the bottom of the screen. Then click an item quickly several times without letting the expand animation complete and it will crash after several clicks.
It happens 100% of the time but the RecyclerView has to be positioned in such a way that the animation would make the bottom comment drop off the bottom of the screen. Then click an item quickly several times without letting the expand animation complete and it will crash after several clicks.
ra...@google.com
Thanks for the detailed inputs.
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
ra...@google.com
ra...@google.com
I'm getting the same crash when using TransitionManager to animate the RecyclerView's bounds (changing the constraintSet with ConstraintLayout) if the user is interacting with the list. The problem doesn't occur if the user is not interacting with the list during the transition.
ap...@google.com
[Comment deleted]
st...@baramundi.de
[Comment deleted]
ra...@google.com
[Comment deleted]
Description
Version used: 1.0.0-alpha08
Devices/Android versions reproduced on: Moto G5s Plus, Android 7.1.1 / Huawai P20 lite, Android 8.0.0
We can reproduce a crash of the workmanager on some devices.
In our code we enqueue a UniqueWork with ExistingWorkPolicy.REPLACE, as soon as it finishes with State.SUCEEDED we enqueue it again. There is always only one job at the time.
After about 100 jobs the workmanager crashes with: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs.
It looks like the workmanager does not prune the finished jobs fast enough, and they count as 'sheduled' job, even if they are finished?
The crash is reproducible on the Moto G5s Plus and Huawai P20 lite. But it behaves very inconsistent, sometimes it occurs on the first run, sometimes only after a few restarts of the app. But we cannot reproduce it on the Pixel 2 XL or the emulator.
Calling pruneWork() before enqueue() doesn't fix the problem.
Reducing the result lifetime by calling keepResultsForAtLeast(..) doesn't work as well.
We provided a sample app which triggers the issue.