question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Notification messages fetch error SyntaxError: Unexpected token T in JSON at position 0

See original GitHub issue
> hyper install hyper-dracula
Disabling Chromium GPU blacklist
running in prod mode
electron will open file:///usr/lib/hyper/resources/app.asar/index.html
Setting Hyper as default client for ssh:// protocol
Checking for notification messages
Notification messages fetch error SyntaxError: Unexpected token T in JSON at position 0
    at JSON.parse (<anonymous>)
    at consumeBody.call.then.buffer (/usr/lib/hyper/resources/app.asar/node_modules/electron-fetch/lib/index.js:240:55)
    at process._tickCallback (internal/process/next_tick.js:68:7)

OS: Manjaro Linux Installation: pamac build hyper I have seen other issues, but these seem to be because of Windows WSL limitations where I’m using Konsole on Manjaro KDE.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:15
  • Comments:21

github_iconTop GitHub Comments

7reactions
allywilsoncommented, Jul 23, 2020

Same issue here. CentOS 8 AppImage 3.0.2 (stable).


$ hyper install hyper-dracula
Disabling Chromium GPU blacklist
running in prod mode
electron will open file:///tmp/.mount_hyper-ayjE5l/resources/app.asar/index.html
Setting Hyper as default client for ssh:// protocol
Checking for notification messages
Notification messages fetch error SyntaxError: Unexpected token T in JSON at position 0
    at JSON.parse (<anonymous>)
    at consumeBody.call.then.buffer (/tmp/.mount_hyper-ayjE5l/resources/app.asar/node_modules/electron-fetch/lib/index.js:240:55)
    at process._tickCallback (internal/process/next_tick.js:68:7)

It also opens a new hyper window, which doesn’t do anything, but if I close it then the original window finally goes back to prompt, so must be expecting something from it…

2reactions
gpontycommented, Nov 23, 2020

Same here, manjaro.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unexpected token < in JSON at position 0 - Dave Ceddia
... (SyntaxError): Unexpected token < in JSON at position 0. You made an HTTP request, probably with Fetch, and it blew up with...
Read more >
How to Fix SyntaxError: Unexpected token < in JSON at ...
In this case the error is thrown when response.json() tries to run and fails to parse the data from the server as JSON....
Read more >
Unexpected token u in JSON at position 0 Error in JS
The "Unexpected token u in JSON at position 0" error occurs when we pass an undefined value to the JSON.parse or $.parseJSON methods....
Read more >
How To Fix Unexpected token u in JSON at position 0 - Isotropic
The "Unexpected token u in JSON at position 0" is a typically Javascript error that will show up in your console log if...
Read more >
Unexpected token in JSON at position 0 - Moodle.org
This usually means that an error has been returned and that's not valid JSON. ... Turn on Debugging and (after reproducing the error)...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found