Steps to reproduce the bug
Its not reproducible always
- Open main page content editor
- Add a playlist tab
Expected behavior
No error should be left uncaught
Actual behaviour
An ui error occurred because it was not handled properly
Exception
- User Action: ui error
- Request:
- Content Country: IN
- Content Language: en-IN
- App Language: en_IN
- Service: none
- Version: 0.19.8
- OS: Linux Android 9 - 28
Crash log
android.view.ViewRootImpl$CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch its views.
at android.view.ViewRootImpl.checkThread(ViewRootImpl.java:7760)
at android.view.ViewRootImpl.requestLayout(ViewRootImpl.java:1225)
at android.view.View.requestLayout(View.java:23114)
at android.view.View.requestLayout(View.java:23114)
at android.view.View.requestLayout(View.java:23114)
at android.view.View.requestLayout(View.java:23114)
at android.view.View.requestLayout(View.java:23114)
at android.view.View.setFlags(View.java:14102)
at android.view.View.setVisibility(View.java:9992)
at org.schabi.newpipe.settings.SelectPlaylistFragment.displayPlaylists(SelectPlaylistFragment.java:143)
at org.schabi.newpipe.settings.SelectPlaylistFragment.lambda$OKidrRDkz4wytGdEytcZ56EPSTU(Unknown Source:0)
at org.schabi.newpipe.settings.-$$Lambda$SelectPlaylistFragment$OKidrRDkz4wytGdEytcZ56EPSTU.accept(Unknown Source:4)
at io.reactivex.internal.subscribers.LambdaSubscriber.onNext(LambdaSubscriber.java:65)
at io.reactivex.internal.operators.flowable.FlowableCombineLatest$CombineLatestCoordinator.drainAsync(FlowableCombineLatest.java:374)
at io.reactivex.internal.operators.flowable.FlowableCombineLatest$CombineLatestCoordinator.drain(FlowableCombineLatest.java:406)
at io.reactivex.internal.operators.flowable.FlowableCombineLatest$CombineLatestCoordinator.innerValue(FlowableCombineLatest.java:250)
at io.reactivex.internal.operators.flowable.FlowableCombineLatest$CombineLatestInnerSubscriber.onNext(FlowableCombineLatest.java:521)
at io.reactivex.internal.operators.flowable.FlowableSubscribeOn$SubscribeOnSubscriber.onNext(FlowableSubscribeOn.java:97)
at io.reactivex.internal.operators.flowable.FlowableFlatMapMaybe$FlatMapMaybeSubscriber.innerSuccess(FlowableFlatMapMaybe.java:175)
at io.reactivex.internal.operators.flowable.FlowableFlatMapMaybe$FlatMapMaybeSubscriber$InnerObserver.onSuccess(FlowableFlatMapMaybe.java:397)
at io.reactivex.internal.operators.maybe.MaybeFromCallable.subscribeActual(MaybeFromCallable.java:61)
at io.reactivex.Maybe.subscribe(Maybe.java:4290)
at io.reactivex.internal.operators.flowable.FlowableFlatMapMaybe$FlatMapMaybeSubscriber.onNext(FlowableFlatMapMaybe.java:132)
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.ExecutorScheduler$ExecutorWorker$BooleanRunnable.run(ExecutorScheduler.java:288)
at io.reactivex.internal.schedulers.ExecutorScheduler$ExecutorWorker.run(ExecutorScheduler.java:253)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
Steps to reproduce the bug
Its not reproducible always
Expected behavior
No error should be left uncaught
Actual behaviour
An ui error occurred because it was not handled properly
Exception
Crash log