Fixed
Status Update
No update yet.
Comments
ap...@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.
ap...@google.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.
ap...@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.
ap...@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.
Description
Component used: Fragment
StrictModeWe should build the same type of infrastructure for Fragments so that developers can enable runtime checking for bad behaviors and validate that they (or libraries they depend on) aren't using deprecated APIs or known potential problematic behaviors.
Importantly, this should only be as a second line of defense behind deprecation warnings or Lint warnings to catch these issues at build time or to handle cases where third party libraries / dependencies are triggering these behaviors so that bugs can be filed against them.
We should support at least
penaltyLog(),penaltyDeath(), andpenaltyListener().Given that we should maintain behavior compatibility, we should not add any
enableDefaults()ordetectAll()methods and instead have developers opt into exactly thedetect***()methods they want. This should also remove the need forpermit***()methods since they'll all default to off.Ideally, this is something that developers can either:
Set globally via
FragmentStrictMode.setDefaultPolicy(FragmentStrictMode.Policy)Set on a specific
FragmentManager(and its childrenFragmentManagers) viafragmentManager.setStrictModePolicy(FragmentStrictMode.Policy)(this would override the default policy)This API shouldn't be made public until there is at least two
detect***()calls added. These will be filed as separate issues.