Repository navigation
Preferences - Mute all sounds from Expensify toggle does not update on secondary device #36487
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: 1.4.41-2
Reproducible in staging?: Y
Reproducible in production?: No, new feature
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4312305
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:
- Log in to New Expensify on two devices with the same account
- Navigate to Preferences
- [Main device] Use both toggles below Notifications to change their state
Expected Result:
Toggles should update on secondary device to reflect changes made in main device
Actual Result:
Contrary to the other toggle, the "Mute all sounds from Expensify" toggle does not update on secondary device.
Workaround:
Unknown
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
Activity
github-actions commentedon Feb 14, 2024
👋 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:
melvin-bot commentedon Feb 14, 2024
Triggered auto assignment to @dangrous (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.jayeshmangwani commentedon Feb 14, 2024
@dangrous Seems like a backend issue, pusher data is not updated when toggle the sound preference
dangrous commentedon Feb 14, 2024
Let me see if this is intended or not, I feel like there was some discussion around it that I recall, and it might be expected behavior?
EDIT: expected - #31055 (comment)
dangrous commentedon Feb 14, 2024
Either way this should definitely not be a deploy blocker, as the syncing never existed in the first place.
Primarily just trying to figure out if we should keep this issue open to have it call the BE or leave it and do nothing.
dangrous commentedon Feb 14, 2024
@Beamanator I see you're assigned to #36455 - I think we only need one of these; which would you prefer to keep open?
Beamanator commentedon Feb 14, 2024
Haha good point!
I'd say the one I'm assigned to just cuz it's been opened longer? Maybe? Feel free to take over, I don't need an extra issue or anything hahaha
m-natarajan commentedon Aug 5, 2024
Reopening as this issue is reproducible as per this https://expensify.slack.com/archives/C049HHMV9SM/p1722620957808589
dangrous commentedon Aug 5, 2024
Reclosing as expected, details here - https://expensify.slack.com/archives/C049HHMV9SM/p1722872455095589?thread_ts=1722620957.808589&cid=C049HHMV9SM