5
Question about TestFlight
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Nov 2024
5 points (100.0% liked)
Mlem for Lemmy
5379 readers
1 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.
founded 2 years ago
MODERATORS
Yes, we can see them! When Mlem crashes on the TestFlight, you will get an option to share crash logs with us. In some cases this is very useful for us because it shows us the entire traceback of the error, which can help us to reproduce the problem.
If you can reproduce an issue consistently we prefer you submit it via GitHub too if possible. GitHub allows us to keep track of which issues we've resolved or not resolved, we're able to ask follow up questions, and you as the reporter are able to see when we've fixed it. If you mention in the GitHub that you've submitted a crash log (and roughly what time you submitted it at, if the crash log was anonymous) then we can find the relevant crash log which is super helpful for us.
We don't really have a notification system set up for TestFlight feedback. I go through it whenever I remember to, but I frequently forget 😅 A lot of people submitted similar crash reports to the one you submitted feedback on, but that particular issue is difficult to reproduce consistently so make take some time to fix.
Thanks! This is great to hear. I will stop submitting them anon. Mostly the ones I have are random.
To be clear, we still want as many TestFlight crash log submissions as possible, even if they're anonymous. If it's a crash that you can reproduce, submitting a GitHub issue is helpful too :)
TestFlight tries to group similar crash logs together, so crashes that can seem "random" can actually help to form a pattern when put together with all the other logs.
I meant I would send my email address when submitting them so if you need to contact me for more information you could.
Ah, that makes sense! Thanks ❤