-
Notifications
You must be signed in to change notification settings - Fork 2
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
iPhone X - Space above keyboard #10
Comments
@markst What do you reckon? I know that the fix that we merged the other day worked for you, but for some reason it didn't work when I tried it (both in a simulator and a device), so I replaced it with the code I posted above to make it work. But maybe I'm doing something wrong...? |
Yo @ezescaruli. Thanks for the concise issue report. Are you sure you're using the The |
@markst So, the sign up button bottom constraint looks like this:
Yep that's right, however the issue in my case is that the execution is not reaching that line because both [self.firstItem conformsToProtocol:@protocol(UILayoutSupport)] and [self.secondItem conformsToProtocol:@protocol(UILayoutSupport)] resolve to |
@ezescaruli as mentioned you need to use the |
@markst I don't have the bottom layout guide among the options 🤔 I could probably make it appear if I disable |
@markst Perfecto, I'll give a try and check if the fix I made above works for the bottom layout guide too 👍 |
I've tried
KeyboardConstraint
in an iPhone X and it's having an issue when the keyboard appears. It looks like this (note the space between the sign up button and the keyboard):I debugged the point in which the keyboard appears:
KeyboardConstraint/KeyboardConstraint/KeyboardAdjustConstraint.m
Line 65 in bcd2a3e
and had this:
and then I did:
The debugger doesn't find the
UILayoutSupport
protocol declaration, which is weird...In runtime, what happens is that the above condition resolves to
NO
, so the execution never falls in the line that decrementskeyboardHeight
, and that's why we still have that extra space in the screenshot.I've tried replacing the fix with this, and it seems to be working fine:
The text was updated successfully, but these errors were encountered: