i’ve updated my Teracube 2e to 1.1-r yesterday. Everything but the mail app seems to work fine.
Mail immediately crashes when i try to open it. I’ve cleaned the cache, but the crashes still persist.
I have not cleaned the app storage till now cause i’m hesitant to go through the setup of my mail accounts again.
Can’t confirm on 1.0-q-20220622198553-dev-FP3, but this is not the latest version for Q dev anyway, 1.1 is out already for this channel.
This is missing detail. What exactly does it say in Settings - About phone - Android version (tap on it) - /e/ OS version (can be long-tapped and copied to clipboard since Android 10 Q)?
Hello, I’m using, /e/ on the FP2, since 1.1 the Mail app is crashing very often, and since this morning it’s crashing every time so I can’t open it anymore. I just upgraded to 1.2 but that doesn’t change anything. I would like to solve that crash without clearing the data, as I’m sure other users may be impacted. Please tell me how to find useful logs, thank you!
I’m not saying clearing my cache / data would impact other users, I’m saying I’m not the only user impacted by the bug, so it should be fixed for everyone, not by asking manual actions to the users.
I don’t think deleting data (mail email accounts!) is a good solution. Mail crashes constantly after updating to 1.2. If any devs happen to look in, here’s a logcat of the crash:
--------- beginning of crash
08-12 10:33:37.091 3679 3679 E AndroidRuntime: FATAL EXCEPTION: main
08-12 10:33:37.091 3679 3679 E AndroidRuntime: Process: foundation.e.mail, PID: 3679
08-12 10:33:37.091 3679 3679 E AndroidRuntime: java.lang.RuntimeException: Unable to resume activity {foundation.e.mail/com.fsck.k9.activity.MessageList}: kotlin.UninitializedPropertyAccessException: lateinit property actionBar has not been initialized
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4438)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4470)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.ClientTransactionHandler.executeTransaction(ClientTransactionHandler.java:58)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.ActivityThread.handleRelaunchActivityLocally(ActivityThread.java:5414)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.ActivityThread.access$3300(ActivityThread.java:237)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2076)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7664)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: Caused by: kotlin.UninitializedPropertyAccessException: lateinit property actionBar has not been initialized
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at com.fsck.k9.activity.MessageList.setActionBarTitle(MessageList.kt:1253)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at com.fsck.k9.activity.MessageList.setMessageListTitle(MessageList.kt:1259)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at com.fsck.k9.fragment.MessageListFragment.setWindowTitle(MessageListFragment.kt:384)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at com.fsck.k9.fragment.MessageListFragment.updateTitle(MessageListFragment.kt:339)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at com.fsck.k9.fragment.MessageListFragment.onResume(MessageListFragment.kt:515)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.fragment.app.Fragment.performResume(Fragment.java:3071)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.fragment.app.FragmentStateManager.resume(FragmentStateManager.java:605)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:285)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.fragment.app.FragmentStore.moveToExpectedState(FragmentStore.java:113)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1374)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:2841)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.fragment.app.FragmentManager.dispatchResume(FragmentManager.java:2798)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.fragment.app.FragmentController.dispatchResume(FragmentController.java:284)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.fragment.app.FragmentActivity.onResumeFragments(FragmentActivity.java:434)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.fragment.app.FragmentActivity.onPostResume(FragmentActivity.java:423)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at androidx.appcompat.app.AppCompatActivity.onPostResume(AppCompatActivity.java:240)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.Activity.performResume(Activity.java:8154)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4428)
08-12 10:33:37.091 3679 3679 E AndroidRuntime: … 14 more
There’s no need for that tone. Clearing cache DOESN’T work as others have said! Clearing app data is marked as the solution which is NOT a good solution. The underlying bug “lateinit property actionBar has not been initialized” needs to be fixed as this will only happen again
The looks to me as though the problem is in the upstream app K-9 Mail, from which /e/'s Mail app is forked. If that’s the case, it will need to be fixed in the upstream app too. I am sure the upstream deveioper would be happy to receive a patch from the /e/ devs to fix the problem