Skip to content

[$250] Web - Chat - Composer is expanded briefly when returning to chat after creating new workspace #39252

Closed

Description

@lanitochka17

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.58-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to Profile > Workspaces
  3. Create a new workspace
  4. Click back button on the top left
  5. Click Chat icon on the bottom left

Expected Result:

The composer will not appear expanded when returning to chat

Actual Result:

The composer appears expanded briefly when returning to chat after creating a new workspace

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

Bug6431596_1711719926703.composer_expand.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0187883d3354706f5f
  • Upwork Job ID: 1776300112459137024
  • Last Price Increase: 2024-04-12

Activity

  1. melvin-bot commented on Mar 29, 2024

    @melvin-bot

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

  2. github-actions commented on Mar 29, 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.
  3. ZhenjaHorbach commented on Mar 29, 2024

    @ZhenjaHorbach
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Web - Chat - Composer is expanded briefly when returning to chat after creating new workspace

    What is the root cause of that problem?

    Problem related with the fact that when we get isComposerFullSize from onyx it equals {}

    isComposerFullSize: {
    key: ({route}) => `${ONYXKEYS.COLLECTION.REPORT_IS_COMPOSER_FULL_SIZE}${getReportID(route)}`,
    initialValue: false,
    },

    And then we get true from {}

    isComposerFullSize={!!isComposerFullSize}

    What changes do you think we should make in order to solve the problem?

    So maybe the problem is related to onyx
    But as an alternative we can add a check for object using selector and return false in this case

    isComposerFullSize: {
    key: ({route}) => `${ONYXKEYS.COLLECTION.REPORT_IS_COMPOSER_FULL_SIZE}${getReportID(route)}`,
    initialValue: false,
    },

    What alternative solutions did you explore? (Optional)

    NA

  4. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 29, 2024
  5. thienlnam commented on Mar 29, 2024

    @thienlnam
    Contributor

    Not a blocker - added to the main tracking issue

  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Apr 5, 2024
  7. changed the title [-]Web - Chat - Composer is expanded briefly when returning to chat after creating new workspace[/-] [+][$250] Web - Chat - Composer is expanded briefly when returning to chat after creating new workspace[/+] on Apr 5, 2024
  8. melvin-bot commented on Apr 5, 2024

    @melvin-bot
  9. 19 remaining items

  10. melvin-bot commented on Apr 11, 2024

    @melvin-bot

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

  11. thienlnam commented on Apr 11, 2024

    @thienlnam
    Contributor

    So to double check, this is no longer reproducible?

  12. melvin-bot commented on Apr 12, 2024

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  13. melvin-bot commented on Apr 12, 2024

    @melvin-bot

    @mananjadhav @anmurali @thienlnam this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  14. anmurali commented on Apr 17, 2024

    @anmurali

    Yea, I cannot reproduce on staging or prod. Closing.

  15. added and removed
    ExternalAdded to denote the issue can be worked on by a contributor
    Help WantedApply this label when an issue is open to proposals by contributors
    on Apr 17, 2024
  16. MelvinBot commented on Apr 17, 2024

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

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.DailyKSv2EngineeringNeeds ReproductionReproducible steps needed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions