[HOLD for payment 2024-12-30] [$250] [Performance] Implement a debug setting that simulates a poor connection by going online/offline a bunch #51331
Description
What performance issue do we need to solve?
When on a poor connection, authentication calls can sometimes fail. This is sometimes de-authing users from the app (logging them out) when it shouldn't be, because we have infinite sessions.
What is the impact of this on end-users?
Users need to re-authenticate when this happens, and this is annoying.
List any benchmarks that show the severity of the issue
It has been reported numerous times in the #quality Slack channel.
Proposed solution (if any)
Implement a debug setting that simulates a poor connection, then see how much of the app breaks and try to fix those spots.
This could be done by setting up some code that will call NetworkActions.setNetWorkStatus(networkStatus); with a random value of CONST.NETWORK.NETWORK_STATUS at random intervals like every 2-5 seconds.
List any benchmarks after implementing the changes to show impacts of the proposed solution (if any)
It might be time to add some benchmarking for how often the network connection is changing. How about logging every hour how many times the network connection state changed?
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
Version Number:
Reproducible in staging?:
Reproducible in production?:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021864308224556700727
- Upwork Job ID: 1864308224556700727
- Last Price Increase: 2024-12-04
Issue Owner
Current Issue Owner: @hoangzinhMetadata
Metadata
Labels
Type
Projects
Status