[FIX] [New arch] Crash when removing account

[JuancaG05]

Related Issues

App: #3721

---

QA

[jesmrec]

Crash is fixed. But, every time one account is removed, the following trace is generated. Could it be "dangerous"?:

2022-08-08 14:07:01.516 16512-16512/com.owncloud.android.debug D/StrictMode: StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: Landroid/view/ViewGroup;->makeOptionalFitsSystemWindows()V
        at android.os.StrictMode.lambda$static$1(StrictMode.java:420)
        at android.os.StrictMode$$ExternalSyntheticLambda3.accept(Unknown Source:2)
        at java.lang.Class.getDeclaredMethodInternal(Native Method)
        at java.lang.Class.getPublicMethodRecursive(Class.java:2110)
        at java.lang.Class.getMethod(Class.java:2097)
        at java.lang.Class.getMethod(Class.java:1724)
        at androidx.appcompat.widget.ViewUtils.makeOptionalFitsSystemWindows(ViewUtils.java:84)
        at androidx.appcompat.app.AppCompatDelegateImpl.createSubDecor(AppCompatDelegateImpl.java:982)
        at androidx.appcompat.app.AppCompatDelegateImpl.ensureSubDecor(AppCompatDelegateImpl.java:815)
        at androidx.appcompat.app.AppCompatDelegateImpl.setContentView(AppCompatDelegateImpl.java:703)
        at androidx.appcompat.app.AppCompatDialog.setContentView(AppCompatDialog.java:95)
        at androidx.appcompat.app.AlertController.installContent(AlertController.java:232)
        at androidx.appcompat.app.AlertDialog.onCreate(AlertDialog.java:279)
        at android.app.Dialog.dispatchOnCreate(Dialog.java:432)
        at android.app.Dialog.show(Dialog.java:321)
        at androidx.fragment.app.DialogFragment.onStart(DialogFragment.java:710)
        at androidx.fragment.app.Fragment.performStart(Fragment.java:3053)
        at androidx.fragment.app.FragmentStateManager.start(FragmentStateManager.java:587)
        at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:279)
        at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1840)
        at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1764)
        at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1701)
        at androidx.fragment.app.FragmentManager$4.run(FragmentManager.java:488)
        at android.os.Handler.handleCallback(Handler.java:938)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loopOnce(Looper.java:201)
        at android.os.Looper.loop(Looper.java:288)
        at android.app.ActivityThread.main(ActivityThread.java:7870)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)

[JuancaG05]

@jesmrec I was researching a bit and seems that StrictMode is a debugging tool used to detect likely accidental accesses to disk or network, so in the same line as LeakCanary. For the moment it shouldn't suppose any problem. More info: https://developer.android.com/reference/kotlin/android/os/StrictMode

[jesmrec]

Let's move forward this, then