-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[New architecture] The keyboard leaves empty space when dismissed #36664
Comments
Triggered auto assignment to @muttmuure ( |
Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Eep! 4 days overdue now. Issues have feelings too... |
not able to reproduce 👍 |
Still overdue 6 days?! Let's take care of this! |
10 days overdue. I'm getting more depressed than Marvin. |
12 days overdue now... This issue's end is nigh! |
this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
This issue has not been updated in over 14 days. eroding to Weekly issue. |
this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Huh... This is 4 days overdue. Who can take care of this? |
this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks! |
Job added to Upwork: https://www.upwork.com/jobs/~01a1e03c65b6df0aca |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @parasharrajat ( |
@parasharrajat Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Closing this one as the purpose of this issue is mainly for tracking and retest once the fabric PR hits staging |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
This issue is related to the ongoing new architecture adoption. It was reported on the build with new architecture enabled on the relevant PR.
Version Number: 1.4.42-1
Reproducible in staging?: no
Reproducible in production?: no
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @ishpaul777 here and here
Slack conversation:
Action Performed:
Tap on any text input to open the keyboard, then navigate back. The flow that allowed to consistently reproduce this issue was:
Assign task
Next
with the keyboard still openExpected Result:
The screen being navigated to should be filling the entire screen.
Actual Result:
There is a blank space where the keyboard has been.
Workaround:
Unknown, should be fixed by 2894ec0 and 39ef764
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
keyboard-space1.mp4
keyboard-space2.mp4
keyboard-task.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: