Repository navigation
[$250] Hybrid - Android - Chat - Keyboard is not displayed when editing a message. #56311
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.94-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
Email or phone of affected tester (no customers): ibellicotest+231@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12
App Component: Chat Report View
Action Performed:
- Open the Expensify app.
- Open any chat with messages or send a few.
- Long tap over any message and tap on "Edit Message"
- Check if the keyboard is displayed when trying to edit message.
- If keyboard is displayed, close the edition composer and repeat steps 3 and 4.
Expected Result:
Keyboard should be displayed everytime the user tries to edit a message.
Actual Result:
Keyboard is not always displayed when the user tries to edit a message in chat.
Workaround:
Unknown
Platforms:
- Android: Standalone
- Android: HybridApp
- Android: mWeb Chrome
- iOS: Standalone
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Bug6732957_1738661701396.Edit_Key.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021886807913878809914
- Upwork Job ID: 1886807913878809914
- Last Price Increase: 2025-02-11
Activity
melvin-bot commentedon Feb 4, 2025
Triggered auto assignment to @johncschuster (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Feb 4, 2025
Triggered auto assignment to @madmax330 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 4, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Feb 4, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
IuliiaHerets commentedon Feb 4, 2025
Production behaviour
XRecorder_04022025_124849.mp4
madmax330 commentedon Feb 4, 2025
I think this can be external
55 remaining items
johncschuster commentedon Feb 19, 2025
Thanks, @hoangzinh! I've gone ahead and updated the issue title to reflect that.
johncschuster commentedon Mar 4, 2025
How's this going, @jnowakow?
jnowakow commentedon Mar 4, 2025
I've been looking at it but I'm not focusing on it very much :/ There were changes in app that changed a bit autofocus behaviour
hoangzinh commentedon Mar 4, 2025
@madmax330 I'm thinking, should we consider if it's an acceptable fix of the temporary solution here #56408. I feel it's not worth investing, instead, we can focus on other things that bring more value to customers. Let me know if you still want to find a better solution for this bug.
mateuuszzzzz commentedon Mar 7, 2025
I agree that this is not a very urgent task, but it would still be good to introduce a cleaner approach here. Perhaps changing this to a monthly task makes sense 🤔 Someone from our team will continue working on it once we have a bit more time 😅
mvtglobally commentedon Mar 7, 2025
Issue not reproducible during KI retests. (First week)
mvtglobally commentedon Mar 15, 2025
Issue not reproducible during KI retests. (Second week)
johncschuster commentedon Mar 19, 2025
It looks like this was fixed in this PR, is that right, @hoangzinh?
hoangzinh commentedon Mar 19, 2025
Yes, it's correct @johncschuster. But please note that it was just a temporary solution to fix DB, then @jnowakow tried to make another PR #56881 to improve it, but it didn't work. I'm also waiting @madmax330 on my suggestion here
madmax330 commentedon Mar 20, 2025
@hoangzinh from this comment here: #56311 (comment)
I think I agree that if it's working and not reproducible we can just close this and focus on more urgent tasks
hoangzinh commentedon Mar 21, 2025
@johncschuster if you also agree with @madmax330. Can you post payment summary and we're good to close this issue.
johncschuster commentedon Mar 21, 2025
Payment Summary
Contributor: @mateuuszzzzz does not require payment (Contractor)
Contributor+: @hoangzinh owed $250 via NewDot
hoangzinh commentedon Mar 21, 2025
Requested payment in ND
garrettmknight commentedon Mar 21, 2025
$250 approved for @hoangzinh