this post was submitted on 11 Oct 2023
13 points (100.0% liked)

LibreTube

339 readers
1 users here now

An alternative frontend for YouTube, for Android.

https://github.com/libre-tube/LibreTube

founded 1 year ago
MODERATORS
13
Android app crashes (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by kWazt@lemmy.world to c/libretube@feddit.rocks
 

Doesn't matter what I do, which instance I'm on, Android app crashes every time I start a video. I've reinstalled several times, didn't solve anything. Clean install - pick an instance - start random video - crash. What do? I left NewPipe SponsorBlock for LT because NP started crashing all the time...

ETA: referringtoboth 0.17.1 and 0.18.1

top 10 comments
sorted by: hot top controversial new old
[–] Emanuel 2 points 1 year ago (1 children)

This was fixed on version 0.19.0.

[–] kWazt@lemmy.world 1 points 1 year ago

Thanks for the assist!

[–] K4mpfie@feddit.de 1 points 1 year ago (2 children)

I have the same issue. This is my crashreport kotlinx.datetime.DateTimeFormatException: j$.time.format.DateTimeParseException: Text '2023-10-11T15:18:46-07:00' could not be parsed, unparsed text found at index 10 at kotlinx.datetime.LocalDate$Companion.parse(SourceFile:20) at kotlinx.datetime.serializers.LocalDateIso8601Serializer.deserialize(SourceFile:15) at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue$1(SourceFile:68) at okio._UtilKt.decodeSerializableElement(SourceFile:11) at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableElement(SourceFile:50) at com.github.libretube.api.obj.Streams$$serializer.deserialize(SourceFile:555) at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue$1(SourceFile:68) at kotlinx.serialization.json.Json.decodeFromString(SourceFile:26) at com.jakewharton.retrofit2.converter.kotlinx.serialization.DeserializationStrategyConverter.convert(SourceFile:33) at retrofit2.OkHttpCall.parseResponse(SourceFile:57) at retrofit2.OkHttpCall$1.onResponse(SourceFile:5) at androidx.appcompat.app.AlertController$2.onSuccess(SourceFile:34) at androidx.work.Worker$2.run(SourceFile:131) 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:919) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@e16a52a, Dispatchers.IO] Caused by: j$.time.format.DateTimeParseException: Text '2023-10-11T15:18:46-07:00' could not be parsed, unparsed text found at index 10 at j$.time.format.DateTimeFormatter.parseResolved0(Unknown Source:160) at j$.time.format.DateTimeFormatter.parse(Unknown Source:11) at j$.time.LocalDate.parse(Unknown Source:10) at j$.time.LocalDate.parse(Unknown Source:2) at kotlinx.datetime.LocalDate$Companion.parse(SourceFile:6) ... 15 more

[–] ohlaph@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

The error message is obvious. It's getting an invalid date object and can't parse it so it crashes. The network call isn't handling error cases and tries to serialize the object without catching the error. The network response might have the invalid date most likely, do the app needs to handle such a case.

What app is this? LibreTube.. got it.

[–] K4mpfie@feddit.de 1 points 1 year ago (1 children)

Yeah smthng about dates causing errors is what I understood too. The app seems to be up to date tho. At least F-droid is not finding a newer version.

[–] ohlaph@lemmy.world 2 points 1 year ago

According to this ticket, it should be in the next release.

https://github.com/libre-tube/LibreTube/issues/4884

[–] netchami@sh.itjust.works 1 points 1 year ago (1 children)

I had the same issue, fixed it by choosing a different Piped instance (kavin.rocks)

[–] droopy4096@lemmy.ca 2 points 1 year ago (1 children)

that was really helpful here. After hopping between Piped instances I finally found the one that works. Will take a note to do that in the future.

I'm guessing this may also be a result of google slamming the doors shut for 3rd party access lest it uses their ads-ridden API

[–] netchami@sh.itjust.works 0 points 1 year ago

I'm guessing this may also be a result of google slamming the doors shut for 3rd party access lest it uses their ads-ridden API

That's correct