Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wikimed crashes on Samsung galaxy A12 with an Android version 12 #3902

Closed
Popolechien opened this issue Jun 21, 2024 · 3 comments · Fixed by #3904
Closed

Wikimed crashes on Samsung galaxy A12 with an Android version 12 #3902

Popolechien opened this issue Jun 21, 2024 · 3 comments · Fixed by #3904
Assignees
Labels
Milestone

Comments

@Popolechien
Copy link
Member

Here is the feedback sent by our user:

When ever I try to open the app it tells me to share this;
Someone has reported a crash
Hi Kiwix Developers!
The Android app crashed, here are some details to help fix it:

  Exception Details:
java.lang.RuntimeException: Parcelable encountered IOException writing serializable object (name = kotlinx.coroutines.CoroutinesInternalError)
at android.os.Parcel.writeSerializable(Parcel.java:2178)
at android.os.Parcel.writeValue(Parcel.java:1944)
at android.os.Parcel.writeArrayMapInternal(Parcel.java:1036)
at android.os.BaseBundle.writeToParcelInner(BaseBundle.java:1620)
at android.os.Bundle.writeToParcel(Bundle.java:1304)
at android.os.Parcel.writeBundle(Parcel.java:1105)
at android.content.Intent.writeToParcel(Intent.java:11771)
at android.app.IActivityTaskManager$Stub$Proxy.startActivity(IActivityTaskManager.java:2867)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1743)
at android.app.ContextImpl.startActivity(ContextImpl.java:1135)
at android.app.ContextImpl.startActivity(ContextImpl.java:1106)
at android.content.ContextWrapper.startActivity(ContextWrapper.java:420)
at org.kiwix.kiwixmobile.core.main.CoreMainActivity$$ExternalSyntheticLambda0.uncaughtException(R8$$SyntheticClass:35)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1071)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1066)
at kotlinx.coroutines.CoroutineExceptionHandlerImplKt.handleCoroutineExceptionImpl(CoroutineExceptionHandlerImpl.kt:73)
at kotlinx.coroutines.CoroutineExceptionHandlerKt.handleCoroutineException(CoroutineExceptionHandler.kt:15)
at kotlinx.coroutines.DispatchedTask.handleFatalException(DispatchedTask.kt:51)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:170)
at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:13)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:3)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:79)
Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: Em
@MohitMaliFtechiz
Copy link
Collaborator

@Popolechien This is the full report or do you have more logs?

When ever I try to open the app it tells me to share this;

The problem is occurring inside the coroutines and throwing the parcelable exception, it is a another issue(I will place a fix for it in a ticket) The logs are not showing the proper error due to this parcelable exception. I confirm this is an issue in if the coroutine throws an error it will not show the actual error instead of it will show the parcelable exception as shown in the below image where I explicitly thow error in the corutine to test this issue.

Screenshot from 2024-06-26 19-07-47

Apart from this, the behavior as the user describes that at the launch he is facing this issue. It seems it is related to #3899. Since in the new version of Wikimed app, we are migrating the history and notes in the room database at the start of the application within the coroutine and it probably throwing the error there.

@kelson42 This issue is related to kiwix android can you please move this issue to kiwix-android repo.

@Popolechien
Copy link
Member Author

Popolechien commented Jun 26, 2024

@MohitMaliDeveloper This is the full report that they shared with me. It would be strange that they only shared part of it so I'd take it as the full stuff

@kelson42
Copy link
Collaborator

@Popolechien Its really important that users which want a fix open the issue themself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment