java.lang.IllegalArgumentException: Receiver not registered: com.polidea.rxandroidble2.internal.util.LocationServicesOkObservableApi23
See original GitHub issueSummary
Android: 6.0
Manufacturer: HTC
Model: HTC One_M8
java.lang.IllegalArgumentException: Receiver not registered: com.polidea.rxandroidble2.internal.util.LocationServicesOkObservableApi23$1@2defaaf
at android.app.LoadedApk.forgetReceiverDispatcher(LoadedApk.java:793)
at android.app.ContextImpl.unregisterReceiver(ContextImpl.java:1203)
at android.content.ContextWrapper.unregisterReceiver(ContextWrapper.java:576)
at com.polidea.rxandroidble2.internal.util.LocationServicesOkObservableApi23$2.run(LocationServicesOkObservableApi23.java:49)
at io.reactivex.disposables.ActionDisposable.onDisposed(ActionDisposable.java:30)
at io.reactivex.disposables.ActionDisposable.onDisposed(ActionDisposable.java:19)
at io.reactivex.disposables.ReferenceDisposable.dispose(ReferenceDisposable.java:43)
at io.reactivex.internal.observers.BasicFuseableObserver.dispose(BasicFuseableObserver.java:152)
at io.reactivex.internal.disposables.DisposableHelper.setOnce(DisposableHelper.java:81)
at io.reactivex.internal.operators.observable.ObservableSwitchMap$SwitchMapInnerObserver.onSubscribe(ObservableSwitchMap.java:346)
at io.reactivex.internal.observers.BasicFuseableObserver.onSubscribe(BasicFuseableObserver.java:66)
at com.polidea.rxandroidble2.internal.util.LocationServicesOkObservableApi23.subscribeActual(LocationServicesOkObservableApi23.java:46)
at io.reactivex.Observable.subscribe(Observable.java:12025)
at io.reactivex.internal.operators.observable.ObservableMap.subscribeActual(ObservableMap.java:33)
at io.reactivex.Observable.subscribe(Observable.java:12025)
at io.reactivex.internal.operators.observable.ObservableSwitchMap$SwitchMapObserver.onNext(ObservableSwitchMap.java:127)
at io.reactivex.internal.operators.observable.ObservableConcatMap$ConcatMapDelayErrorObserver.drain(ObservableConcatMap.java:464)
at io.reactivex.internal.operators.observable.ObservableConcatMap$ConcatMapDelayErrorObserver.onSubscribe(ObservableConcatMap.java:324)
at io.reactivex.internal.operators.observable.ObservableFromArray.subscribeActual(ObservableFromArray.java:30)
at io.reactivex.Observable.subscribe(Observable.java:12025)
at io.reactivex.internal.operators.observable.ObservableConcatMap.subscribeActual(ObservableConcatMap.java:54)
at io.reactivex.Observable.subscribe(Observable.java:12025)
at io.reactivex.internal.operators.observable.ObservableSwitchMap.subscribeActual(ObservableSwitchMap.java:51)
at io.reactivex.Observable.subscribe(Observable.java:12025)
at io.reactivex.internal.operators.observable.ObservableSkip.subscribeActual(ObservableSkip.java:29)
at io.reactivex.Observable.subscribe(Observable.java:12025)
at io.reactivex.internal.operators.observable.ObservableFlatMap$MergeObserver.subscribeInner(ObservableFlatMap.java:165)
at io.reactivex.internal.operators.observable.ObservableFlatMap$MergeObserver.onNext(ObservableFlatMap.java:139)
at io.reactivex.internal.observers.DeferredScalarDisposable.complete(DeferredScalarDisposable.java:82)
at io.reactivex.internal.operators.single.SingleToObservable$SingleToObservableObserver.onSuccess(SingleToObservable.java:73)
at io.reactivex.internal.operators.single.SingleMap$MapSingleObserver.onSuccess(SingleMap.java:64)
at io.reactivex.internal.operators.observable.ObservableCountSingle$CountObserver.onComplete(ObservableCountSingle.java:83)
at io.reactivex.internal.operators.observable.ObservableTakeWhile$TakeWhileObserver.onNext(ObservableTakeWhile.java:86)
at io.reactivex.internal.operators.observable.ObservableInterval$IntervalObserver.run(ObservableInterval.java:83)
at io.reactivex.internal.schedulers.ScheduledDirectPeriodicTask.run(ScheduledDirectPeriodicTask.java:38)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:423)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:278)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:154)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:270)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Library version
1.6.0-SNAPSHOT
Actual result
It threw IllegalArgumentException
and thus crashed the app.
Expected result
It should not throw IllegalArgumentException
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
java.lang.IllegalArgumentException: Receiver not ... - GitHub
java.lang.IllegalArgumentException: Receiver not registered: com.polidea.rxandroidble2.internal.util.LocationServicesOkObservableApi23 #436.
Read more >java.lang.IllegalArgumentException: Receiver not registered
The data is being retrieved to the the map activity but I am facing problem to unregister my bReceiver . I want to...
Read more >'java.lang.IllegalArgumentException: Receiver not registered ...
This is a client bug, so I'm moving it into the appropriate product/component. Krupa: does the app still appear to install and run...
Read more >java.lang.IllegalArgumentException: Receiver not registered
Android : java. lang. IllegalArgumentException : Receiver not registered [ Beautify Your Computer : https://www.hows.tech/p/recommended.html ] ...
Read more >java.lang.IllegalArgumentException: Receiver not registered ...
This seems like a very critical issue as it brakes the apps that are out there. We're getting this exception from a LOT...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s @dariuszseweryn 😉 Hmmm… Apparently (if it is a clean build with no caches) then it is possible to determine from the timestamp. Anyway I have just released
1.6.0
so there will be no more confusion about1.6.0-SNAPSHOT
😉 Closing in this situationAdditionally when from this
1.6.0-SNAPSHOT
version was? 4 days ago we have fixed a similar crash in commit d3197ebf15044d8369763c385bea982253fcb0ffThe code that is using this observable can also be useful if this has something to do with threading.