horizon.authEndpoint('github').subscribe returns "Unexpected token <"

[jakobrosenberg]

horizon.authEndpoint('github').subscribe(endpoint => {})
e {isUnsubscribed: false, syncErrorValue: null, syncErrorThrown: false, syncErrorThrowable: false, isStopped: false…}
subscribeToResult.js:41 Uncaught SyntaxError: Unexpected token <

Facebook returns the same error.

Client served from server v1.0.2

[deontologician]

This is probably an issue with error reporting. @jakobrosenberg Which endpoints do you have configured in your config.toml?

[jakobrosenberg]

Just Facebook and Github. Added Github to see if the error was specific to Facebook.

Error persists in 1.0.3.

[Mike-neti]

same here

[poznyakovskiy]

Same for google. The function passed to .subscribe is also never entered.

[deontologician]

I would guess it's getting an error status code which is failing the observable, but the error handling code probably tries to deserialize from json which won't work if you don't receive json back

[poznyakovskiy]

@deontologician Yes, it's response.json() within fetchJSON(url) that triggers this error.

[jordandenison]

try running this inside the horizon.onReady callback

[poznyakovskiy]

@jordandenison If I understand correctly, horizon.onReady would only be triggered after a connection has been established. However, attempting to establish a connection with Horizon.connect() returns the error message "Attempting to authenticate with a token, but no token is present".

[jordandenison]

yeah that was my understanding as well, but it seemed to fix the issue - now I am on the same boat as you : ) "Attempting to authenticate with a token, but no token is present" - haven't had a chance to look into this much yet though (can't specify horizon server host in configure for now so leaving auth for now as I'm serving statics from another server)

[deontologician]

authEndpoint uses xhr/fetch under the hood, so it shouldn't have anything to do with the main horizon connection (which onReady is linked to).

[jordandenison]

yeah, so the error in my case is likely incorrect horizon host since the assets aren't served from it - strange that the error message changes when run inside onReady though (likely the Attempting to authenticate raises the first uncaught)