Entitlements missing from `INTERACTION_CREATE` payloads

[Misha-133]

Description

According to the documentation, one time purchase entitlements should be included with the INTERACTION_CREATE payload.

We had at least 3 users report this issue in our lib's support server - real purchases of SKUs were missing from payloads, while the could be successfully fetched via a REST call; I managed to reproduce this by purchasing SKUs in app test mode.

This issue may be related to #7038, but that one claims to be fixed.

Steps to Reproduce

• Purchase a durable SKU in app test mode
• call GET /applications/{id}/entitlements?user_id={userId}
  • the entitlements are actually returned in the response
• The interaction payload will be missing the entitlements

[INTERACTION_CREATE] : 
{
  "version": 1,
  "type": 2,
  "token": "",
  ...
  "entitlements": [],
  "entitlement_sku_ids": [],
  ...

Expected Behavior

Entitlements actually included with the INTERACTION_CREATE payload

Current Behavior

Entitlements missing from the INTERACTION_CREATE payload

Screenshots/Videos

e is an interaction object, parsed from the json payload.
GetEntitlementsAsync calls the List Entitlements endpoint.

the interaction payload has 0 entitlements. rest call returns 2.

Client and System Information

API v10 / Discord.NET

[ithinkimcats]

I'm having the same issue (JDA 5.2.2). Seeing as this can involve real purchases, and bots are required to use Discord's monetization API, I feel like this is a pretty significant bug.

[Lulalaby]

Same here, neither v9 nor v10 gives us any information about OTP entitlements

[ithinkimcats]

This remains an issue over a month later, without any acknowledgement from Discord.

[ithinkimcats]

This remains an issue over a month later, without any acknowledgement from Discord.

I have just tested this again, and it remains an issue two months later. This is an inconsistent behavior for a feature that involves real purchases.

[ithinkimcats]

I have just tested this again, and it remains an issue three months later, with no acknowledgement from Discord. This is an inconsistent behavior for a feature that involves real purchases.

JDA 5.3.0
System.out.println("Interaction Event: " + event.getEntitlements().size());
System.out.println("API Request: " + (int) event.getJDA().retrieveEntitlements().user(event.getUser()).stream().count());
Interaction Event: 0
API Request: 5