-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Black area appears after keyboard dismissed #1422
Comments
Thanks for the demo project. I'll try to check what might be the cause of this issue. |
I have a similar problem. In my case, after an incomplete interactive pop, it slides down the whole view and it leaves there. I think the root of the problem is the same. |
Hi, I have the same problem, so, how to solve this problem? @hackiftekhar |
@pockerhead which version of library you are using? |
Using IQKeyboardManagerSwift (6.2.0) ,,,,this is my used version |
okay, can you please share a demo project? |
@superdev89 It is already been fixed with the v6.0.5, this is similar issue of #1361. Enjoy! |
Hello! I use new 6.3.0 pod version and I have this issue too. I didn't use some beginFirstResponder, just open keyboard and swipe back to pop view controller. It works only if u will swipe back but swipe right, not letting go of your finger. so that there is no going back. And u will see black space |
@SonnyMore Please share a video and demo project to demonstrate the issue with v6.3.0. |
Describe the bug
Black area appears in the place of keyboard when popping the view controller by swiping.
I build a chat view controller by placing table view and textfield and buttons to send chat like the screenshot below.
After trying swipe to popup(not popped completely, released touch and stayed back in chat screen), black area appeared.
Versions
Xcode: 9.4.1
iOS: 11.3
Mac OS: xx.xx.x
Device: iPhone X, iPhone 6
Simulator/Device Name: iPhone 8
Library Version: 6.0.4
###Demo Project
https://www.dropbox.com/s/fry8b4bbh5wpzar/KeyboardDemo.zip?dl=0
The text was updated successfully, but these errors were encountered: