-
Notifications
You must be signed in to change notification settings - Fork 65
Unexpected token { in JSON at position XYZ #82
Comments
Hi. Sorry you're having this problem - it's not one we've seen so far, and I'd like to find out what's going on. The first thing I'd like to know is what version of the Node SDK you're running; that will help us know exactly which code path corresponds to I can also try to reproduce the problem over here if I know what account and project you're using. You can either email me at eli@launchdarkly.com, or create a support ticket and ask them to pass the information along to me. Two other things that might help to narrow this down:
best, |
I forgot to say, it'd also be helpful to know the approximate date/time range when these messages occurred (not every one, just how long ago you first noticed them and whether they are still going on), in case it's correlated with any known service outage in the past. |
Hi @eli-darkly, thank you for the really quick answer 🙏
3.2.1
Not sure, but for some users this error has occured more than 1000 times in the last 2 weeks, so I assume that's happening throughout the lifetime of the clients.
I'm connecting directly to LaunchDarkly
The first time the error appeared on our side was on Feb 13th, and it's still ongoing (we have this error reported between 5 and 15 times per minutes from several days now).
I'm forwarding our project information to you by email. |
OK, I'm now running a copy of the Node client, connecting with your credentials (but not doing any flag evaluations, so it won't trigger any analytics events) to see if I can reproduce the JSON error. No luck at present, though - it seems to be working fine. Two thoughts I have so far are:
|
I assume that adding a |
I've opened a support ticket for continued investigation - you should have received a link to it via email. |
In the end, after adding the debugging information, it was the following error that was triggered a lot: |
remove problematic dependency used by EventSource
I'm going to close this issue as it has been inactive for over a year. However, before I do so, I wanted to mention that in the time since this issue was filed, we released a first-class Electron SDK. If you're currently using our Node Server SDK in an Electron application, we recommend considering switching over to it. |
We have a lot of stacktraces like this one on an Electron project:
The position of the unexpected token (here 499) varies from client to client, but the error remains the same.
Any clue on what could go wrong, or how I can gather more details ?
The text was updated successfully, but these errors were encountered: