Skip to content

[PAID] [$250] Android - Chat - When navigating to WS link, chat is seen on the background while loading #53345

Closed

Description

@IuliiaHerets

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: 9.0.69-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): ibellicotest+57@gmail.com
Issue reported by: Applause Internal Team

Action Performed:

  1. Open the Expensify app.
  2. Tap on "Settings"
  3. Tap on "Workspaces" and select any workspace.
  4. Tap on "Profile" and navigate to share code.
  5. Tap on "Copy URL"
  6. Navigate back to LHN and open any chat,
  7. Paste the workspace share code.
  8. Tap on the URL.
  9. Verify you are automatically navigated to workspace profile.

Expected Result:

The user should be automatically navigated to workspace profile after tapping on the URL.

Actual Result:

Chat can be seen on the background, with a loading spinner, for a few seconds, before the user is navigated to the workspace profile after tapping on the URL on chat.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6680852_1732994632298.URL.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @strepanier03
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021863541156905286108
  • Upwork Job ID: 1863541156905286108
  • Last Price Increase: 2024-12-02
  • Automatic offers:
    • daledah | Contributor | 105155655
    • dominictb | Contributor | 105399428

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 30, 2024
  2. melvin-bot commented on Nov 30, 2024

    @melvin-bot

    Triggered auto assignment to @strepanier03 (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.

  3. melvin-bot commented on Nov 30, 2024

    @melvin-bot

    Triggered auto assignment to @yuwenmemon (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Nov 30, 2024

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Nov 30, 2024

    @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.
  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Dec 1, 2024
  7. 40 remaining items

  8. strepanier03 commented on Dec 20, 2024

    @strepanier03
    Contributor

    I am now out of the office until January 3.

    When the checklist is completed, please post in Slack and request help to pay the Upwork contract.

  9. dominictb commented on Dec 24, 2024

    @dominictb
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] 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: https://github.com/Expensify/App/pull/37525/files#r1896349995

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: NA

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Test:

    1. Open Settings > Workspaces
    2. Select a workspace
    3. Open Profiles > Share > Copy URL
    4. Go to any chat
    5. Send copied URL
    6. Press on URL
    7. Verify that: if loading indicator is shown, it is shown on a blank background (instead of a transparent overlay)

    Do we agree 👍 or 👎

  10. melvin-bot commented on Dec 24, 2024

    @melvin-bot

    @strepanier03, @mountiny, @dominictb, @daledah Whoops! This issue is 2 days overdue. Let's get this updated quick!

  11. melvin-bot commented on Dec 26, 2024

    @melvin-bot

    @strepanier03, @mountiny, @dominictb, @daledah Huh... This is 4 days overdue. Who can take care of this?

  12. melvin-bot commented on Dec 28, 2024

    @melvin-bot

    @strepanier03 @mountiny @dominictb @daledah this issue is now 4 weeks old, please consider:

    • Finding a contributor to fix the bug
    • Closing the issue if BZ has been unable to add the issue to a VIP or Wave project
    • If you have any questions, don't hesitate to start a discussion in #expensify-open-source

    Thanks!

  13. melvin-bot commented on Dec 30, 2024

    @melvin-bot

    @strepanier03, @mountiny, @dominictb, @daledah 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  14. melvin-bot commented on Jan 1, 2025

    @melvin-bot

    @strepanier03, @mountiny, @dominictb, @daledah 10 days overdue. I'm getting more depressed than Marvin.

  15. melvin-bot commented on Jan 3, 2025

    @melvin-bot

    @strepanier03, @mountiny, @dominictb, @daledah 12 days overdue. Walking. Toward. The. Light...

  16. strepanier03 commented on Jan 3, 2025

    @strepanier03
    Contributor

    Payment Summary

  17. strepanier03 commented on Jan 3, 2025

    @strepanier03
    Contributor

    Back from OoO 👋 I've paid both offers and closed the contracts in Upwork. I created the reg test request as well. Closing this out, thanks everyone!

  18. moved this from Hold for Payment to Done in #expensify-bugson Jan 3, 2025
  19. changed the title [-][Payment 2024-12-16] [$250] Android - Chat - When navigating to WS link, chat is seen on the background while loading[/-] [+][PAID] [$250] Android - Chat - When navigating to WS link, chat is seen on the background while loading[/+] on Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions