feddit.online

211 readers

2 users here now

Posts related to this server. Everyone who is a member of this server should join this community to know about changes and maintenance activities.

Post items that would be of interest to feddit.online members.

Rules

This community is only for discussions related to the feddit.online server

founded 1 year ago

MODERATORS

feddit-admin@feddit.online

Jerry@feddit.online

Help! Unable to log in through any android PieFed client (feddit.online)

submitted 3 days ago* (last edited 3 days ago) by skeevy_scallops@feddit.online to c/feddit_online@feddit.online

2 comments fedilink hide all child comments

I apologize if there's a better place to post this, but this seemed to make the most sense to me.

I've been trying out different instances and ultimately have settled of finding more user engagement over specific content curation. All the instances I've tried so far have worked flawlessly when logging in through one of the many android clients. Unfortunately after signing up for feddit.online, it seems I am unable to login through any of those apps. I've tried Summit, Blorp, and Interstellar and they all return some sort of login error. Usually including something along the lines of "login successful but local_user_view is null."

I'm wondering if this is user error? Maybe I'm missing something obvious. Or does feddit.online just not work with these clients? I don't see why it wouldn't. Can someone help me figure this out or provide whatever obvious information I might be missing?

Edit: Immediately after making this post I tried logging in again and it worked. I'm assuming some kind of preventative measure against unused accounts? Mods feel free to take this down, but maybe leaving this up can help another noob like me in the future.

you are viewing a single comment's thread
view the rest of the comments

[–] feddit-admin@feddit.online 3 points 3 days ago

This comes up once in a while, and not just with feddit.online. I've never figured it out. I only know that eventually the problem disappears and the login happens. My theory is that somewhere the login error is getting cached, and regardless of whether you enter the correct credentials, you get the failure from the cache.

I've wanted to test this by refreshing the entire instance cache while it's happening to see if it would help, but cache entries time out eventually, and maybe this is what resolved it for you. Had you not had it self-resolved, then I would have tried the cache refresh.

I'm going to do more investigation this weekend.

Thanks for reporting it.