this post was submitted on 01 Mar 2025
4 points (100.0% liked)

Arctic

487 readers
7 users here now

Arctic is a Lemmy client for iOS built on pure Swift. It currently supports iOS 15+ and Lemmy v0.17+

Get the latest version on TestFlight, or check it out on the AppStore.

If you would like to support Arctic’s development, feel free to Buy Me A Coffee

founded 2 years ago
MODERATORS
 

Trying logging in with my account, it only shows my subscription and activity but can’t load my profile page It also appear when I tap on the profile page

Example log: [2025-03-01 10:16:47 +0000] [error] [arctic] [fetchUserDetails(person_id:username:)] Error loading user details: lemmyError(message: Optional("couldnt_find_person"), code: 400)

top 4 comments
sorted by: hot top controversial new old
[–] CreatureSurvive@lemmy.world 2 points 1 day ago (1 children)

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
[–] StrangeMed@lemmy.world 1 points 1 day ago (2 children)

I solved the problem. The issue arises when you enter your email and password in the login tab. The app attempts to find a username that matches the email precisely, which leads to an error. However, when I log in using my username instead, everything worked flawlessly.

[–] CreatureSurvive@lemmy.world 3 points 22 hours ago

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!

[–] BigDiction@lemmy.world 1 points 21 hours ago

You at least found a workaround!