3 ms·

Apparently it was fixed upstream by Google? https://gitlab.com/fdroid/admin/-/issues/593#note_2681207153 https://gitlab.com/fdroid/admin/-/issues/593#note_2681

by jchw 1y ago

Apparently it was fixed upstream by Google? https://gitlab.com/fdroid/admin/-/issues/593#note_2681207153 https://gitlab.com/fdroid/admin/-/issues/593#note_2681207153 Not sure how long it will take to get resolved but that thread seems reassuring even if there isn't a direct source that it was fixed.

nativeforks 1y ago
Still haven't. Currently, most of the devs aren't aware of this underlying issue!
AnssiH 1y ago
It is not fixed. In the thread you linked to people are confusing a typo correction ("mas fixed" => "was fixed") as a claim about this new issue being fixed. The one that was fixed is this similar old issue from years ago: https://issuetracker.google.com/issues/172048751 https://issuetracker.google.com/issues/172048751
- jchw 1y ago
  Oh, that's unfortunate, very confusing thread.