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

BUG - sev-3 - Android - ~10 seconds of non-responsiveness at app startup (sometimes) #9557

Open
5 tasks
TKDickson opened this issue Sep 9, 2024 · 2 comments
Open
5 tasks
Assignees
Labels
bug Used to identify a bug ticket that will be worked through the bug process front-end Ticket requires front-end work global Issues for the global team QA Tickets require QA work / review scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this

Comments

@TKDickson
Copy link
Contributor

TKDickson commented Sep 9, 2024

What happened?

If I force-quit the app (after having logged in), then open it again, there's a good ~10 seconds where an empty black screen displays, rather than the sync screen (or any other intentional app screen).

I'm not sure what's going on during this time (us? platform/device stuff? calling firebase? etc) so I'm guessing there's a non-zero chance that delays could be even longer for veterans in production. We do have user reports of a completely non-responsive app, maybe this is what they're talking about. Example:

I downloaded this app and it will not load up so that I can even log into it. I deleted it within 15 minutes due to non-operation

Specs:

  • Device:
  • OS:
  • User Account:
  • Accessibility State:

Steps to Reproduce

Desired behavior

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking for details on severity levels

  • Impact: High Low
  • Frequency: High Low
  • 3 - Low
  • 2 - High
  • 1 - Critical

Linked to Story

Screen shot(s) and additional information

-Binny Note: Confirm how early in this video our code actually begins executing.

Full JSON response for services related to issue (expand/collapse)

Ticket Checklist

  • Steps to reproduce are defined
  • Desired behavior is added
  • Labels added (front-end, back-end, global, Health, relevant feature, accessibility, etc)
  • Estimate of 1 added (for front-end tickets)
  • Added either to the relevant feature epic (if found during new feature implementation), or the relevant team's bug epic (Global, Health & Benefits, API, QART)
@TKDickson TKDickson added bug Used to identify a bug ticket that will be worked through the bug process front-end Ticket requires front-end work global Issues for the global team QA Tickets require QA work / review sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this labels Sep 9, 2024
@dumathane
Copy link
Contributor

Confirm how early in this video our code actually begins executing.

@TKDickson TKDickson added the scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness label Sep 19, 2024
@jennb33
Copy link

jennb33 commented Dec 11, 2024

12/11/2024 - @kellylein @timwright12 @oddballpete @Eallan919 @ATeal @TKDickson The MFS team will be taking this ticket into Sprint 7, (12/14/2024-12/27/2024)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Used to identify a bug ticket that will be worked through the bug process front-end Ticket requires front-end work global Issues for the global team QA Tickets require QA work / review scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this
Projects
None yet
Development

No branches or pull requests

4 participants