This is definitely a caching issue. That menu is updated only as needed, but does not check for external changes. I’m going to update that so it is not cached and rechecks its state when opened.

I’m able to reproduce the issue with this video. I’ll look into it. It seems to only affect HLS streams with variable resolution. So it is likely not updating the zoom properly since the aspect ratio doesn’t change, but the size does.

Whoops, that’s not supposed to happen. It’s a super simple fix, I’ll have this patched really quick.

Sorry I’ve been absent the last week, I’ve been busy and haven’t had much time to work on Arctic. I appreciate all the feedback and reports!

Ahh, more than likely it tried to generate a link preview for a localhost link. I’ll patch this so localhost links are not fetched.

Good to know, I see exactly what is causing this issue. I’ll have this patched in the next update. Thanks for letting me know!

This is something I haven’t seen before. I’m curious if this may have been an issue with the API considering your account was so new.

In case this is not an issue with the api, would you mind opening the profile tab, and then going to Settings -> About -> Arctic Logs. There should be an entry that shows the raw api request including the username sent with the request. It’s possible that the username is malformed in some way which would cause this issue.

The log entry I am looking for should look something like this:

[2025-03-02 01:13:49 +0000] [info] [lemmy] [performRequestWithCheckedResponse(_:)] LemmyAPI request: https://lemmy.world/api/v3/user?auth=_private_&limit=20&page=1&saved_only=false&sort=New&username=CreatureSurvive%40lemmy.world

I just released an update to address this issue, thanks for letting me know about this!

I’m able to reproduce this on my end as well. I’ll see if I can’t release a hotfix for this tonight when I get home. Thanks for letting me know about this.

v0.4.5.10 had a lot of major changes behind the scenes, and a few issues slipped through that I didn’t catch in my tests.

Just a little update on v1.0 support. I spent yesterday writing a parser for the v1.0 api that generates a swift library for me that is compatible with Swimmy for handling requests. In testing, it looks like everything is working except for image upload methods. For uploads I’ll need to update the parser for generating these requests. Now I just need to write a compatibility layer to map the responses into a common format for Arctic.

Thank you for cross-posting this. I haven’t started working on adding support just yet.

Up until now, the api changes have been relatively minor, which I’ve been able to work around using optional and version checks. This release has a lot more breaking changes, and I’ll need to change how the api is accessed.

I’m planning to extract the Lemmy api from Arctic, and write a middleware that I’ll use for handling api requests. This will be a lot easier to maintain, and allow me to decouple Arctic from the API format.

I didn’t see any reference to a stable release date for v1.0, but I’ll do my best to have Arctic ready for the changes before they roll out.

I’m planning to start working on this tomorrow. I’ll post back in this thread with any development updates.

Thanks, it’s been an insanely busy month, but definitely worth it!

Thank you so much, it’s great to get feedback from a cross-platform user!

Done.

Now when you tap the search tab while it’s already active, firstly it will scroll to the top of the results if it’s not already there, otherwise it will activate the search bar. If it is scrolled down, you can double tap to scroll to the top and activate the search bar. And just like before you can long press the search tab while it’s not selected and it will open the search view and activate the search bar.

I’ve found myself accidentally doing this and it not working, but I never got around to adding this feature until now.

I should hopefully have an update out soon, I have a lot of other fixes and some new features just about ready for a release.

You can view instance and community modlogs with !arctic@lemmy.world

Just to clarify, you do not need to pay the subscription when building an iOS app. Apple does have free tier developer accounts with limitations. Such as you can only install 3 development apps on an actual device at a time, you need to resign (reinstall) the apps every 7 days, certain capabilities are not available such as Push Notifications, etc.

Now, for releasing to the AppStore or TestFlight, you will need to pay the subscription fee. You also need to continue paying the subscription in order to keep the apps on the AppStore.