Embeds do not show when using webhooks with ephemeral messages

[rxdn]

Description

When using responding to slash commands with an ACK (or ACK with source) and using a webhook with the interaction's token to respond, embeds are ignored by the API if the ephemeral message flag is set. If the flag is not set, embeds work fine.

Steps to Reproduce

POST to https://discord.com/api/v8/webhooks/{bot_id}/{interaction_token} with

{
	"flags": 64,
	"embeds": [{
		"title": "hello",
		"description": "Test"
	}]
}

Expected Behavior

Embeds are not ignored by the API when using ephemeral messages

Current Behavior

The API responds with a HTTP 200 and a valid message object, but with "embeds": []. The message is shown as a blank message by the client, see the next section.

Screenshots/Videos

Client and System Information

N/A, curl can be used to reproduce

[A5rocks]

#2295 (comment) might be relevant here.

[rxdn]

#2295 (comment) might be relevant here.

Don't think so, since the API returns a message object without embeds, it's not just the client not rendering them

[muddyfish]

As far as I'm aware, not being able to use embeds or attachments is intended

[rxdn]

As far as I'm aware, not being able to use embeds or attachments is intended

The docs for InteractionApplicationCommandCallbackData have an embeds field defined. I haven't tested what happens when you respond directly with a ChannelMessage interaction response that contains embeds yet, but I'd assume if they work with them, they'd work with webhooks. I'll test and get back to you on that

[muddyfish]

I meant with ephemeral messages specifically. I remember someone saying they skipped out all the infrastructure that renders embeds/saves attachments and ships the message directly to the client

[rxdn]

I meant with ephemeral messages specifically. I remember someone saying they skipped out all the infrastructure that renders embeds/saves attachments and ships the message directly to the client

Hmm ok, just confirmed same happens when you use the ChannelMessage response. I understand why attachments wouldn't be supported (they aren't documented under the callback data structure, unlike embeds), but since embeds are rendered by the client I don't see why they wouldn't be supported

Nvm, this is the case

[night]

This behavior is working as intended at present, as embeds go through a separate workflow ephemeral messages do not have the capability to (these are messages which are not persisted). You can voice your support for this at #2318