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
{{ message }}
This repository has been archived by the owner on Mar 16, 2021. It is now read-only.
The main issue is when update and migrate your data from one app version to next one with versioned Preferences and a onUpgrade() method - onUpgrade took more than 5 seconds and the foreground service crashes since startForeground() not reached within the 5 seconds.
The text was updated successfully, but these errors were encountered:
Duna
changed the title
ANR that leads to app crashing
ANR that leads to app crashing, support needed
Sep 27, 2020
Is it ok to initialize Tray on separate thread(when onUpdate is called)?
What happens if I read/write data on main thread, and the initialization(onUpdate) not reaches the end, done on the separate thread, different than main looper.
Is it a way to avoid ouUpdate when having new release of the app on the market?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
See attached picture, is self explanatory
The main issue is when update and migrate your data from one app version to next one with versioned Preferences and a onUpgrade() method - onUpgrade took more than 5 seconds and the foreground service crashes since startForeground() not reached within the 5 seconds.
The text was updated successfully, but these errors were encountered: