You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Awaiting Checklist Completion] Workspace - Unsupported browser notification appears on the Xero setup page (Android) #41512
issue found when validating #41415 Version Number: 1.4.70-0 Reproducible in staging?: y Reproducible in production?: y 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 Expensify/Expensify Issue URL: Issue reported by: Applause internal Slack conversation:
Action Performed:
Log in with a new expensifail account
Create a workspace
Enable "Accounting" on the WS settings page
Navigate to "Accounting"
Tap on the "Set up" button next to Xero
Expected Result:
The browser should be switched to a supported one or if it's not possible, the notification shouldn't appear for users.
Actual Result:
Unsupported browser notification appears on the Xero setup page.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
@twisterdotcom FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
changed the title [-]Workspace - Unsupported browser notification appears on the Xero setup page[/-][+][$250] Workspace - Unsupported browser notification appears on the Xero setup page[/+]on May 3, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.73-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@mananjadhav] The PR that introduced the bug has been identified. Link to the PR:
[@mananjadhav] 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:
[@mananjadhav] 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:
[@mananjadhav] Determine if we should create a regression test for this bug.
[@mananjadhav] 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.
[@twisterdotcom] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
changed the title [-][HOLD for payment 2024-05-22] Workspace - Unsupported browser notification appears on the Xero setup page (Android)[/-][+][Awaiting Checklist Completion] Workspace - Unsupported browser notification appears on the Xero setup page (Android)[/+]on May 22, 2024
There is no offending PR for this one. We're using WebView and we added this as a follow up. Additionally we don't need a regression test for this one.
@twisterdotcom Payout for me will be after the whole Xero as a flat fee.
Activity
melvin-bot commentedon May 2, 2024
Triggered auto assignment to @twisterdotcom (
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.m-natarajan commentedon May 2, 2024
@twisterdotcom FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
m-natarajan commentedon May 2, 2024
We think that this bug might be related to #wave-collect - Release 1
twisterdotcom commentedon May 3, 2024
Trying to recreate on iOS, my Android phone is at home. Added my test domain to the xero beta
twisterdotcom commentedon May 3, 2024
Hmm, not an issue on iOS:

twisterdotcom commentedon May 3, 2024
Confirmed: https://expensify.slack.com/archives/C01SKUP7QR0/p1714742239560959?thread_ts=1714741936.915729&cid=C01SKUP7QR0
[-]Workspace - Unsupported browser notification appears on the Xero setup page[/-][+][$250] Workspace - Unsupported browser notification appears on the Xero setup page[/+]melvin-bot commentedon May 3, 2024
Job added to Upwork: https://www.upwork.com/jobs/~01609688787adfdcff
melvin-bot commentedon May 3, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee (
External)25 remaining items
melvin-bot commentedon May 15, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 15, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.73-7 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 2024-05-22. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 15, 2024
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
twisterdotcom commentedon May 22, 2024
Payment Summary:
twisterdotcom commentedon May 22, 2024
Waiting on you @mananjadhav for the checklist.
[-][HOLD for payment 2024-05-22] Workspace - Unsupported browser notification appears on the Xero setup page (Android)[/-][+][Awaiting Checklist Completion] Workspace - Unsupported browser notification appears on the Xero setup page (Android)[/+]mananjadhav commentedon May 25, 2024
There is no offending PR for this one. We're using WebView and we added this as a follow up. Additionally we don't need a regression test for this one.
@twisterdotcom Payout for me will be after the whole Xero as a flat fee.
melvin-bot commentedon May 28, 2024
@mananjadhav, @twisterdotcom, @lakchote, @gijoe0295 Whoops! This issue is 2 days overdue. Let's get this updated quick!