-
-
Notifications
You must be signed in to change notification settings - Fork 100
Unable to mount KeyboardProvider
without animations freezing
#842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Possibly relevant dependencies I'm using
|
I discovered that what's happening is that:
|
Sounds very similar to #750 @denysoleksiienko is that something that you experienced as well? I. e. that This is actually very strange, because what However I may assume, that @smhutch one advice I can give to you is to try to remove/simplify In example app I also use bottom-sheet component, but it works well in example app 🤷♂ So my current advice is to try to remove line-by-line of the code in |
In my case, all animations freeze when I use react-native 0.76+ (NEW ARCH) and reanimated 3.15+. |
@kirillzyusko I have managed to get this working now. I think I was just being a n00b and not rebuilding my Expo app fully in development. |
Describe the bug
I assume this is an integration issue with some of my other dependencies, but I'm a bit lost on what' I'm doing wrong. In short, I am mounting a
KeyboardProvider
(following this guide), and this causes my entire app to freeze. All reanimated-driven animations fail to run.This issue happens even if I mount the
KeyboardProvider
withenabled:false
.I have recorded a Loom with a demo of the issue I'm facing.
Code snippet
I am simply mounting a
KeyboardProvider
at the root of my application. I have tried mounting it at the very top, and also inside some other third-party providers. The same issue appears to occur regardless of where I mount it.Repo for reproducing
No minimal repro available yet. I can prepare one soon unless I learn of a quick fix for this.
To Reproduce
Mount
KeyboardProvider
anywhere in app tree.Expected behavior
App continues to render as normal.
Screenshots
Loom with a demo.
Smartphone (please complete the following information):
Additional context
I assume I'm missing something obvious here. Mostly seeking advice on this one.
The text was updated successfully, but these errors were encountered: