Crash at attempting to play a videi on 0.16.13 #10
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-fdroid#10
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Issue
Steps to reproduce
Expected behaviour
Video is played
Actual behaviour
Application crashes.
System Configuration
Anything Else
Trace
Screenshots
Internal Use
Acceptance Criteria
Definition of Done
This is going to be fixed on 0.16.14a or next release. Unfortunately, 0.16.14 was already built by FDroid servers when this issue was noticed, so the fix is not going to get there.
Sorry for the inconvenience. A fixed release will land in a few days, depending on FDroid build servers.
I've got this problem also. It's infuriating that I can't watch Jeremy's latest vids on his own platform. Pls never again.
Why don't you have a more current apk available for download direct? Still waiting to try this broken app.
FDroid signes every release with a digital signature created for every app. They own the key to sign the release, not LBRY, @viceverser
I don't understand... I can direct download other apps as an apk, that get direct push in app updates, why is LBRY such an exception? Surely there is no need for f-droid to play middle man? Especially if they are this incapable of keeping up with the actual project? And if big tech has taught us anything this year, it's that any vendor we use can be targeted to attack any competition of the tech monopolies... How long you think before f-droid is slandered in the media to remove apps that are a threat to the oligopoly? I'm just saying, if there is an option to directly release to your audience, why not give the option?
Fixed on now released 0.16.15 version