-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disconnecting after one or two hours #83
Comments
Hello. Looks like you use preview version of |
Is this code still needed or you have updated the library where it keeps alive without the code? |
This code is still needed. It should be removed in ‘0.6.0’.
…On 15 Jan 2022, 12:03 +0100, derodevil ***@***.***>, wrote:
Is this code still needed or you have update the library where it keeps alive without the code? IDisposable KeepAlive(TelegramClient tg) =>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
I use the latest version 0.5.1 started at 17:45 and I let it idle for more than two hours. At 21:00 I send a text message and it couldn't receive any massage. I don't think the latest version keep it alive. My code looks like this:
|
Hm. Can you subscribe to internal exceptions? Should look like |
I had been running from 11pm to 7am and no exception was caught. I've checked the log file since I put the error message to a file and nothing there. [EDIT] |
Yet another reason to move |
Well, I'm waiting for the next release |
Do you have any updates for this issue? |
Not yet. I had started the refactoring and abandoned it. I do not have time for Telega now and the next few months. I can review and merge a PR however. |
Hi.. I'm still waiting 💯 |
The above snippet doesn't work. My winforms application gets disconnected after 1 to 2 hours inactivity.
[EDIT]
I try my own custom ping every ten seconds. After approximately an hour it generates error as follows:
The text was updated successfully, but these errors were encountered: