Skip to content

[Hold for payment - 2024-03-07] MEDIUM: Custom message sound not consistent on mobile #36579

Closed

Description

@Julesssss

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: 1.4.42-0
Reproducible in staging?: Yes

Action Performed:

  • Send a message to a user signed in on mobile in three different app states:
    • App Killed
    • App Open
    • App in background

Expected Result:

  • App Killed: Custom sound
  • App Open: Custom sound
  • App in background: Custom sound

Actual Result:

  • App Killed: Default notification sound
  • App Open: Custom sound
  • App in background: Default notification sound

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

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

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 15, 2024
  2. self-assigned this
    on Feb 15, 2024
  3. melvin-bot commented on Feb 15, 2024

    @melvin-bot

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

  4. kirillzyusko commented on Feb 15, 2024

    @kirillzyusko
    Contributor

    Thanks for bringing this up! As I have written that feature let me take some time trying to reproduce. I'll let you know if I found anything 👀

  5. Julesssss commented on Feb 15, 2024

    @Julesssss
    ContributorAuthor

    I can also help with backend changes. As you mentioned we may need to start sending a reportType variable -- though I also think we don't send IOU notifications currently

  6. Julesssss commented on Feb 19, 2024

    @Julesssss
    ContributorAuthor

    @kirillzyusko and I discussed. We can drop the message received sound on mobile apps as this is being handled by the OS push notification itself.

  7. 13 remaining items

  8. Julesssss commented on Feb 29, 2024

    @Julesssss
    ContributorAuthor

    Awaiting C+ payment

  9. changed the title [-]MEDIUM: Custom message sound not consistent on mobile[/-] [+][Hold for payment - 2024-03-07] MEDIUM: Custom message sound not consistent on mobile[/+] on Feb 29, 2024
  10. moved this from CRITICAL to MEDIUM in [#whatsnext] #vip-vsbon Mar 5, 2024
  11. abdulrahuman5196 commented on Mar 5, 2024

    @abdulrahuman5196
    Contributor

    The PR that introduced the bug has been identified. Link to the PR:
    The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

    Not a regression. Update to existing implementation

    Determine if we should create a regression test for this bug.

    Yes.

    If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

    1. Open app on two devices (A - iOS, B - Android)
    2. Send a message from device A to device B
    3. Be sure that you hear a custom sound only when message is received (plain messages)
    4. Send message from device B to device A
    5. Be sure that you hear a custom sound only when message is received (plain messages)
    6. Open app on two devices (any platforms, exclude iOS/Android platform)
    7. Send a message from device A to device B
    8. Be sure that sound can be heard
  12. Julesssss commented on Mar 5, 2024

    @Julesssss
    ContributorAuthor

    We're still making changes to the push notification logic so this test will soon be outdated. We'll create one seperately once the changes are complete.

  13. CortneyOfstad commented on Mar 11, 2024

    @CortneyOfstad
    Contributor

    Sorry, was OoO last week — handling the payment now!

  14. CortneyOfstad commented on Mar 11, 2024

    @CortneyOfstad
    Contributor

    @Julesssss in regards to the comment here, is a regression test needed here if there will be separate tests created after the logic is adjusted? Just trying to confirm — thank you!

  15. CortneyOfstad commented on Mar 11, 2024

    @CortneyOfstad
    Contributor

    @abdulrahuman5196 I sent you a job offer here — https://www.upwork.com/jobs/~01d297cc64a730c705

    Not sure why the job did not post originally, but please let me know once you accept and I'll get that paid ASAP. Thanks!

  16. abdulrahuman5196 commented on Mar 11, 2024

    @abdulrahuman5196
    Contributor

    @CortneyOfstad accepted the offer. Thank you

  17. CortneyOfstad commented on Mar 11, 2024

    @CortneyOfstad
    Contributor

    Paid!

    Payment Summary

    @abdulrahuman5196 — paid $500 via Upwork!

  18. Julesssss commented on Mar 12, 2024

    @Julesssss
    ContributorAuthor

    Hi @CortneyOfstad, no test needed here

  19. CortneyOfstad commented on Mar 12, 2024

    @CortneyOfstad
    Contributor

    Perfect! This can be closed — thanks everyone!

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.ReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions