Thunder App

3720 readers

1 users here now

An open-source, cross-platform Lemmy client for iOS and Android.

This community is intended to discuss features and feature suggestions for Thunder; as well as friendly, respectful talks about Lemmy in general.

Please use the GitHub repository linked below to submit bug reports, so keeping track of them is easier, and make sure to search first if you already can find an issue for your report.

If there are any developers who would like to contribute, feel free to reach out on GitHub!

General Links
Website: Link
GitHub Repository: Link
Matrix Space: Link

Android Releases
IzzyOnDroid: Link
Google Play: Link

iOS Releases
Apple App Store: Link
TestFlight Beta: Link

Related Communities
Nightly Community: Link

founded 2 years ago

MODERATORS

darklightxi@lemmy.world

poolitzer@lemmy.world

darklightxi@lemmy.ca

micahmo@programming.dev

micahmo@lemmy.world

BUG? Settings return to default after a load failure (self.thunder_app)

submitted 3 weeks ago by SanctimoniousApe to c/thunder_app@lemmy.world

1 comments fedilink hide all child comments

I haven't tested this enough to be certain yet, but I happen to have lost my Internet connection a few times today (phone & hotspot issues) while using Thunder. Once the connection was fixed & I reloaded, it seems like the load failure caused Thunder to reset some settings to default such as my preferred sort order, and nav bar visibility.

I'd normally test more before posting to be sure, but it's way past my bedtime & I've got a full day tomorrow, so I wanted to post the possibility before I forgot.

you are viewing a single comment's thread
view the rest of the comments

[–] darklightxi@lemmy.world 1 points 2 weeks ago

Hey there!

If you're logged in, Thunder determines your post sort settings from your Lemmy account settings. If there's a bad connection, Thunder might then default back to the guest sort settings located here: Thunder Setting: General > Default Feed Type and Sorting > Default Feed Sort Type

As for the nav bar visibility, Thunder should be respecting that setting regardless of network connectivity. If you're able to reproduce this issue, feel free to open up a new GitHub issue on this so that I can take a closer look at it!