Skip to content
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

Internal error occurred! after running npm start or ezytdl.exe #126

Closed
nameniok opened this issue Dec 19, 2023 · 1 comment
Closed

Internal error occurred! after running npm start or ezytdl.exe #126

nameniok opened this issue Dec 19, 2023 · 1 comment

Comments

@nameniok
Copy link

nameniok commented Dec 19, 2023

Type: Error

Title:

Internal error occurred!

Content:

{}

SyntaxError: Bad escaped character in JSON at position 21581 (line 1 column 21582)
at JSON.parse ()
at E:\Robienie Stron html css\ezytdl-main\dist\win-unpacked\resources\app.asar\util\currentVersion\pybridge.js:48:40
at ChildProcess.exithandler (node:child_process:422:7)
at ChildProcess.emit (node:events:514:28)
at maybeClose (node:internal/child_process:1091:16)
at Process.onexit (node:internal/child_process:302:5)

(no stack)

Stack:

- at module.exports (E:\Robienie Stron html css\ezytdl-main\dist\win-unpacked\resources\app.asar\core\sendNotification.js:24:34)
- at module.exports (E:\Robienie Stron html css\ezytdl-main\dist\win-unpacked\resources\app.asar\util\errorHandler.js:8:48)
- at process.<anonymous> (E:\Robienie Stron html css\ezytdl-main\dist\win-unpacked\resources\app.asar\index.js:22:125)
- at process.emit (node:events:514:28)
- at emit (node:internal/process/promises:149:20)
- at processPromiseRejections (node:internal/process/promises:294:27)
- at process.processTicksAndRejections (node:internal/process/task_queues:96:32)

Below this line, please describe what caused this error.

After running (npm start or .exe and settings) it's showing up.

@sylviiu
Copy link
Owner

sylviiu commented Dec 20, 2023

Duplicate of #121

@sylviiu sylviiu marked this as a duplicate of #121 Dec 20, 2023
@sylviiu sylviiu closed this as not planned Won't fix, can't repro, duplicate, stale Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants