Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fetching report history on reconnect is inefficient and causes issues for sign out #2615

Closed
marcaaron opened this issue Apr 28, 2021 · 0 comments · Fixed by #2616
Closed
Assignees

Comments

@marcaaron
Copy link
Contributor

marcaaron commented Apr 28, 2021

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Expected Result:

If we already have local report actions for a report we don't need to fetch them again.
If we log out quickly after logging in the app does not end up in a bad state.

Actual Result:

Even though we are up to date on a report's history we will still re-download the 50 most recent items on reconnect
If we log in and out quickly the app appears to get caught in some kind of infinite loop.

Actions Performed:

  1. Be me
  2. Have chat history already downloaded
  3. Go offline and back online
  4. See that we are fetching the history for all reports and returning up to 50 comments we already have for each

Screen Shot 2021-04-28 at 12 26 22 PM

  1. Sign in and sign out quickly
  2. See that the app tries to make API requests that it should not and gets caught in some sort of infinite loop.

Workaround:

This mostly leads to performance issues like slowdowns from having to re-download things we've already got.

Platform:

Where is this issue occurring?

Everywhere

Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:

View all open jobs on Upwork

@marcaaron marcaaron self-assigned this Apr 28, 2021
@marcaaron marcaaron changed the title Fetching report history on reconnect is inefficient Fetching report history on reconnect is inefficient and causes issues for sign out Apr 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant