Stopped working with Milktea #351

Closed
opened 2023-02-28 08:18:21 +00:00 by volpeon · 3 comments

A while ago I noticed that Milktea seemed kind of broken with my instance. Most notably, I couldn't use custom emojis anywhere, and if I opened a note its parent notes and replies wouldn't show up.

My phone broke and I tried to set Milktea up on a new phone, but I can't even add my account there. Tapping the "Authenticate" button briefly shows the loading inidcator and then nothing happens.

Unfortunately, I'm not sure how to provide debugging info. Milktea doesn't expose such a feature, and the Foundkey log doesn't show any errors.

A while ago I noticed that Milktea seemed kind of broken with my instance. Most notably, I couldn't use custom emojis anywhere, and if I opened a note its parent notes and replies wouldn't show up. My phone broke and I tried to set Milktea up on a new phone, but I can't even add my account there. Tapping the "Authenticate" button briefly shows the loading inidcator and then nothing happens. Unfortunately, I'm not sure how to provide debugging info. Milktea doesn't expose such a feature, and the Foundkey log doesn't show any errors.
Owner

My current guess is that Milktea checks the Nodeinfo and "foundkey" is not one of its recognized types: 9d4807bc9f/modules/model/src/main/java/net/pantasystem/milktea/model/nodeinfo/NodeInfo.kt (L56-L63)

From looking at that files history it seems that Milktea started using nodeinfo only in January 2023, which would explain why it broke now.

My current guess is that Milktea checks the Nodeinfo and `"foundkey"` is not one of its recognized types: https://github.com/pantasystem/Milktea/blob/9d4807bc9f79b5fcb17a8ca4cf485cbb79f1a900/modules/model/src/main/java/net/pantasystem/milktea/model/nodeinfo/NodeInfo.kt#L56-L63 From looking at that files history it seems that Milktea started using nodeinfo only in January 2023, which would explain why it broke now.
Owner

Some cursing, downloading Milktea and console.log debugging on my instance later: If what I said above is not the issue, it will definitely be stopped by this: Milktea requests the permissions "read:gallery", "write:gallery", "read:gallery-likes", "write:gallery-likes" from /api/app/create. But because we removed galleries, those permissions do not exist and thus the API validation returns a 400 error.

Some cursing, downloading Milktea and console.log debugging on my instance later: If what I said above is not the issue, it will definitely be stopped by this: Milktea requests the permissions `"read:gallery", "write:gallery", "read:gallery-likes", "write:gallery-likes"` from `/api/app/create`. But because we removed galleries, those permissions do not exist and thus the API validation returns a 400 error.
Owner

Closing this issue since it turned out this is not a problem with Foundkey.

Closing this issue since it turned out this is not a problem with Foundkey.
Sign in to join this conversation.
No labels
feature
fix
upkeep
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: FoundKeyGang/FoundKey#351
No description provided.