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

ApplicationNotResponding: Application Not Responding for at least 5000 ms. #6542

Closed
sentry-io bot opened this issue Jan 20, 2021 · 2 comments · Fixed by valora-inc/wallet#48
Closed
Labels

Comments

@sentry-io
Copy link

sentry-io bot commented Jan 20, 2021

Sentry Issue: CELO-MOBILE-3AP

ApplicationNotResponding: Application Not Responding for at least 5000 ms.
    at java.lang.Object.wait(Object.java)
    at java.lang.Object.wait(Object.java:422)
    at com.th3rdwave.safeareacontext.g.d
    at com.th3rdwave.safeareacontext.g.c
    at com.th3rdwave.safeareacontext.g.b
...
(34 additional frame(s) were not displayed)
@etuleu etuleu added the wallet label Jan 20, 2021
@isabellewei
Copy link
Contributor

Hypothesis that this should be fixed by #6284

@etuleu
Copy link
Contributor

etuleu commented Feb 11, 2021

ANR reported by a twitter user
https://twitter.com/thetimtalksalot/status/1359595492317876224

This looks to happen right after app start. Notice that the app did actually load (at least partially) because the background renders the screen. So maybe something like a deadlock happens right after, or takes more than 5 seconds to process.

mergify bot pushed a commit to valora-inc/wallet that referenced this issue Mar 1, 2021
### Description

Still doing more testing with the flags but I believe we should use priority normal for android push notifications so our app does not get woken up in the background, which can cause other unintended consequences.

Looking at the ANR traces in sentry I think most of them happen while the app is in the background. The only way our app gets woken up in background is via high priority push notifications. Since devices are in low latency network mode whatever we attempt to send or connect to might fail. We do not actually need to do any processing in background at this point so I think it is better to not wake up the device at all. The system takes care of displaying the notification as usual and the app process gets created when the notification is tapped.

### Other changes

None

### Tested

curl firebase
https://celo-org.slack.com/archives/CL7BVQPHB/p1606917022075000

### Related issues

- Fixes celo-org/celo-monorepo#6542

### Backwards compatibility

Yes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants