-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
# There is an error in ModalSubmitInteraction.js #9731
Comments
I cannot reproduce this issue. My code sample is actually simply copied from the version 13 guide. Moreover, this seems to be impossible. This method is referenced in one place only: discord.js/src/structures/ModalSubmitInteraction.js Lines 37 to 45 in cb11c56
The more likely scenario is you are doing something incorrectly or the internal behaviour of discord.js has been edited (especially since this has not changed since implementation and no one has complained). |
ok thanks. But many people in the discord server have this issue. I reinstalled discord v13 and used a new bot with the guide copied and pasted. But I always get the same error |
the textinput was only logged without error when I modified c.custom_id to c.customId |
I have a hard time believing that, considering modal support was added over a year ago, I cannot reproduce this, and this code has been untouched. Care to link these many people in the server? |
From Discord, it was found that the reporter had a third-party package installed which modified the internal behaviour of discord.js resulting in this error (posting for transparency). |
Which package is this bug report for?
discord.js
Issue description
Always get the MODAL_SUBMIT_INTERACTION_FIELD_NOT_FOUND error because of this failure in code:
interaction.fields.getField() never got the custom ID of the field
discord.js/src/structures/ModalSubmitInteraction.js
Line 93 in cb11c56
"c.custom_id" needs to be "c.customId"
Now TextInputComponent() and getField() get the customId again!
Code sample
Versions
[email protected]
Node: v18.15.0
Issue priority
Medium (should be fixed soon)
Which partials do you have configured?
Not applicable
Which gateway intents are you subscribing to?
Not applicable
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered: