java.lang.AssertionError

Error(s) present: [java.lang.IllegalStateException: onSubscribe not called in proper order] (latch = 1, values = 51, errors = 1, completions = 0)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web5312

  • via GitHub by vanniktech
    , 10 months ago
    Error(s) present: [java.lang.IllegalStateException: onSubscribe not called in proper order] (latch = 1, values = 51, errors = 1, completions = 0)
  • Subscriber still running! Error(s) present: [java.lang.IllegalStateException: onSubscribe not called in proper order]
  • No errors (latch = 1, values = 0, errors = 0, completions = 0)
  • Stack trace

    • java.lang.AssertionError: Error(s) present: [java.lang.IllegalStateException: onSubscribe not called in proper order] (latch = 1, values = 51, errors = 1, completions = 0) at io.reactivex.observers.TestObserver.fail(TestObserver.java:363) at io.reactivex.observers.TestObserver.assertNoErrors(TestObserver.java:411) at io.reactivex.internal.operators.observable.ObservableRefCountTest.testRepeat(ObservableRefCountTest.java:195)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.