search

clragon / e1547

A sophisticated e621 browser
https://e1547.clynamic.net/
GNU General Public License v3.0
209 stars 16 forks source link

User data parsing fails #63

Closed erisdev closed 2 years ago

erisdev commented 2 years ago

i couldn't figure out how to reply on the play store...

Screenshot_20220214-015459_e1547

so, i get this error any time i try to modify my blacklist, and the list itself shows up blank, as you can see. my blacklist is fairly simple—less than 20 items and only single tags.

i'm logged in and able to view and edit favorites and such with no issue, but of potential interest, if i click my username in the settings, i get "Failed to load user". i haven't encountered any other issues accessing my account through the app so far, and i can view other user profiles just fine too. the only thing i can think of is maybe having a dot in my username is fucking something up?

clragon commented 2 years ago

Hi, its possible that the parser for user data somehow fails to process your user correctly. The dot shouldnt be an issue though.

Could you tell us what your username is? If you cannot visit your own user profile page, that hints that there is some discrepancy between the public user data and the parser.

clragon commented 2 years ago

Also from your screenshot we can see that the bottom bar has fallen behind your navigation bar. interesting! We assume thats because of edge to edge mode on android. We will try to employ a fix for the next version.

erisdev commented 2 years ago

apologies for the delay, i'm currently out of town for anthro new england and haven't been online much.

i'd rather not have my username publicly associated with my github account, but could i send it to you privately somehow?

clragon commented 2 years ago

sure thing, we have a discord server for the app where you can find me, or we also have a support email on the playstore.

erisdev commented 2 years ago

oh, hell, i forgot to respond to this—my apologies! i was out of town and just got back mid last week.

i am not sure that commit is going to fix the issue. i had a look at the api response for my user account and none of the fields appear tobe missing, including the one that was removed. i'll hop on the discord momentarily!

erisdev commented 2 years ago

for the curious: the problem was most likely related to my username having a dot in it. the api endpoint was throwing a 404 and changing my username to one without a dot fixed it. no relation to the new bug the commit above fixed!

addendum: dots are not allowed in usernames, but i signed up before they banned dots. dot crimes.