Newpipe: [Soundcloud] "Could not parse json response"

Created on 31 Dec 2019  路  8Comments  路  Source: TeamNewPipe/NewPipe

There is currently, with NewPipe 0.18.0, the "Could not parse json response" exception when:

ASAP bug soundcloud

Most helpful comment

I'm having this issue on all of my phones to, with version 0.19.5. Whats odd is that on some of my frieds phones it works flawlesly.

Fresh installation did not change anything, and the behavior is there on the fdroid/github version.

All 8 comments

Exception

Crash log

org.schabi.newpipe.extractor.exceptions.ParsingException: Could not parse json response
    at org.schabi.newpipe.extractor.services.soundcloud.SoundcloudParsingHelper.resolveFor(SoundcloudParsingHelper.java:118)
    at org.schabi.newpipe.extractor.services.soundcloud.SoundcloudStreamExtractor.onFetchPage(SoundcloudStreamExtractor.java:33)
    at org.schabi.newpipe.extractor.Extractor.fetchPage(Extractor.java:54)
    at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:64)
    at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:60)
    at org.schabi.newpipe.util.ExtractorHelper.lambda$getStreamInfo$3(ExtractorHelper.java:115)
    at org.schabi.newpipe.util.-$$Lambda$ExtractorHelper$5fJcha6Sq5APJBLdG6osaJby-mc.call(Unknown Source:4)
    at io.reactivex.internal.operators.single.SingleFromCallable.subscribeActual(SingleFromCallable.java:44)
    at io.reactivex.Single.subscribe(Single.java:3438)
    at io.reactivex.internal.operators.single.SingleDoOnSuccess.subscribeActual(SingleDoOnSuccess.java:35)
    at io.reactivex.Single.subscribe(Single.java:3438)
    at io.reactivex.internal.operators.maybe.MaybeFromSingle.subscribeActual(MaybeFromSingle.java:41)
    at io.reactivex.Maybe.subscribe(Maybe.java:4154)
    at io.reactivex.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.drain(MaybeConcatArray.java:153)
    at io.reactivex.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.request(MaybeConcatArray.java:78)
    at io.reactivex.internal.operators.flowable.FlowableElementAtMaybe$ElementAtSubscriber.onSubscribe(FlowableElementAtMaybe.java:66)
    at io.reactivex.internal.operators.maybe.MaybeConcatArray.subscribeActual(MaybeConcatArray.java:42)
    at io.reactivex.Flowable.subscribe(Flowable.java:14479)
    at io.reactivex.internal.operators.flowable.FlowableElementAtMaybe.subscribeActual(FlowableElementAtMaybe.java:36)
    at io.reactivex.Maybe.subscribe(Maybe.java:4154)
    at io.reactivex.internal.operators.maybe.MaybeToSingle.subscribeActual(MaybeToSingle.java:46)
    at io.reactivex.Single.subscribe(Single.java:3438)
    at io.reactivex.internal.operators.single.SingleSubscribeOn$SubscribeOnObserver.run(SingleSubscribeOn.java:89)
    at io.reactivex.Scheduler$DisposeTask.run(Scheduler.java:578)
    at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:66)
    at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:57)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
    at java.lang.Thread.run(Thread.java:764)
Caused by: com.grack.nanojson.JsonParserException: Expected JSON value, got EOF on line 1, char 0
    at com.grack.nanojson.JsonParser.createParseException(Unknown Source:44)
    at com.grack.nanojson.JsonParser.currentValue(Unknown Source:30)
    at com.grack.nanojson.JsonParser.parse(Unknown Source:3)
    at com.grack.nanojson.JsonParser$JsonParserContext.from(Unknown Source:15)
    at org.schabi.newpipe.extractor.services.soundcloud.SoundcloudParsingHelper.resolveFor(SoundcloudParsingHelper.java:116)
    ... 30 more



Exception

  • __User Action:__ get suggestions
  • __Request:__ neonlight 10
  • __Content Language:__ FR
  • __Service:__ SoundCloud
  • __Version:__ 0.18.0
  • __OS:__ Linux samsung/heroltexx/herolte:8.0.0/R16NW/G930FXXU4ESB4:user/release-keys 8.0.0 - 26

Crash log

org.schabi.newpipe.extractor.exceptions.ParsingException: Could not parse json response
    at org.schabi.newpipe.extractor.services.soundcloud.SoundcloudSuggestionExtractor.suggestionList(SoundcloudSuggestionExtractor.java:47)
    at org.schabi.newpipe.util.ExtractorHelper.lambda$suggestionsFor$2(ExtractorHelper.java:105)
    at org.schabi.newpipe.util.-$$Lambda$ExtractorHelper$kAwiU5Tjeit-NCwHTWhD3V6UHS8.call(Unknown Source:4)
    at io.reactivex.internal.operators.single.SingleFromCallable.subscribeActual(SingleFromCallable.java:44)
    at io.reactivex.Single.subscribe(Single.java:3438)
    at io.reactivex.internal.operators.single.SingleToObservable.subscribeActual(SingleToObservable.java:35)
    at io.reactivex.Observable.subscribe(Observable.java:12090)
    at io.reactivex.internal.operators.observable.ObservableMap.subscribeActual(ObservableMap.java:32)
    at io.reactivex.Observable.subscribe(Observable.java:12090)
    at io.reactivex.internal.operators.observable.ObservableZip$ZipCoordinator.subscribe(ObservableZip.java:110)
    at io.reactivex.internal.operators.observable.ObservableZip.subscribeActual(ObservableZip.java:72)
    at io.reactivex.Observable.subscribe(Observable.java:12090)
    at io.reactivex.internal.operators.observable.ObservableMaterialize.subscribeActual(ObservableMaterialize.java:28)
    at io.reactivex.Observable.subscribe(Observable.java:12090)
    at io.reactivex.internal.operators.observable.ObservableSwitchMap$SwitchMapObserver.onNext(ObservableSwitchMap.java:127)
    at io.reactivex.internal.operators.observable.ObservableFilter$FilterObserver.onNext(ObservableFilter.java:52)
    at io.reactivex.internal.operators.observable.ObservableConcatMap$ConcatMapDelayErrorObserver$DelayErrorInnerObserver.onNext(ObservableConcatMap.java:506)
    at io.reactivex.observers.SerializedObserver.onNext(SerializedObserver.java:111)
    at io.reactivex.internal.operators.observable.ObservableDebounceTimed$DebounceTimedObserver.emit(ObservableDebounceTimed.java:143)
    at io.reactivex.internal.operators.observable.ObservableDebounceTimed$DebounceEmitter.run(ObservableDebounceTimed.java:168)
    at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:66)
    at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:57)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
    at java.lang.Thread.run(Thread.java:764)
Caused by: com.grack.nanojson.JsonParserException: Expected JSON value, got EOF on line 1, char 0
    at com.grack.nanojson.JsonParser.createParseException(Unknown Source:44)
    at com.grack.nanojson.JsonParser.currentValue(Unknown Source:30)
    at com.grack.nanojson.JsonParser.parse(Unknown Source:3)
    at com.grack.nanojson.JsonParser$JsonParserContext.from(Unknown Source:15)
    at org.schabi.newpipe.extractor.services.soundcloud.SoundcloudSuggestionExtractor.suggestionList(SoundcloudSuggestionExtractor.java:40)
    ... 26 more

I can't reproduce the issue since I reinstall the app (still 0.18.0 from F-Droid). :disappointed:

Maybe a cache issue?

As I explained here and in the comment above, we might need to improve the method which checks whether a client_id is valid to always use the correct one.

Having the same issue on version 18.6

Same issue on 0.19.2

I'm having this issue on all of my phones to, with version 0.19.5. Whats odd is that on some of my frieds phones it works flawlesly.

Fresh installation did not change anything, and the behavior is there on the fdroid/github version.

Any change with 0.19.8?

@opusforlife2: Yes, this should've been fixed by Mauricio in some NPE PR

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Hunter9888x picture Hunter9888x  路  3Comments

mouarfff picture mouarfff  路  3Comments

Wang-GY picture Wang-GY  路  3Comments

Aevann picture Aevann  路  3Comments

cavemandaveman picture cavemandaveman  路  3Comments