Small issue with panGestureAnimatedValue
See original GitHub issueDescribe the bug When I use the prop “panGestureAnimatedValue” to animate a pitch black background from 1 to 0 doing this quickly after the modal opened, it looks like that animated value is set too late. I have attached a video to demonstrate the issue. If I wait a second before I drag down, everything is fine but when I start dragging instantly there is a issue. Things getting worse when there is a scale animation (which I’ve disabled for now).
I tried to write the value like in your example using a useRef
and also tried to use a plain let
for it. It didn’t change anything. You can see, that the value is missing sometimes for a second.
Reproduce https://streamable.com/ojmrvt
Dependencies:
- react-native-modalize 2.0.3
- react-native: EXPO SDK 37
- react-native-gesture-handler: EXPO SDK 37
- expo/react-navigation/react-native-navigation: [e.g. expo@37.0.11]
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Modalize, a highly customizable modal/bottom sheet that ...
We now only have ~8 issues opened, for ~92 closed, which is a pretty good number and we have been able to fix...
Read more >Bountysource
panGestureAnimatedValue is animated to 0 instead of 1 when calling open("top") with alwaysOpen option.
Read more >Jenkins aws credentials iam role
In the case of Jenkins, we can identify four main issues :. All reactions. And then you can run:. ... Next issue Small...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jeremybarbet I’ve done some debugging and I believe it is this block that is causing the issue:
Setting
toPanValue
to 1 in the first block fixes this specific issue. I haven’t had enough time to grasp what exactly this code is doing so I don’t know if that would break other things, but it fixes it for me (I’m also using alwaysOpen).Is this a valid solution?
ping @jeremybarbet