Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/characters/{character_id}/notifications/ - unknown notification type (6013) #1392

Open
5 of 6 tasks
soratidus999 opened this issue Aug 31, 2024 · 0 comments
Open
5 of 6 tasks

Comments

@soratidus999
Copy link

soratidus999 commented Aug 31, 2024

Bug

Regression of #1380 which is a regression of #1368

A notification returned from /characters/{character_id}/notifications/ is not returning it's type, instead they are returning an "unknown notification type (6013)" breaking validation of this response data. Interfering with the normal usage of this endpoint.

This is occuring because the respective notification types have not been added to eve-glue. These notifications should not neccessarily be in eve glue because they are part of the 6xxx ephemeral range and are supposed to be client only.

I am fairly certain this is Daily Reward Auto-Redeemed, after looking in the notifications test menu manually. But i do not have the Class.

Request

GET http://characters/character_id/notifications/?datasource=tranquility

Response

Status Code

200

Headers

I didnt record headers this time around

Body

...
  {
    "notification_id": 1234567890,
    "sender_id": 1234567890,
    "sender_type": "character",
    "text": "station_id: 1234567890 type_id:12345",
    "timestamp": "2024-08-31Txx:yy:00Z",
    "type": "unknown notification type (6013)"
  },
...

Expected

200

...
  {
    "notification_id": 1234567890,
    "sender_id": 1234567890,
    "sender_type": "character",
    "text": "station_id: 1234567890 type_id:12345",
    "timestamp": "2024-08-31Txx:yy:00Z",
    "type": "DailyRewardAutoRedeemed" ?? Guessing at the Class ??
  },
...

Checklist

Check all boxes that apply to this issue:

  • Bug description is provided
  • Request path is provided
  • Response status code is provided
  • Response headers are provided
  • Response body is provided
  • Expected response is provided
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants