Skip to content

Web - Page with error message(crashed) when selecting Settings button from room details  #7786

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. Open app and login with any applause account
  2. Tap on Fub menu - Select New Room
  3. Create a new room
  4. Select on name of the room to view the details
  5. Select the Settings

Expected Result:

Settings page should open

Actual Result:

Page crashes all the time

Workaround:

Unknow

Platform:

Where is this issue occurring?

  • Web

Version Number: 1.1.39.1

Reproducible in staging?: Yes

**Reproducible in production?:**Yes

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

Notes/Photos/Videos: Any additional supporting documentation

Recording.222.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause

Slack conversation:

View all open jobs on GitHub

Activity

  1. MelvinBot commented on Feb 16, 2022

    @MelvinBot
    Contributor

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

  2. parasharrajat commented on Feb 16, 2022

    @parasharrajat
    Member

    It could be due to my PR and please test it if this is fixed on #7782 then please add this issue to that PR as well.

  3. mvtglobally commented on Feb 17, 2022

    @mvtglobally

    @parasharrajat are you saying your fix is ready? What's the ticket ID? nevermind. Will wait for it to deploy and retest this

  4. parasharrajat commented on Feb 17, 2022

    @parasharrajat
    Member

    Yeah, that comment was for assignee.

  5. TomatoToaster commented on Feb 21, 2022

    @TomatoToaster
    Contributor

    I'm not able to recreate this on staging @mvtglobally are you able to still reproduce this?

    How many users are in the workspace where this error happens?

  6. TomatoToaster commented on Feb 23, 2022

    @TomatoToaster
    Contributor

    I still can't recreate this one so I think some other change might have fixed it? It doesn't seem to be linked to the undefined crash because this still works for me on staging. I'm going to close this but if it crops up again feel free to reoopen.

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