First off thanks for this awesome library we love it!
We've run into an issue when our access token is expired and we attempt to start a hub.
The attempt to start a connection returns an error and dispatches the @ngrx/signalr/error with a payload that includes:
errror: { statusCode: 401 }
This is all as expected thus far. But we then take actions to refresh our access token and make it available to through the hub Options and dispatch the @ngrx/signalr/startHub which results in the following actions being dispatch @ngrx/signalr/error which is the exact same as the previous error action dispatched including the 401 code, this is followed by a @ngrx/signalr/connected action.
The hub is connected to successfully but the extra error action is a bug and causes us further problems. Please see related PR for a proposed solution that seems to have fixed it for us.
First off thanks for this awesome library we love it!
We've run into an issue when our access token is expired and we attempt to start a hub.
The attempt to start a connection returns an error and dispatches the
@ngrx/signalr/error
with a payload that includes:errror: { statusCode: 401 }
This is all as expected thus far. But we then take actions to refresh our access token and make it available to through the hub Options and dispatch the@ngrx/signalr/startHub
which results in the following actions being dispatch@ngrx/signalr/error
which is the exact same as the previous error action dispatched including the 401 code, this is followed by a@ngrx/signalr/connected
action.The hub is connected to successfully but the extra error action is a bug and causes us further problems. Please see related PR for a proposed solution that seems to have fixed it for us.