search

Paperback-iOS / app

Repository to host app releases, issues, and feature requests for Paperback
https://paperback.moe/
663 stars 20 forks source link

[BUG] “Content settings unavailable” #364

Closed henderea closed 3 years ago

henderea commented 3 years ago

Describe the bug In general settings in 0.6.0, the content filtering section says "content settings unavailable", and when looking in the source repos, I see a message that says X results are filtered out, with no results actually showing up.

To Reproduce Look in general settings and a source repo

Expected behaviour There should be some sort of content settings and I should see sources in the repos.

App Version V0.6.0-1.0.2

Screenshots image image

TheNetsky commented 3 years ago

Yoinked from our support bot, should solve the issue image

Portal here

henderea commented 3 years ago

Thanks, that fixes the issue. Might be good to have a button in the app to launch the portal.

TheNetsky commented 3 years ago

That's not allowed by Apple guidelines, so we can't do that.

henderea commented 3 years ago

Too bad. Oh well. Thanks for the quick answers.

Oh, and I should point out that even the official "paperback" repo was filtered out before I went to the portal, so you might want to fix that. The second screenshot I posted was from the "official repo". I can't imagine the official "paperback" repo is actually one that would need to be filtered out, since the whole point of it is to remove adult content to meet App Store guidelines.

TheNetsky commented 3 years ago

Sources without the new content rating will automatically be marked as "adult". And since the Paperback sources needs to work on both 0.5 and 0.6 it doesn't have this content rating, else it wouldn't be backwards compatible on 0.5.

henderea commented 3 years ago

Makes sense. I imagine it'll be fixed by the time the app makes it to the App Store (if we're lucky enough to get it there), so it isn't a big deal.

github-actions[bot] commented 5 months ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.