Skip to content
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

Soundcloud intermittent JSON parsing error #11538

Open
6 tasks done
davidasunmo opened this issue Sep 15, 2024 · 0 comments
Open
6 tasks done

Soundcloud intermittent JSON parsing error #11538

davidasunmo opened this issue Sep 15, 2024 · 0 comments
Labels
bug Issue is related to a bug soundcloud Service, https://soundcloud.com/

Comments

@davidasunmo
Copy link

davidasunmo commented Sep 15, 2024

Checklist

  • I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
  • I made sure that there are no existing issues - open or closed - which I could contribute my information to.
  • I have read the FAQ and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected version

0.27.2

Steps to reproduce the bug

  1. Have a bunch of SoundCloud songs in a playlist
  2. Play them
  3. Wait.

Expected behavior

All Soundcloud songs play without error.

Actual behavior

Eventually one of the songs will play with a duration of exactly 2 seconds (no audio), then skip to the next song, and will get the error notification with JSON parsing error in the stack trace.

Going back to play the offending song will still have it be 2 seconds: only restarting NewPipe allows you to properly reload the song, but eventually another song will cause the error again and have to repeat the process if you want to hear that song.

Other songs are still able to be played even though the one song doesn't load.
The occurrence of this bug is rare.
I have tried brute forcing it by going through my playlist multiple times to make it show up, with WiFi and mobile data, but to no avail yet.

Screenshots/Screen recordings

No response

Logs

Exception (stack trace may be a bit scuffed cus idk if I copied it properly)

  • User Action: play stream
  • Request: Loading failed for [Acceptance]: https://soundcloud.com/slowmagic/acceptance
  • Content Country: GB
  • Content Language: en-GB
  • App Language: en_GB
  • Service: SoundCloud
  • Version: 0.27.2
  • OS: Linux Android 9 - 28
Crash log

org.schabi.newpipe.player.mediasource.FailedMediaSource$StreamInfoLoadException: org.schabi.newpipe.extractor.exceptions.ParsingException: Could not parse json response
 at org.schabi.newpipe.player.playback.MediaSourceManager.lambda$getLoadedMediaSource$7(MediaSourceManager.java:448)
 at org.schabi.newpipe.player.playback.MediaSourceManager.$r8$lambda$7wkrzYpwfZdms79okpk8_MCaW4U(MediaSourceManager.java:0)
 at org.schabi.newpipe.player.playback.MediaSourceManager$$ExternalSyntheticLambda5.apply(R8$$SyntheticClass:0)
 at io.reactivex.rxjava3.internal.operators.single.SingleOnErrorReturn$OnErrorReturn.onError(SingleOnErrorReturn.java:55)
 at io.reactivex.rxjava3.internal.operators.single.SingleMap$MapSingleObserver.onError(SingleMap.java:70)
 at io.reactivex.rxjava3.internal.operators.single.SingleDoOnError$DoOnError.onError(SingleDoOnError.java:63)
 at io.reactivex.rxjava3.internal.operators.single.SingleSubscribeOn$SubscribeOnObserver.onError(SingleSubscribeOn.java:73)
 at io.reactivex.rxjava3.internal.operators.maybe.MaybeToSingle$ToSingleMaybeSubscriber.onError(MaybeToSingle.java:89)
 at io.reactivex.rxjava3.internal.operators.flowable.FlowableElementAtMaybe$ElementAtSubscriber.onError(FlowableElementAtMaybe.java:94)
 at io.reactivex.rxjava3.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.onError(MaybeConcatArray.java:100)
 at io.reactivex.rxjava3.internal.operators.maybe.MaybeFromSingle$FromSingleObserver.onError(MaybeFromSingle.java:82)
 at io.reactivex.rxjava3.internal.operators.single.SingleDoOnSuccess$DoOnSuccess.onError(SingleDoOnSuccess.java:65)
 at io.reactivex.rxjava3.internal.operators.single.SingleFromCallable.subscribeActual(SingleFromCallable.java:47)
 at io.reactivex.rxjava3.core.Single.subscribe(Single.java:4855)
 at io.reactivex.rxjava3.internal.operators.single.SingleDoOnSuccess.subscribeActual(SingleDoOnSuccess.java:35)
 at io.reactivex.rxjava3.core.Single.subscribe(Single.java:4855)
 at io.reactivex.rxjava3.internal.operators.maybe.MaybeFromSingle.subscribeActual(MaybeFromSingle.java:41)
 at io.reactivex.rxjava3.core.Maybe.subscribe(Maybe.java:5377)
 at io.reactivex.rxjava3.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.drain(MaybeConcatArray.java:153)
 at io.reactivex.rxjava3.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.request(MaybeConcatArray.java:78)
 at io.reactivex.rxjava3.internal.operators.flowable.FlowableElementAtMaybe$ElementAtSubscriber.onSubscribe(FlowableElementAtMaybe.java:66)
 at io.reactivex.rxjava3.internal.operators.maybe.MaybeConcatArray.subscribeActual(MaybeConcatArray.java:42)
 at io.reactivex.rxjava3.core.Flowable.subscribe(Flowable.java:16144)
 at io.reactivex.rxjava3.internal.operators.flowable.FlowableElementAtMaybe.subscribeActual(FlowableElementAtMaybe.java:36)
 at io.reactivex.rxjava3.core.Maybe.subscribe(Maybe.java:5377)
 at io.reactivex.rxjava3.internal.operators.maybe.MaybeToSingle.subscribeActual(MaybeToSingle.java:46)
 at io.reactivex.rxjava3.core.Single.subscribe(Single.java:4855)
 at io.reactivex.rxjava3.internal.operators.single.SingleSubscribeOn$SubscribeOnObserver.run(SingleSubscribeOn.java:89)
 at io.reactivex.rxjava3.core.Scheduler$DisposeTask.run(Scheduler.java:644)
 at io.reactivex.rxjava3.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:65)
 at io.reactivex.rxjava3.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:56)
 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:1167)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
 at java.lang.Thread.run(Thread.java:764)
Caused by: org.schabi.newpipe.extractor.exceptions.ParsingException: Could not parse json response
 at org.schabi.newpipe.extractor.services.soundcloud.SoundcloudParsingHelper.resolveFor(SoundcloudParsingHelper.java:166)
 at org.schabi.newpipe.extractor.services.soundcloud.extractors.SoundcloudStreamExtractor.onFetchPage(SoundcloudStreamExtractor.java:61)
 at org.schabi.newpipe.extractor.Extractor.fetchPage(Extractor.java:60)
 at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:77)
 at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:72)
 at org.schabi.newpipe.util.ExtractorHelper.lambda$getStreamInfo$3(ExtractorHelper.java:118)
 at org.schabi.newpipe.util.ExtractorHelper.$r8$lambda$YTHJjScxCJNO1LTCqs3IKy35iyY(ExtractorHelper.java:0)
 at org.schabi.newpipe.util.ExtractorHelper$$ExternalSyntheticLambda3.call(R8$$SyntheticClass:0)
 at io.reactivex.rxjava3.internal.operators.single.SingleFromCallable.subscribeActual(SingleFromCallable.java:43)
 ... 23 more
Caused by: com.grack.nanojson.JsonParserException: Expected JSON value, got 0 on line 1, char 0
 at com.grack.nanojson.JsonTokener.createParseException(Unknown Source:0)
 at com.grack.nanojson.JsonParser.currentValue(Unknown Source:0)
 at com.grack.nanojson.JsonParser.parse(Unknown Source:0)
 at com.grack.nanojson.JsonParser$JsonParserContext.from(Unknown Source:0)
 at org.schabi.newpipe.extractor.services.soundcloud.SoundcloudParsingHelper.resolveFor(SoundcloudParsingHelper.java:164)
 ... 31 more


Affected Android/Custom ROM version

Android 9

Affected device model

Samsung Galaxy S8

Additional information

No response

@davidasunmo davidasunmo added bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up labels Sep 15, 2024
@opusforlife2 opusforlife2 added soundcloud Service, https://soundcloud.com/ and removed needs triage Issue is not yet ready for PR authors to take up labels Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue is related to a bug soundcloud Service, https://soundcloud.com/
Projects
None yet
Development

No branches or pull requests

2 participants