Error starting today - <rejected> TypeError: Cannot read properties of null (reading 'all') #1440
Closed
Chrisharrison1328
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Has anyone been able to reliably/consistently get the bot working again? I have multiple instances and some will run and many others will not I can't seem to find a commonality between them. I know a bug was submitted under #1439 but hoping someone has a fix they were able to implement without waiting for the whole package to be udpated or reviewed to determine the issue.
I was originally on [discord.js-selfbot-v13@2.15.1] and was receiving a "reading 'all'" error.
I updated ot [discord.js-selfbot-v13@3.4.6] and started receiving a TypeError: terminated error.
as mentioned a couple other instances are running and seem fine. but most have stopped. Many stopped after restarting the bot so not sure if there has been anyone able to work around this.
Initial Error
TypeError: Cannot read properties of null (reading 'all')
new Error after updating
Error Fetching Message : TypeError: terminated
Initial FullError
4|TestBot | TypeError: Cannot read properties of null (reading 'all') 4|TestBot | at ClientUserSettingManager._patch (/home/ubuntu/TestBot/D2D/node_modules/discord.js-selfbot-v13/src/managers/ClientUserSettingManager.js:201:39) 4|TestBot | at module.exports [as READY] (/home/ubuntu/TestBot/D2D/node_modules/discord.js-selfbot-v13/src/client/websocket/handlers/READY.js:112:19) 4|TestBot | at WebSocketManager.handlePacket (/home/ubuntu/TestBot/D2D/node_modules/discord.js-selfbot-v13/src/client/websocket/WebSocketManager.js:366:31) 4|TestBot | at WebSocketShard.onPacket (/home/ubuntu/TestBot/D2D/node_modules/discord.js-selfbot-v13/src/client/websocket/WebSocketShard.js:499:22) 4|TestBot | at WebSocketShard.onMessage (/home/ubuntu/TestBot/D2D/node_modules/discord.js-selfbot-v13/src/client/websocket/WebSocketShard.js:333:10) 4|TestBot | at callListener (/home/ubuntu/TestBot/D2D/node_modules/ws/lib/event-target.js:290:14) 4|TestBot | at WebSocket.onMessage (/home/ubuntu/TestBot/D2D/node_modules/ws/lib/event-target.js:209:9) 4|TestBot | at WebSocket.emit (node:events:513:28) 4|TestBot | at Receiver.receiverOnMessage (/home/ubuntu/TestBot/D2D/node_modules/ws/lib/websocket.js:1220:20) 4|TestBot | at Receiver.emit (node:events:513:28)
Updated Full New Error
4|TestBot | [07:32:42] (-) Error Fetching Message : TypeError: terminated
4|TestBot | at Fetch.onAborted (/home/ubuntu/TestBot/D2D/node_modules/undici/lib/web/fetch/index.js:2046:49)
4|TestBot | at Fetch.emit (node:events:513:28)
4|TestBot | at Fetch.terminate (/home/ubuntu/TestBot/D2D/node_modules/undici/lib/web/fetch/index.js:93:10)
4|TestBot | at /home/ubuntu/TestBot/D2D/node_modules/undici/lib/web/fetch/index.js:511:30
4|TestBot | at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
4|TestBot | [cause]: TypeError [ERR_INVALID_ARG_TYPE]: The "stream" argument must be an instance of Stream. Received an instance of ReadableStream
4|TestBot | at new NodeError (node:internal/errors:400:5)
4|TestBot | at eos (node:internal/streams/end-of-stream:66:11)
4|TestBot | at fetchFinale (/home/ubuntu/TestBot/D2D/node_modules/undici/lib/web/fetch/index.js:1101:5)
4|TestBot | at mainFetch (/home/ubuntu/TestBot/D2D/node_modules/undici/lib/web/fetch/index.js:765:5)
4|TestBot | at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
4|TestBot | code: 'ERR_INVALID_ARG_TYPE'
4|TestBot | }
4|TestBot | }
Beta Was this translation helpful? Give feedback.
All reactions