We are using the new
resolveStreamUrl feature in
@servicestack/client TypeScript client.
However it looks like our heartbeat events are failing.
Checking the source, it looks like
heartbeatUrl is never resolved through
resolveStreamUrl, which looks like the culprit.
Does that sound correct or are we doing something wrong?
Maybe this is by design and we should be also changing the heartbeat URL directly when setting up the client?
resolveStreamUrl is only for resolving the /event-stream url. What error are you receiving from the heartbeat responses?
We can't seem to reproduce this anymore on our end. Thanks for the help anyway.