Akkoma Backend: Notifications Cause 400 Bad Request because Status notification type is not Supported (issue restored from email) #1375

Open
opened 2025-09-18 12:54:46 +00:00 by hj · 1 comment
Owner

Environment info

  • Browser, version, OS, platform: Librewolf, Windows 11 (was able to reproduce this on Chrome but that is not relevant)
  • Instance URL: https://froth.zone
  • Frontend version (see settings -> about): 40eb565f
  • Backend version (see settings -> about): Akkoma 3.15.2-3007-g31bf1ec2-froth-zone
  • Browser extensions (ublock, rikaichamp etc): N/A
  • Known instance/user customizations: None that I am aware of that are relevant (I was able to reproduce with vanilla akkoma and vanilla pleroma-fe)

Bug description & reproduction steps

  • Log in
  • Notifications fail to load, 400 Bad Request in log
  • Send API request without &include_types[]=status in the URL, the notifications load.

For some reason I cannot re-create this on production but I can reproduce this locally.

The error is caused by Akkoma not supporting the status notification type, as seen in my """workaround""". Getting rid of it fixes any problems.

Bug seriousness

  • How annoying it is: Annoying enough as to be unusable
  • How often does it happen: Always
  • How many people does it affect: Anyone who is logged in using Akkoma backend and Pleroma frontend
  • Is there a workaround for it: If this counts, otherwise, no.

original issue by @SamTherapy

## Environment info - Browser, version, OS, platform: Librewolf, Windows 11 (was able to reproduce this on Chrome but that is not relevant) - Instance URL: https://froth.zone - Frontend version (see settings -> about): 40eb565f - Backend version (see settings -> about): Akkoma 3.15.2-3007-g31bf1ec2-froth-zone - Browser extensions (ublock, rikaichamp etc): N/A - Known instance/user customizations: None that I am aware of that are relevant (I was able to reproduce with vanilla akkoma and vanilla pleroma-fe) ## Bug description & reproduction steps - Log in - Notifications fail to load, 400 Bad Request in log - Send API request without &include_types[]=status in the URL, the notifications load. For some reason I cannot re-create this on production but I can reproduce this locally. The error is caused by Akkoma not supporting the status notification type, as seen in my """workaround""". Getting rid of it fixes any problems. ## Bug seriousness - How annoying it is: Annoying enough as to be unusable - How often does it happen: Always - How many people does it affect: Anyone who is logged in using Akkoma backend and Pleroma frontend - Is there a workaround for it: If [this](https://git.froth.zone/sam/pleroma-fe/commit/b711dc1151f2e6250d872281539c8fa2e36a2dbe) counts, otherwise, no. original issue by @SamTherapy
Author
Owner

I don't know why but backend only throws error SOMETIMES. I can't reproduce it in either setup, even supplying completely invalid notification type works. I however KNOW that this happens - we had "test" leftover in code that suddenly broke things.

I don't know why but backend only throws error SOMETIMES. I can't reproduce it in either setup, even supplying completely invalid notification type works. I however KNOW that this happens - we had "test" leftover in code that suddenly broke things.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
pleroma/pleroma-fe#1375
No description provided.