subscribeV5 unsubscribeV5 promise not resolved

[pool683]

the following code breaks something

import { WebsocketClient } from 'bybit-api';

const wsClient = new WebsocketClient({
  market: 'v5',
});

wsClient.on('update', (data) => {
  wsClient.unsubscribeV5('tickers.' + data.data.symbol, 'linear');
  console.log("unsubscribeV5");
});

wsClient.on('error', (err) => {
  console.error(err);
});
   
console.log("before subscribeV5");
await wsClient.subscribeV5('tickers.' + 'BTCUSDT', 'linear');
console.log("never reach here!!!"); // <--- HERE

output

before subscribeV5
[
  'Starting public only websocket client.',
  { category: 'bybit-ws', wsKey: 'v5LinearPublic' }
]
[
  'Websocket connected',
  {
    category: 'bybit-ws',
    wsKey: 'v5LinearPublic',
    testnet: false,
    market: 'v5'
  }
]
[
  'Subscribing to topics',
  {
    category: 'bybit-ws',
    wsKey: 'v5LinearPublic',
    topics: [ 'tickers.BTCUSDT' ]
  }
]
unsubscribeV5
unsubscribeV5
unsubscribeV5
unsubscribeV5
unsubscribeV5
unsubscribeV5

[tiagosiebler]

Apologies for the late response. I'm currently working through an upgraded WebSocket Client, as part of the addition of the WS API (#344). Once the upgrades are complete, I'll make sure this workflow works as expected with that release. You can follow (and comment on) the incoming changes in #398. I'll try to keep breaking changes minimal, so take anything currently in the PR with a grain of salt as that may still be subject to change.

[tiagosiebler]

Help test the latest generation of the Bybit SDK, currently in public beta, before the major release! There should also be a significant improvement to this behaviour (details in the PR, with some limitations).

More info here in the open PR:
#398 (comment)

[tiagosiebler]

During further testing, I'm seeing more circumstances where this has intended errors (unhandled promise rejection) if you weren't expecting to use this. So I've decided to disable this feature by default. The majority won't be using this as far as I can tell, so unexpected promise rejections will be avoided by just keeping it disabled by default. It will still work, but you need to actively enable it using the promiseSubscribeRequests setting in the websocket client. This is live as of v4.0.0-beta.6.