-
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
[$500] Android - Chat - Keyboard does not pull up when editing the message #30991
Comments
Job added to Upwork: https://www.upwork.com/jobs/~011928df9e6f1e55ee |
Triggered auto assignment to @alexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
Not reproducible in production Screen_Recording_20231107_112754_New.Expensify.mp4 |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @cristipaval ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.The edit composer is focused but the keyboard does not pull up. What is the root cause of that problem?In here, we're having the focusing logic after the delay, which works well for all platforms. However, recently this focus logic is added to fix a bug. But we didn't use the correct What changes do you think we should make in order to solve the problem?Use this correct focus function in here rather than triggering the We might need to move this scroll logic to inside What alternative solutions did you explore? (Optional)Calling these focus and scrollTop only on iOS and mWeb (the platforms where that code is supposed to fix) |
Thanks, @dukenv0307 for the proposal. What happens if the user taps again on the input field? Does the keyboard show up? I would like to know if removing the deploy blocker label and fixing it without rushing makes sense. |
@cristipaval if the user taps again, the keyboard does show up. It's very inconvenient though, when the user edit any message, they have to tap like that. |
Alright, thanks @dukenv0307! Given that the keyboard shows up if the user explicitly taps on the input field, I'll consider this a minor issue that shouldn't block the deployment. I just removed |
@mananjadhav could you please check if the proposed solution works? |
@mananjadhav, @alexpensify, @cristipaval Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I think @dukenv0307's proposal will work. Will have to make sure 🎀 👀 🎀 C+ reviewed. |
Current assignee @cristipaval is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new. |
This was deploy blocker. What's offending PR? |
The follow up PR #31041 is already merged to fix the keyboard issue in android... |
Thanks for your help @cristipaval! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Found when executing PR : #30669
Version Number: v1.3.96-0
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause-Internal Team
Slack conversation: @
Action Performed:
Expected Result:
The keyboard will pull up.
Actual Result:
The edit composer is focused but the keyboard does not pull up.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6267190_1699355804164.Screen_Recording_20231107_121932_New_Expensify.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mananjadhavThe text was updated successfully, but these errors were encountered: