Skip to content

Workspace - The Workspace editor page isn't open after creating the new workspace. #10605

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!


Action Performed:

  1. Create a new applause.expensifail account on staging.new.expensify.com
  2. Click on Create a New Workspace

Expected Result:

The Workspace editor page should be open after creating the new workspace.

Actual Result:

The Workspace editor page isn't open after creating the new workspace.

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number: 1.1.92.0

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers): any

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5705659_WS_new2.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Aug 26, 2022

    @melvin-bot

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

  2. melvin-bot commented on Aug 30, 2022

    @melvin-bot

    @cead22 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  3. removed their assignment
    on Aug 30, 2022
  4. melvin-bot commented on Aug 30, 2022

    @melvin-bot

    Triggered auto assignment to @jasperhuangg (Demolition), see https://stackoverflow.com/c/expensify/questions/8099 for more details.

  5. cead22 commented on Aug 30, 2022

    @cead22
    Contributor

    Labeling Demolition instead of External since this is something we should fix asap

  6. jasperhuangg commented on Aug 31, 2022

    @jasperhuangg
    Contributor

    Can confirm this is happening locally, taking a look

  7. jasperhuangg commented on Aug 31, 2022

    @jasperhuangg
    Contributor

    Found the problem, it's because of this incorrect usage of Promise.all that was added here cc @arosiclair

    Promise.all takes an iterable of promises, not the individual promises as arguments. Simply passing in the promises as an array fixes things. PR in the works.

  8. melvin-bot commented on Aug 31, 2022

    @melvin-bot

    ⚠️ Looks like this issue was linked to a possible regression on PRODUCTION 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here.

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions