Saltar al contenido principal

Common Errors

This document outlines frequent console errors encountered in Bot Maker For Discord (which uses Oceanic.js) and provides their solutions.

Error: Unhandled Rejection DiscordRESTError: Invalid Form Body​

When attempting to register application commands (e.g., using bulkEditGlobalCommands), you may encounter the following error:

Unhandled Rejection DiscordRESTError: Invalid Form Body on PUT /api/v10/applications/.../commands 
0.options.0: Field "type" is required to determine the model type. 
1.options.0: Field "type" is required to determine the model type. ...

Solution​

  1. Verify that all options for your commands include a type field.
  2. Check your command registration code and ensure it adheres to the Discord API's application command structure.

Reason​

This error occurs because the Discord API requires a type field for all command options to specify the option's data type (e.g., string, integer, boolean, etc.). The missing type field causes the request body to be invalid.

Error: Error [TOKEN_INVALID]: An invalid token was provided​

When initializing the bot, you may encounter the following error:

Error [TOKEN_INVALID]: An invalid token was provided.

Solution​

  1. Double-check your bot token in the .env file or configuration file.
  2. Regenerate the token from the Discord Developer Portal if you suspect it is compromised or incorrect.
  3. Ensure that your bot is connecting to the correct gateway.

Reason​

This error occurs when the bot token used for authentication is invalid. It could be due to a typo, expired token, or an attempt to use the wrong token (e.g., client secret instead of bot token).

Error: Unhandled Rejection DiscordRESTError: 403 Forbidden​

When making API calls (e.g., sending messages or updating permissions), you may encounter:

Unhandled Rejection DiscordRESTError: 403 Forbidden

Solution​

  1. Check if the bot has the required permissions in the server.
  2. Ensure the bot's role is above the roles it is trying to modify.
  3. Verify the bot's OAuth2 scopes and granted permissions in the Discord Developer Portal.

Reason​

This error indicates that the bot is attempting an action it does not have permission to perform. Common causes include insufficient permissions in the bot's role or missing OAuth2 scopes during authorization.

Error: RangeError [BITFIELD_INVALID]: Invalid bitfield flag or number​

When setting permissions or intents, you may encounter:

RangeError [BITFIELD_INVALID]: Invalid bitfield flag or number.

Solution​

  1. Verify that the permissions or intents you are using are valid. Refer to the Discord API documentation for a list of valid flags.
  2. Avoid using deprecated or removed permissions.

Reason​

This error occurs when an invalid permission or intent flag is used. Oceanic.js validates these flags against a predefined list, and any mismatch causes this error.

Error: Unhandled Rejection DiscordRESTError: 400 Bad Request​

When sending a request to the Discord API, you may encounter:

Unhandled Rejection DiscordRESTError: 400 Bad Request

Solution​

  1. Inspect the request payload to ensure all required fields are included and valid.
  2. Use a JSON validator to verify the structure of the request body.
  3. Cross-reference the payload with the Discord API documentation for the specific endpoint you are using.

Reason​

This error occurs when the API receives a request with missing, invalid, or incorrectly formatted fields. Common causes include:

  • Missing required fields (e.g., name or description for commands).
  • Providing fields with the wrong data types (e.g., string instead of integer).

Error: TypeError: Cannot read properties of undefined (reading '...')​

When accessing an object property, you may encounter:

TypeError: Cannot read properties of undefined (reading '...').

Solution​

  1. Add null checks before accessing properties of objects.
  2. Ensure the object you are accessing is properly initialized.
  3. Log the variable to confirm it contains the expected data.

Reason​

This error occurs when trying to access a property of undefined or null. It usually happens when the expected data from the Discord API or another source is missing or improperly handled.

Error: Error: Cannot find module 'oceanic.js'​

When starting the bot, you may encounter:

Error: Cannot find module 'oceanic.js'

Solution​

  1. Install the library using npm or yarn:

    npm install oceanic.js

    or

    yarn add oceanic.js

  2. Verify that node_modules is not excluded or missing in your project directory.

  3. Confirm the import path in your code matches the library.

Reason​

This error occurs when the required dependency is not installed or the import path is incorrect. It may also happen if the node_modules directory is missing (e.g., after transferring the project without running npm install).

Error: UnhandledPromiseRejectionWarning​

When using async functions, you may encounter:

UnhandledPromiseRejectionWarning: Some Error Message

Solution​

  1. Always handle promises with .catch or try/catch.

Example with .catch:

someAsyncFunction().catch(err => console.error(err));

Example with try/catch:

try {
    await someAsyncFunction();
} catch (err) {
    console.error(err);
}
  1. Add an unhandledRejection handler in your bot for debugging:
process.on("unhandledRejection", (reason, promise) => {
    console.error("Unhandled Rejection:", reason);
});

Reason​

This warning appears when a promise is rejected but no error handler is attached. Unhandled rejections may crash your application in future versions of Node.js.

Error: Error: Request entity too large​

When uploading a large file or payload, you may encounter:

Error: Request entity too large

Solution​

  1. Reduce the size of the file or data you are uploading.
  2. If uploading attachments, ensure the total size does not exceed Discord's limit (8MB for regular bots, 100MB for Nitro bots).
  3. Use Buffer or streaming techniques for large data uploads.

Reason​

Discord imposes size limits on API requests and attachments. This error occurs when the payload exceeds these limits.

Here’s a detailed section for the provided error:

Error: Unhandled Rejection TypeError: Cannot read properties of undefined (reading 'createMessage')​

When attempting to send a message to a channel, you may encounter the following error:

Unhandled Rejection TypeError: Cannot read properties of undefined (reading 'createMessage') 
    at Object.getChannel (D:\Steam\steamapps\common\Bot Maker For Discord\bot.js:767:28) 
    at D:\Steam\steamapps\common\Bot Maker For Discord\AppData\Actions\sendmessage.js:1433:38 
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Solution​

  1. Verify that the channel ID being used is valid and corresponds to an existing channel in your server.
  2. Ensure the bot is in the server where the channel exists and has sufficient permissions to access the channel.

Reason​

This error occurs because the getChannel method is returning undefined or a non-channel object, meaning the bot cannot find the specified channel. Common causes include:

  • The provided channel ID is invalid or missing.
  • The bot does not have access to the channel due to insufficient permissions or being removed from the server.
  • The channel was deleted or does not exist.

Here’s a detailed section for the provided error:

Error: Unhandled Rejection DiscordRESTError: Unknown Message​

When attempting to edit a message, you may encounter the following error:

Unhandled Rejection DiscordRESTError: Unknown Message on PATCH /api/v10/channels/1199458338509959209/messages/1284589399748903094
    at RequestHandler.request (/home/container/node_modules/oceanic.js/dist/lib/rest/RequestHandler.js:96:15)
    at RequestHandler.authRequest (/home/container/node_modules/oceanic.js/dist/lib/rest/RequestHandler.js:81:21)
    at RESTManager.authRequest (/home/container/node_modules/oceanic.js/dist/lib/rest/RESTManager.js:47:29)
    at Channels.editMessage (/home/container/node_modules/oceanic.js/dist/lib/routes/Channels.js:395:30)
    at Message.edit (/home/container/node_modules/oceanic.js/dist/lib/structures/Message.js:392:42)
    at /home/container/AppData/Actions/sendmessage.js:1466:25
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 10008
}

Solution​

  1. Verify that the message ID you are trying to edit exists.
  2. Turn o nreply to interaction
  3. Ensure the bot has permission to view the channel and the message.
  4. Check if the message has been deleted.

Reason​

This error occurs when the bot attempts to edit a message that no longer exists or is inaccessible. Common causes include:

  • The message has been deleted.
  • The message ID provided is invalid or belongs to a different channel.
  • The bot lacks permissions to view the message's channel or edit the message.

Error: npm ERR! code ENOENT​

When attempting to install a package using npm, you may encounter the following error:

npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno -4058
npm ERR! enoent An unknown git error occurred
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in: C:\...

Solution​

  1. Ensure Git is installed:

    • Download and install Git from git-scm.com.
    • During installation, make sure to add Git to your system's PATH.

  2. Verify Git installation:

    • Run the following command in your terminal to confirm Git is installed: 
      git --version
    • If this command fails, check your PATH settings and reinstall Git if necessary.

  3. Fix npm configuration (if needed):

    • Check npm's configuration for the git binary: 
      npm config get git
    • If the output is empty or incorrect, set the correct path: 
      npm config set git "C:\\Program Files\\Git\\cmd\\git.exe"
      Replace the path with the location of your Git installation.

  4. Reinstall the package:

    • Once Git is properly installed and configured, retry the command: 
      npm install

Reason​

This error occurs when npm attempts to use Git as part of the package installation process, but it cannot find the Git executable. Common causes include:

  • Git is not installed on your system.
  • Git is installed but not added to the system's PATH.
  • npm is configured with an invalid or nonexistent Git path.