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-2 - Android - libc.so crash #3013

Closed
2 tasks
narin opened this issue Apr 22, 2022 · 3 comments
Closed
2 tasks

BUG - Sev-2 - Android - libc.so crash #3013

narin opened this issue Apr 22, 2022 · 3 comments
Assignees
Labels
bug Used to identify a bug ticket that will be worked through the bug process Closed - Deployed/Fixed eng Ticket requires engineering work, other labels for specific backend or frontend front-end Ticket requires front-end work sev-2 Mid-tier bug severity level based on QA bug severity scale - QA to assign this

Comments

@narin
Copy link
Contributor

narin commented Apr 22, 2022

What happened?

There is an obscure bug on Android (mostly Samsung) devices that has existed for quite some time and is causing the app to crash for many users early on when launching the app.

In the past 30 days, it has affected 282 users over 300 times. Crashlytics Link

The logs do not tell us much, but some solutions either seem to suggest it is related to firebase RN packages, or an incorrect Hermes version. See this potentially related GH issue: facebook/react-native#25494.

Specs:

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

Steps to Reproduce

Unknown

Desired behavior

Acceptance Criteria

  • Investigate potential causes/solutions to this issue and document in this ticket
  • If any potential fixes are to be performed, please comment and track them in this ticket

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Issue Tracking for details on Severity Levels

  • 2 - High
@narin narin added sev-2 Mid-tier bug severity level based on QA bug severity scale - QA to assign this bug Used to identify a bug ticket that will be worked through the bug process labels Apr 22, 2022
@b-rocha b-rocha added front-end Ticket requires front-end work eng Ticket requires engineering work, other labels for specific backend or frontend labels Apr 27, 2022
@narin
Copy link
Contributor Author

narin commented May 9, 2022

@rarroyo23 is looking into adding symbols to the project in order to get a better stacktrace on this to help us better pinpoint the issue.

@b-rocha b-rocha added the slated for next sprint Use Next Sprint column instead of this label May 9, 2022
@jmarchi jmarchi self-assigned this May 18, 2022
@narin narin added the blocked-UX Issues blocked by UX/ design dependencies label May 24, 2022
@narin
Copy link
Contributor Author

narin commented May 24, 2022

To quote @jmarchi in this Slack thread: "It looks like it’s related to the way certain android phones handle react navigations animations onto a view with a webview on it. All of the logs I went through were at the webview login and only had the login start event logged, so this tracks with the users hitting login and the app crashing. The easiest way to confirm this is to disable the animation transitioning to the login webview screen for android devices and see if we stop seeing the crash. iOS would be unaffected."

UX has given us the okay with us disabling the animation to test this theory.

@narin narin removed the blocked-UX Issues blocked by UX/ design dependencies label May 24, 2022
@TKDickson TKDickson self-assigned this May 26, 2022
@TKDickson
Copy link
Contributor

On my Android devices (Nord n100, Galaxy Tab s7, Samsung Galaxy S9) going back and forth between the native app and login for webview worked just fine - animation is gone, workflow works - with the variations I used (device vs in-app navigation, initial and subsequent login, waiting for webview to fully load vs not).

@narin narin removed the slated for next sprint Use Next Sprint column instead of this label Aug 1, 2022
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 Closed - Deployed/Fixed eng Ticket requires engineering work, other labels for specific backend or frontend front-end Ticket requires front-end work sev-2 Mid-tier bug severity level based on QA bug severity scale - QA to assign this
Projects
None yet
Development

No branches or pull requests

4 participants