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

JSON at position 20911 #143

Closed
naill975763 opened this issue Jan 23, 2024 · 2 comments
Closed

JSON at position 20911 #143

naill975763 opened this issue Jan 23, 2024 · 2 comments

Comments

@naill975763
Copy link

Type: Error

Title:

Internal error occurred!

Content:

{}

SyntaxError: Bad escaped character in JSON at position 20911 (line 1 column 20912)
at JSON.parse ()
at C:\Users\Admin\Downloads\ezytdl-win32\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 ChildProcess._handle.onexit (node:internal/child_process:302:5)

(no stack)

Stack:

- at module.exports (C:\Users\Admin\Downloads\ezytdl-win32\resources\app.asar\core\sendNotification.js:24:34)
- at module.exports (C:\Users\Admin\Downloads\ezytdl-win32\resources\app.asar\util\errorHandler.js:8:48)
- at process.<anonymous> (C:\Users\Admin\Downloads\ezytdl-win32\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.


@naill975763
Copy link
Author

Fixed the problem by installing the old version https://github.com/sylviiu/ytdlp-pybridge/releases

@sylviiu
Copy link
Owner

sylviiu commented Mar 4, 2024

Glad that worked. I'm not at all sure why it's happening in the first place; it's never appeared on my system for any version, but it's appeared for some of my friends using other versions. I don't know where to start troubleshooting.

Tracking this issue @ #121

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