Skip to content

VBA - Continuous loading spinner appears after company information page #6620

Closed

Description

@kavimuru

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. Launch the app and login
  2. Go to any Workspace and tap on connect Bank account
  3. Use Plaid or connect manually
  4. Continue the flow up to company info page and click next

Expected Result:

User is taken to the next page

Actual Result:

Loading spinner appears for ever

Workaround:

Unknown

Platform:

Where is this issue occurring?

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

Version Number: 1.1.18.0

Reproducible in staging?: Yes

Reproducible in production?: Unable to check in production with staging credentials

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

Notes/Photos/Videos:

Bug5362537_Screen_Recording_20211206-230247_New_Expensify__2_.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause

Slack conversation:

View all open jobs on GitHub

Activity

  1. changed the title [-]VBA - Continuous loading spinner appears after company information added[/-] [+]VBA - Continuous loading spinner appears after company information page[/+] on Dec 7, 2021
  2. OSBotify commented on Dec 7, 2021

    @OSBotify
    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. MelvinBot commented on Dec 7, 2021

    @MelvinBot
    Contributor

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

  4. roryabraham commented on Dec 7, 2021

    @roryabraham
    Contributor

    @stitesExpensify is not fully online this week, I'm going to lend a hand and grab this one.

  5. marcaaron commented on Dec 7, 2021

    @marcaaron
    Contributor

    Investigating this as well. I thought maybe this PR could be causing this -> #6230

    But reverted it and the issue persists. Also went back to that commit and verified that everything works so gonna try to git bisect.

  6. marcaaron commented on Dec 7, 2021

    @marcaaron
    Contributor

    First bad commit is here 68e5ce6

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