Skip to content

[$500] Android - Split scan - Unable to select workspace as recipient when creating split scan in WS chat #32810

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!


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:

  1. Launch New Expensify app.
  2. Go to workspace chat > + > Request money.
  3. Tap Split bill > Scan.
  4. 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?

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6308990_1702303061277.Screen_Recording_20231211_200248_New_Expensify.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0135d3b2a39137f316
  • Upwork Job ID: 1734225777714790400
  • Last Price Increase: 2023-12-11
  • Automatic offers:
    • 0xmiroslav | Reviewer | 28035664
    • mkhutornyi | Contributor | 28035665
Issue OwnerCurrent Issue Owner: @anmurali

Activity

  1. github-actions commented on Dec 11, 2023

    @github-actions
    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.
  2. melvin-bot commented on Dec 11, 2023

    @melvin-bot

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

  3. tgolen commented on Dec 11, 2023

    @tgolen
    Contributor

    I'll take this and look into it.

  4. assigned and unassigned on Dec 11, 2023
  5. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 11, 2023
  6. melvin-bot commented on Dec 11, 2023

    @melvin-bot

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

  7. melvin-bot commented on Dec 11, 2023

    @melvin-bot

    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
  8. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Dec 11, 2023
  9. 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
  10. 11 remaining items

  11. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Dec 11, 2023
  12. melvin-bot commented on Dec 11, 2023

    @melvin-bot

    📣 @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

  13. melvin-bot commented on Dec 11, 2023

    @melvin-bot

    📣 @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 📖

  14. melvin-bot commented on Dec 12, 2023

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  15. melvin-bot commented on Jan 3, 2024

    @melvin-bot

    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!

  16. 0xmiroslav commented on Jan 3, 2024

    @0xmiroslav
    Contributor

    Automation didn't work. This is awaiting payment

  17. mallenexpensify commented on Jan 24, 2024

    @mallenexpensify
    Contributor

    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 Reviewing label wasn't removed and this hasn't gone overdue.

    Think we're good to close this

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions