You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Going forward: Please provide your code and reproducible (minimal) code sample as well as detailed instruction steps that are reproducible for yourself, so we can try and reproduce it under the same conditions.
Which location has the wrong token? I tried altering either as well as both locations where a token is usually provided and received the expected Error [TOKEN_INVALID]: An invalid token was provided. or (if i completely mess my code up Error [TOKEN_MISSING]: Request to use token, but token was unavailable to the client.)
After much more digging (thanks space) we found the issue
With an invalid token this throws the response when we try to fetch the recommended amount of shards to spawn (hence why i could not reproduce this earlier, as i provide the shard count manually for testing purposes)
Further details:
Returns an error:
(node:10640) UnhandledPromiseRejectionWarning: #
Running base index.js (my sharder is in sharder.js) returns invalid token error.
discord.js version: 12.3.1
Node.js version: 12.18.2
Operating system: Windows
Priority this issue should have – please be realistic and elaborate if possible: No priority
I have also tested the issue on latest master, commit hash:
The text was updated successfully, but these errors were encountered: