Skip to content

[HOLD for payment 2023-04-12] Web - Chat - User can't type second ":" to finish emoji input in edit mode #16896

Closed

Description

@kbecciv

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Launch the application staging.new.expensify.com
  2. Open any chat
  3. Send a message that includes emojis
  4. Edit the message with the emojis. Try to add new emojis

Expected Result:

User can successfully edit a message with an emoji. User can add a new emoji to the message.

Actual Result:

User can't type second ":" to finish emoji input in edit mode.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.2.94.0

Reproducible in staging?: Yes

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

Notes/Photos/Videos: Any additional supporting documentation

Bug6004945_emoji-edit.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 3, 2023
  2. MelvinBot commented on Apr 3, 2023

    @MelvinBot
    Contributor

    Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. added
    DeployBlockerCashThis issue or pull request should block deployment
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 3, 2023
  4. MelvinBot commented on Apr 3, 2023

    @MelvinBot
    Contributor

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  5. OSBotify commented on Apr 3, 2023

    @OSBotify
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. MelvinBot commented on Apr 3, 2023

    @MelvinBot
    Contributor

    Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  7. 23 remaining items

  8. Beamanator commented on Apr 11, 2023

    @Beamanator
    Contributor

    Not sure how this got "deployed" twice, but let's go with the original payment date, 04-12

  9. changed the title [-][HOLD for payment 2023-04-13] [HOLD for payment 2023-04-12] Web - Chat - User can't type second ":" to finish emoji input in edit mode[/-] [+][HOLD for payment 2023-04-12] Web - Chat - User can't type second ":" to finish emoji input in edit mode[/+] on Apr 11, 2023
  10. Santhosh-Sellavel commented on Apr 13, 2023

    @Santhosh-Sellavel
    Collaborator
  11. garrettmknight commented on Apr 14, 2023

    @garrettmknight
    Contributor

    Thanks! @Santhosh-Sellavel offer sent to you.

    @fedirjh also sent you an offer since you proposed the solution we ended up going with.

  12. Santhosh-Sellavel commented on Apr 14, 2023

    @Santhosh-Sellavel
    Collaborator

    @garrettmknight Offer says withdrawn can you send again thanks!

  13. garrettmknight commented on Apr 17, 2023

    @garrettmknight
    Contributor

    Weird, just resent!

  14. garrettmknight commented on Apr 17, 2023

    @garrettmknight
    Contributor

    Paid!

  15. fedirjh commented on May 12, 2023

    @fedirjh
    Contributor

    cc @garrettmknight , I am still seeing the contract as open with remaining milestone as unpaid , could you please verify
    https://www.upwork.com/nx/wm/workroom/33331313/details

  16. garrettmknight commented on Jul 21, 2023

    @garrettmknight
    Contributor

    @fedirjh sorry about that, just caught this notification after being out for a few months. Paid and closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions