Skip to content

Akkoma Backend: Notifications Cause 400 Bad Request because Status notification type is not Supported

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

  1. Log in
  2. Notifications fail to load, 400 Bad Request in log
  3. 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.