Fixed
Status Update
No update yet.
Comments
su...@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.
ch...@gmail.com
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.
[Deleted User] <[Deleted User]>
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.
ro...@gmail.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.
ch...@instacart.com
[Comment deleted]
Description
Version used: 1.0.0-alpha12
After upgrading to alpha12, all of my Workers written in Kotlin (and CoroutineWorkers, FWIW), complain about the 'Result' return value with an error that says: "One type argument expected for class Result<out T>"
It appears that the Kotlin standard library contains a public inline Result class already:
The Kotlin Result class is automatically available in every file, so Android Studio (3.2.1) doesn't offer to import the androidx.work.Result class, causing the error since it assumes you want to use the already available kotlin Result.
There were two workarounds, neither very friendly:
1) Use the fully qualified androidx.work.Result
2) Manually adding the androidx.work.Result import statement
Note that:
- Using the fully qualified name, then using the Android Studio option to add import did not work
- Removing the doWork method entirely and using Android Studio's quick fix to implement the method did add an import to androidx.work.Result, so new classes would avoid running into this issue.