Slash commands with auto-complete returning the `name` and not the `value` of the option selected

[vkuts]

Description

For only some select Discord users, our bot is consistently getting name and not value for selected auto-complete params for all of our slash commands. This seems like a new issue we've not seen with our bot before (first noticed by us Feb 18th). Majority of our users don't seem to be affected, but those who are affected are experiencing the issue on all Discord clients they tried using (Chrome, Mac app, etc). We're suspecting some experimental Discord feature/version having been pushed to a fraction of the user base only?

Our issue sounds a bit like #4467, but we don't think that a tailing whitespace is needed to reproduce.

Have to add that this is a pretty gross issue for us to have to work around, and it's making our own app look buggy and unreliable 😢 would appreciate a swift response for this one.

Steps to Reproduce

• Add a slash command to your bot with auto-complete params.
• Invoke the command and serve some results to the client (eg. interaction.respond([ { "name": "Design Guild", "value": "WDQ3NbpugZ" }, { "name": "Writters Guild", "value":"8fmtsruwrM" }, { "name": "Legal Guild", "value": "VgZGmx71NE" } ]))
• Have the user select any of the provided options
• Observe in bot that the selected option resolves as the name of the option and not value

Expected Behavior

Slash commands with auto-complete yield the value of the option instead name

Current Behavior

name is returned instead of value

Screenshots/Videos

No response

Client and System Information

discord.js@npm:13.3.1 for bot implementation. Latest Chrome and Mac Discord apps on the client side.

One of our own team members was experiencing this issue consistently with all of their Discord clients, and we could provide their discordId via a DM if that helps.

[yonilerner]

@vkuts Thanks for the report!
Couple questions:

• Could you also share the payload you're using to create the slash command?
• Are those example autocomplete responses very similar to what your bot is sending when encountering this error? If not, could we see real examples?

[yonilerner]

Oh also, what version of the app are you on?

[vkuts]

Hey, @yonilerner thanks for a prompt reply. We deploy several commands with auto-complete. Here's an example of the payload for one of them:

{
        "type": 2,
        "name": "attest",
        "description": "Create a Verifiable Credential to attest to your Sobol contributions.",
        "options": [
          {
            "type": 1,
            "name": "membership",
            "description": "Attest Discord roles that are mapped to Sobol Team Members",
            "options": [
              {
                "type": 3,
                "name": "team",
                "description": "Select a role to attest.",
                "required": true,
                "autocomplete": true
              }
            ]
          }
        ]
      },

Yes, the auto-complete response example I provided should be representative of the content we serve up (but I may have shortened it for brevity). Here's a more exact example taken from our logs:
[{ "name": "Design Guild", "value": "WDQ3NbpugZ" }, { "name": "Memelord Guild", "value": "EMiDnLRJJf" }, { "name": "WAGMI Podcast", "value": "ufNGO4J8s1" }, { "name": "Meme-a-thon", "value": "49QrwyGLu5" }]

One of the users that experienced the issue was likely using the Mac app version 0.0.264 (0.0.264) at the time (Feb 17-18). He also tried the web app version on Brave (Version 1.35.100 Chromium: 98.0.4758.87 (Official Build) (arm64))
Worth noting that this same user is unable to reproduce the issue anymore this week, and nothing has changed on our end. His Mac app version is now 0.0.265 if that helps. We're having a hard time making sense of what we're seeing and we have no idea how many other users are still affected.

[yonilerner]

@vkuts More useful than that app version is actually the web bundle of the app. When you open settings in the desktop app for example, you can see:

For context, the "Canary 115873 (da9ef5e)" part means "web build #115873 for commit hash da9ef5e", and that web build is more related to this functionality.

Anyway, the reason this might not be reproducible anymore for your issue is that we actually fixed a very similar issue last week on Friday, see: #4536

It may be that your issue is already solved, and at this time we are not able to reproduce the issue you describe. Please let me know if you do keep seeing it after updating, as we may need to launch a new investigation

[vkuts]

Ok, sweet! If the fix went out sometime late on Fri, that would match our timeline. Can we expect that the issue is completely gone for the web version of Discord app?
We'll advise any of our users experiencing the issue to update their desktop app versions.
Thanks for the swift fix on this issue 🙏 I'll reopen or create another ticket if we find new ways to reproduce.

[yonilerner]

Yup!

[GitSparTV]

This issue still exist on Canary 116506 (5e71dd7) OS X 10.15.7 64-Bit.

Should I create a new issue or report here?

[yonilerner]

@GitSparTV Can you create a new issue and tag me, and provide a command definition, a payload thats failing, and any other steps to reproduce?