You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
### 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
- Fixescelo-org/celo-monorepo#6542
### Backwards compatibility
Yes
Sentry Issue: CELO-MOBILE-3AP
The text was updated successfully, but these errors were encountered: