Sjmarf

Ah, that makes sense! Thanks ❤

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.

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.

Can we get a back button on iPad?

I’m not sure what you mean by this. Could you elaborate please? There is a back button at the top of the screen here:

I tried to get used to the glow around sections in the OLED theme, but it’s just distracting and frankly ugly. I’m requesting an improvement here as well.

Yeah, we aren’t happy with it either. Unfortunately adding a border to those elements isn’t simple to do - Apple really doesn’t want us changing the appearance of forms. We’ll try to come up with a better solution before 2.0 release (no promises though).

As Eric said, if you tap on the error it’ll give you more info. Have you tried a different image? Some instances impose a maximum file size on the images you can upload. If that happens, it’ll show the “error” toast. We’d like to make that error case show a more obvious warning in future.

Thanks. It looks like this only happens on beehaw.org so it’s possibly related to older Lemmy versions. We’ll look into fixing it 👍

Thanks for the bug report. Do you have a link to a comment chain where this happens?

Hi! In the Mlem v2 beta there’s a setting for this at General -> Swipe Actions. In Mlem v1 this isn’t possible.

Hi! Mlem v1 requires iOS 16 or later and Mlem v2 requires iOS 17 or later. Supporting a wider range of versions would take up significantly more development time, and prevent us from using newer APIs. For that reason we choose to support only the two most recent iOS versions, which most of our users fall under.

We’re sorry that you can’t use Mlem on your old iPad. You could try Voyager instead, which supports any iOS version (I think).

Thanks for the info. That’s not the intended behavior; we’ll make sure it works properly in Mlem v2. Sorry about that!

Hey! In Mlem v1 there’s a setting for this at General > Confirm Image Uploads. We haven’t added this to the beta version yet but will be doing so.

We’re glad you like it 😄

It should be back now on the weekly TestFlight :)

Yes, we’ll be adding it back in at some point 👍

I’m glad you like it :) Yes, we’re re-doing almost all of the code from scratch. It’s a lot of work but we’re getting there!

Eric’s posted the links :) Worth noting is that Mlem v2 doesn’t yet support mod/admin stuff, so if you use Mlem for administration duties you may want to consider waiting until the full release.

Sure, we’ll add an option for this in Mlem 2.0. We’re glad you’re enjoying Mlem 😄

I’m glad you’re enjoying Mlem :)

Hey! We haven’t implemented post searching yet, though we’ll be implementing it in the next version of Mlem (2.0).

To block an instance, you need to go to the instance page. You can do this by searching for the instance in the “Search” tab, or by tapping the (…) button in the top-right of a community page or profile page and tapping the instance name. In the instance page, you can tap the (…) button in the top-right and then choose “block” to block the instance.

To view blocked instances go to the Settings tab, then tap the button at the top of the page (your username), then tap “Blocklist”.

I should mention that I can’t get the new Testflight to work either. I use the old version, the Testflight for some reason is unavailable to me. Is it perhaps because I use an older model iPhone?

We closed the old TestFlight, as we don’t plan to release any major updates to Mlem v1 aside from critical bug fixes. The new TestFlight is for testing the upcoming Mlem v2, and requires iOS 17 or later. Mlem v1 supported iOS 16 and above. You can read more about our reasons for dropping iOS 16 support here.

Similarly, I sometimes don’t see comments, eg. a post might have 5 comments but I only see 3 or none.

Yeah, this happens because the Lemmy API only returns a limited number of comments initially for large comment threads. It’s the client’s responsibility to request more comments when needed. On the Lemmy website UI, you have to click a “Load (x) more comments” button, and it’ll load the rest. Mlem v1 (and presumably Voyager) haven’t implemented this yet. We’re planning to add it to Mlem v2.