-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2022-09-20] [HOLD for payment 2022-08-01] [$250] Android - Keyboard doesn't always open on search (reported by @jayeshmangwani) #9827
Comments
Triggered auto assignment to @laurenreidexpensify ( |
Triggered auto assignment to @sketchydroide ( |
this seems to not be a problem in iOS, maybe just Android? |
Triggered auto assignment to @kevinksullivan ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Current assignee @sketchydroide is eligible for the Exported assigner, not assigning anyone new. |
Also applicable to |
ProposalLine 179 in ce89922
Solution:
Tried using the upper prop works fine now. @rushatgabhane @kevinksullivan @sketchydroide |
🎀 👀 🎀 C+ reviewed cc: @sketchbook |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
@rushatgabhane can you let us know if this caused a regression? |
Triggered auto assignment to @kevinksullivan ( |
Triggered auto assignment to @michaelhaxhiu ( |
Reassigning as I'm OOO for a bit. Thanks @michaelhaxhiu ! |
I don't think so, I can't repro the regression - #10414 (comment) |
This seems ready for payment! I'm going to work on that now. |
Done. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.99-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2022-09-20. 🎊 |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Note: try 3-4 times issue is inconsistent
Expected Result:
Keyboard should always open
Actual Result:
Sometimes does not open
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.82.5
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): any
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
search-keyboard.mp4
Expensify/Expensify Issue URL:
Issue reported by: @jayeshmangwani
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1656618123670899
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: