Skip to content
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

useKeyboardAnimation hook is not respecting to keyboard size changes #54

Closed
kirillzyusko opened this issue Aug 17, 2022 · 0 comments · Fixed by #58
Closed

useKeyboardAnimation hook is not respecting to keyboard size changes #54

kirillzyusko opened this issue Aug 17, 2022 · 0 comments · Fixed by #58
Assignees
Labels
🤖 android Android specific 🐛 bug Something isn't working

Comments

@kirillzyusko
Copy link
Owner

Describe the bug

Animated values from useKeyboardAnimation are not reacting to keyboard size changes.

Repo for reproducing

Just open any screen (Animated transition, Chat) in example app and try to change the input mode (for example switch keyboard to emoji selection).

To Reproduce
Steps to reproduce the behavior:

  1. Go to Animated transition screen;
  2. Click on TextInput
  3. See that red and green circles have been moved accordingly.
  4. Change keyboard type to emoji selection
  5. See that red and green circles hasn't changed its position.

Expected behavior

Returned values from useKeyboardAnimation should respect to keyboard size changes and should update its values.

Screenshots

Actual Expected
image image

Using standard keyboard both circles are located above the keyboard, but when you change keyboard type - red circle (driven by useKeyboardAnimation) is getting overlapped by the keyboard.

Smartphone:

  • Desktop OS: Mac OS 12.5
  • Device: Pixel 3 (emulator)
  • OS: Android API 32
  • JS engine: JSC
  • Library version: 1.0.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤖 android Android specific 🐛 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant