Skip to content

ReaderForSelfoss broke #1508

@cmm

Description

@cmm

[ I realize this is not technically the right place to report issues with 3rd-party clients, but also kind of is because there is no other (working) outlet to do so at present, and this specific client is currently linked from the Selfoss home page, so ]

The breakage itself is inability to log in to the Selfoss instance, but something bigger and fishy-looking seems to be going on:

  • The latest build on F-Droid, at the time of writing this, is 124113311-github ("-github"?). The corresponding source tarball is https://f-droid.org/repo/bou.amine.apps.readerforselfossv2.android_124113311_src.tar.gz.
  • The tarball is downloadable, and v124113311 exists on "releases" page (the tarball linked from there is different from the one used by F-Droid, but source code therein seems identical apart from some Gradle stuff), but there are no commits in the repository, reachable from the release tag, that correspond to the (quite non-trivial) changelog of the F-Droid build. In fact, CHANGELOG.md on both the master branch and the v124113311 tag ends at the previous release (v124113301). On the release branch it does end on v124113311, but with a trivial chore-only list of changes.
  • You need to register on the site to report an issue at the supposedly-correct place, but the registration flow is broken: confirmation e-mails are never sent. Which is why I'm reporting here.

FYI to anyone affected, I guess.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions