Mlem for Lemmy

5526 readers

3 users here now

Official community for Mlem, a free and open-source iOS Lemmy client.

Rules

Keep it civil.
This is a forum for discussion about Mlem. We welcome a degree of general chatter, but anything not related to Mlem may be removed at moderator discretion. This is not a forum for iPhone/Android debate. Posts and comments saying nothing but "iOS bad/I use Android" will be removed as off-topic.
We welcome constructive criticism, but ask that it be both precise and polite.

FAQ

When will insert feature here be implemented?
- Check our issue board--if there isn't an issue open for the feature you want, feel free to open an issue or make post! Just remember that devs are people too--we're doing this for free in our spare time, and building a quality app takes a lot of patient work.
Is Mlem available for Android?
- No. Mlem is written using SwiftUI, which is not currently supported on Android. If such support becomes available, we will look into bringing Mlem to our Android friends.
How do I join the beta?
- We are currently testing our new 2.0 codebase on TestFlight. We have two beta groups: a weekly group that receives the current state of our development branch every week, and a stable group that receives a curated pre-release build at the end of each development cycle.
- Join the weekly beta
- Join the stable beta
How do I join the dev team?
- Head over to our recruitment channel, or go straight to our GitHub and read CONTRIBUTING.md to get started.

Download Mlem for iOS

GitHub

Website

Donate to Mlem

founded 2 years ago

MODERATORS

ericbandrews@lemmy.ml

darknavi@vlemmy.net

Kronusdark@lemmy.world

Update TestFlight build at least to the App Store build (lemm.ee)

submitted 1 year ago by narc0tic_bird@lemm.ee to c/mlemapp@lemmy.ml

4 comments fedilink hide all child comments

Would it be possible to update the TestFlight build whenever a new build is pushed to the App Store? This way, TestFlight users won't have to switch to the App Store version because the TestFlight version would always be at least as new.

top 4 comments

sorted by: hot top controversial new old

[–] ericbandrews@lemmy.ml 6 points 1 year ago

Oh yeah, whoops! Bumped the build, it should be the same in both now.

Normally the deployment strategy is to merge the TestFlight tagged code into master once we're ready to submit, then rebuild from master and submit that build--it's a "different build" but the exact same code. This time we ran into some Apple Review snags (they wanted a way to permanently delete your Lemmy account from within the app), so we had to hotfix that on master and forgot to release that to back to the TestFlight.

[–] hddsx@lemmy.ca -2 points 1 year ago (1 children)

Why not just use the stable App Store version instead of the bleeding edge Test Flight build? Isn’t Test Flight for testing purposes and hence likely to contain more bugs? Fixes should be merged back into the stable branch.

[–] narc0tic_bird@lemm.ee 6 points 1 year ago (1 children)

Yes it's for testing, but there's not much point in testing an outdated build.

[–] hddsx@lemmy.ca 1 points 1 year ago

Right, but there’s a stable release. If there’s more issues to test, there will be a new test flight. Why have stable builds released under test flight?