Fix incognito mode disabled after the app kicked out of memory (#5167)

The application class onCreate will also be called when user navigates to an
activity after the app process is killed by the system.

So make sure the incognito is disabled only when the entry point of the app is
created from scratch (e.g. after being force closed by the user).
This commit is contained in:
Ivan Iskandar 2021-05-24 20:09:35 +07:00 committed by GitHub
parent a462ce3626
commit 3c186a3c8d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions

View file

@ -74,9 +74,6 @@ open class App : Application(), LifecycleObserver, ImageLoaderFactory {
ProcessLifecycleOwner.get().lifecycle.addObserver(this) ProcessLifecycleOwner.get().lifecycle.addObserver(this)
// Reset Incognito Mode on relaunch
preferences.incognitoMode().set(false)
// Show notification to disable Incognito Mode when it's enabled // Show notification to disable Incognito Mode when it's enabled
preferences.incognitoMode().asFlow() preferences.incognitoMode().asFlow()
.onEach { enabled -> .onEach { enabled ->

View file

@ -224,6 +224,9 @@ class MainActivity : BaseViewBindingActivity<MainActivityBinding>() {
syncActivityViewWithController(router.backstack.lastOrNull()?.controller()) syncActivityViewWithController(router.backstack.lastOrNull()?.controller())
if (savedInstanceState == null) { if (savedInstanceState == null) {
// Reset Incognito Mode on relaunch
preferences.incognitoMode().set(false)
// Show changelog prompt on update // Show changelog prompt on update
if (Migrations.upgrade(preferences) && !BuildConfig.DEBUG) { if (Migrations.upgrade(preferences) && !BuildConfig.DEBUG) {
WhatsNewDialogController().showDialog(router) WhatsNewDialogController().showDialog(router)