-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
PlayStore test failing for custom app (Tunisie) #3638
Comments
@gouri-panda, @kelson42 I have tried to reproduce the error with many scenarios in the same configuration of the emulator which is provided by the pre-launched report. Unfortunately, I am not able to reproduce this error on my local machine. The logs provided by the pre-launched report are related to the getEntryByPath and getItem methods, these methods are already in the try-catch block so the crash is occurring inside the lib, and we can not handle this in Android since these methods are already inside the try-catch block. I saw this report is generated by the Firebase Test lab. so I have tested our APK with the Firebase test lab. However, I have not seen this crash in the Firebase test lab report, so it probably hardly occurs. Might be @mgautierfr can better understand the error by the provided logs. Apart from this, the Firebase test lab report provides a bug report in our application. This is a genuine error, our application is crashing below Api level 29, when we switch to external storage and it has less storage in it. Error reported by the Firebase Test Lab report Logs Process: org.kiwix.kiwixmobile, PID: 15852
io.reactivex.exceptions.UndeliverableException: The exception could not be delivered to the consumer because it has already canceled/disposed the flow or the exception has nowhere to go to begin with. Further reading: https://github.com/ReactiveX/RxJava/wiki/What's-different-in-2.0#error-handling | java.lang.NoSuchMethodError: No direct method <init>(Ljava/io/File;I)V in class Landroid/os/FileObserver; or its super classes (declaration of 'android.os.FileObserver' appears in /system/framework/framework.jar)
at io.reactivex.plugins.RxJavaPlugins.onError(RxJavaPlugins.java:367)
at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:69)
at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:57)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:272)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
Caused by: java.lang.NoSuchMethodError: No direct method <init>(Ljava/io/File;I)V in class Landroid/os/FileObserver; or its super classes (declaration of 'android.os.FileObserver' appears in /system/framework/framework.jar)
at org.kiwix.kiwixmobile.zimManager.Fat32Checker$fileObserver$1.<init>(Fat32Checker.kt:66)
at org.kiwix.kiwixmobile.zimManager.Fat32Checker.fileObserver(Fat32Checker.kt:66)
at org.kiwix.kiwixmobile.zimManager.Fat32Checker._init_$lambda-2(Fat32Checker.kt:59)
at org.kiwix.kiwixmobile.zimManager.Fat32Checker.$r8$lambda$qFAKoPi7GWGXdtHXd4q0qCUOpJg(Fat32Checker.kt)
at org.kiwix.kiwixmobile.zimManager.Fat32Checker$$ExternalSyntheticLambda2.accept(D8$$SyntheticClass)
at io.reactivex.internal.subscribers.LambdaSubscriber.onNext(LambdaSubscriber.java:65)
at io.reactivex.internal.operators.flowable.FlowableSubscribeOn$SubscribeOnSubscriber.onNext(FlowableSubscribeOn.java:97)
at io.reactivex.internal.operators.flowable.FlowableObserveOn$ObserveOnSubscriber.runAsync(FlowableObserveOn.java:407)
at io.reactivex.internal.operators.flowable.FlowableObserveOn$BaseObserveOnSubscriber.run(FlowableObserveOn.java:176)
at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:66) |
@MohitMaliFtechiz Thank you for the analysis. I guess without the devug symbols of libkiwix it will be difficult to do more. |
I guess here there is nothing much more we can do. Closing. |
Logs provided by google
Video of crash provided by Google
video.mp4
Second crash logs
Device specifications
The text was updated successfully, but these errors were encountered: