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
[$500] Android - Split scan - Unable to select workspace as recipient when creating split scan in WS chat #32810
Version Number: v1.4.11-1 Reproducible in staging?: y Reproducible in production?: n 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 Team Slack conversation:
Action Performed:
Launch New Expensify app.
Go to workspace chat > + > Request money.
Tap Split bill > Scan.
Upload a photo.
Note that we cannot select a workspace in participant page although we are now in the workspace chat.
Expected Result:
User will be redirected to the confirmation page without the need to select a workspace since user is already in the workspace chat.
Actual Result:
User is redirected to participant selection page and there is no way to select a workspace since workspace is not in the list.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Android - Split scan - Unable to select workspace as recipient when creating split scan in WS chat[/-][+][$500] Android - Split scan - Unable to select workspace as recipient when creating split scan in WS chat[/+]on Dec 11, 2023
📣 @mkhutornyi 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Activity
github-actions commentedon Dec 11, 2023
👋 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 Dec 11, 2023
Triggered auto assignment to @rlinoz (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.tgolen commentedon Dec 11, 2023
I'll take this and look into it.
melvin-bot commentedon Dec 11, 2023
Triggered auto assignment to @anmurali (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Dec 11, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)[-]Android - Split scan - Unable to select workspace as recipient when creating split scan in WS chat[/-][+][$500] Android - Split scan - Unable to select workspace as recipient when creating split scan in WS chat[/+]11 remaining items
melvin-bot commentedon Dec 11, 2023
📣 @0xmiroslav 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!
Offer link
Upwork job
melvin-bot commentedon Dec 11, 2023
📣 @mkhutornyi 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖
melvin-bot commentedon Dec 12, 2023
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Jan 3, 2024
This issue has not been updated in over 15 days. @tgolen, @anmurali, @0xmiroslav, @mkhutornyi eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
0xmiroslav commentedon Jan 3, 2024
Automation didn't work. This is awaiting payment
mallenexpensify commentedon Jan 24, 2024
Contributor: @mkhutornyi paid $500 via Upwork
Contributor+: @0xmiroslav owed $500 via Upwork
I saw another contributor was hired, Volodymry L, but I don't see a reference here for work they've completed so I didn't pay.
PR hit production over a month ago, automation wasn't working so the
Reviewinglabel wasn't removed and this hasn't gone overdue.Think we're good to close this