title: 429: Too Many Requests: retry after 18053 only on telegram.sendContact
body: <p>I've got an issue with Too many requests only when I try to send a contact via telegram.sendContact. But when I am sending a message via telegram.sendMessage everything is fine.</p>
  
  <p>I think I may have done some loop somewhere haven't close requests or something which are still pending or something or it's an issue with the framework.</p>
  
  <p>I already tried to put <code>ctx.answerCb</code> everywhere where I 've found but it did not help.</p>
  
  <p><strong>EDIT:</strong>
  I already tried to start a new project with only this line and I get the error anyway.
  There must be some updates or something that caused that weird behaviour because before it seemed to work fine for me. I didn't notice any issues with Contacts</p>
  
  <pre><code>bot.hears(
      /(Contacts)|(Контакты)|(Контакти)/i,
      //@ts-ignore
      getUserInfo,
      updateUserActivity,
      async (ctx: ITelegramContext) =&gt; {
        // @ts-ignore
        ctx.telegram.sendContact(
          //@ts-ignore
          **********,
          +***********,
          "name"
        )
      }
    );
  </code></pre>
  
  <pre><code>(node:8620) UnhandledPromiseRejectionWarning: Error: 429: Too Many Requests: retry after 17496
      at C:\Users\Валерий\Documents\Projects\TelegramBOT\node_modules\telegraf\core\network\client.js:281:17
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
  (node:8620) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
  (node:8620) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  </code></pre>