Thunder App

3652 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

Hotfix Alpha Release [v0.2.3+16] (github.com)

submitted 2 years ago by darklightxi@lemmy.world to c/thunder_app@lemmy.world

3 comments fedilink hide all child comments

Hey everyone, just wanted to make a quick announcement about this hotfix release. This minor hotfix release addresses the following issue:

Using "Reply" FAB action inside a post fails with "Could not determine post to comment to"

As always, if you are using the Google Play version or App Store version, please note that it may take a bit of time before you receive the update.

Thanks!

top 3 comments

sorted by: hot top controversial new old

[–] Jackthelad@lemmy.world 2 points 2 years ago

It works!

[–] eatham@aussie.zone 1 points 2 years ago (1 children)

It works! Quick question, whats going on with the naming scheme?

[–] darklightxi@lemmy.world 2 points 2 years ago

I mentioned this briefly in the Matrix development channel, but for those who are not part of it, this is what is happening:

Google Play Store requires the build number to increase for every new release (this is the +16 in this case)
App Store requires the version number to increase for every new release (this is the 0.2.3 part)

To be able to accommodate both Google Play and App Store, I'm temporarily increasing both the version number and build numbers for releases. In the future, the naming scheme might be adjusted to just contain the version number (0.2.3) for more consistency!