You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everybody, I was building my Telegram Bot when I faced in the following problem.
I was using local Telegram API Server because I needed to upload large file, the upload seems to work fine, but the large size of the file and obviously the amount of time needed to upload it, all this made the request (sendDocument method) return an exception due to idleTimeout (Sockets wait too much for file fully upload).
How know I manage it
So now the only way for me to see if the file has been uploaded, it is to just wait the file appear in the chat.
How I would be able to manage it
I would like to have some sort of progress bar or callback query with the percentage of file sent, or it could be just fine a response from the server when a file has been uploaded.
Thanks
If anyone know how to help me I would be really thankfully,
The text was updated successfully, but these errors were encountered:
Upload documents progress bar / status code
The issue
Hi everybody, I was building my Telegram Bot when I faced in the following problem.
I was using local Telegram API Server because I needed to upload large file, the upload seems to work fine, but the large size of the file and obviously the amount of time needed to upload it, all this made the request (sendDocument method) return an exception due to idleTimeout (Sockets wait too much for file fully upload).
How know I manage it
So now the only way for me to see if the file has been uploaded, it is to just wait the file appear in the chat.
How I would be able to manage it
I would like to have some sort of progress bar or callback query with the percentage of file sent, or it could be just fine a response from the server when a file has been uploaded.
Thanks
If anyone know how to help me I would be really thankfully,
The text was updated successfully, but these errors were encountered: