We're just adopting growthbook-golang v0.1.4, but ...
# give-feedback
b
We're just adopting growthbook-golang v0.1.4, but it seems to be exiting with an "SSE error", but it's not actually telling us what the error is 🤔
cc @alert-dream-63361
We're just using the default DevLogger for now, as it seems positive for it to quit the app if there's a serious error
a
Let me take a look...
b
Copy code
[WARNING] Unknown key in JSON data: FeatureAPIResponse status
[INFO] Connecting to SSE stream: <https://cdn.growthbook.io>||sdk-82dX3Yk8FKvatDm
[ERROR] SSE error: <https://cdn.growthbook.io>||sdk-82dX3Yk8FKvatDm
Container called exit(1).
Copy code
if err != nil {
	logErrorf("SSE error: %s", key)
}
If it was to provide the error, that might help, but seems like it might just be something wrong with the deserialization
a
Yeah, I assume it's just deserialization. Let me get set up to replicate it, then I'll have a look.
b
Feel free to use our SDK API key if it'd be handy - there's nothing sensitive in our features
a
I have one for testing that I can use, and my test program understands the features that will return, which will remove one source of confusion. If that works OK, I might ask for your key so I can see if there's a problem deserializing the feature responses for your stuff.
b
The key is in the error message above 🙂
a
Oh. So it is. Maybe we should obfuscate that... I think I might have done that in the development branch already.
b
Well not really a concern from our perspective, maybe others are a bit more precious about it
a
OK, I can reproduce it. I'll figure out what's going on.
Right, I've figured it out. Just a fix that hadn't been carried over from the development branch. Let me tidy up a little and I'll make a new release.
OK, should be fixed now in v0.1.5.
b
💯
will give it a try, ty
Sorry I didn't check back in, but that all worked great 🙂 thanks!
👍 1