Skip to content
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

Async web request conflicts with Async telefgram2. #117

Open
miguelfernando55 opened this issue Aug 9, 2023 · 4 comments
Open

Async web request conflicts with Async telefgram2. #117

miguelfernando55 opened this issue Aug 9, 2023 · 4 comments

Comments

@miguelfernando55
Copy link

I am trying to open a webpage using server.on() at the same time using bot asynctelegram2. But the web page does not open. The bot still runs.

@cotestatnt
Copy link
Owner

Can you provide a sketch which can reproduce your issue?
I've just tried to serve a simple web page and it works.

@miguelfernando55
Copy link
Author

Sorry, I cannot. It does not belong to me.
Yes, with only a few lines of code it works. I also did only with a few lines before going further, but for a 40kB html css js it creates a err_invalid_chunked_encoding.
I thought the cause was something related to the quality of the content or chrome but when I comment the lines. myBot.begin and getNewMessages it works fine.
I also tries to bundle the html js css but the code is delivery partially to the browser.

@cotestatnt
Copy link
Owner

If you are using ESPAsynWebServer library could be something like related to this issue compounded by the additional resources required for the Telegram WiFi client.

With the suggested pull requests, I have greatly improved the stability of some of my projects

@miguelfernando55
Copy link
Author

It appears that to create a server and client at the same time is not possible. I do not know why.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants