New behavior: current master (revision e4fdf5fb94fe6e982dbc0a5a9f84174355c83df4)
Old behavior: revision 3436f3b032ecd9bba62d088da0258e81c0370105
PHP version doesn't matter, tested with 7.2.33, 7.3.21, 7.4.9 and 8.0.9
Description of problem
It seems, that after PR #127 which migrates reactphp, there is no longer access to real error message from Telegram, but generic HTTP 400 error is returned instead.
Steps to reproduce incorrect behavior:
clone repo and open terminal in cloned folder
run composer install
update BOT_TOKEN constant in examples/conf.php
run php examples/get-chat-members-count.php
Description of error message: "HTTP status code 400 (Bad Request)"
Steps to reproduce old correct behavior:
clone repo but checkout to 3436f3b032ecd9bba62d088da0258e81c0370105 revision (just before #127), then continue as usually
Description of error message: "Bad Request: chat not found"
Added attachments of Tracy logging which is interactive, so you can check all parameters across call stack or environment.
Which version are you using?
New behavior: current master (revision e4fdf5fb94fe6e982dbc0a5a9f84174355c83df4) Old behavior: revision 3436f3b032ecd9bba62d088da0258e81c0370105 PHP version doesn't matter, tested with 7.2.33, 7.3.21, 7.4.9 and 8.0.9
Description of problem
It seems, that after PR #127 which migrates reactphp, there is no longer access to real error message from Telegram, but generic HTTP 400 error is returned instead.
Steps to reproduce incorrect behavior:
composer installBOT_TOKENconstant inexamples/conf.phpphp examples/get-chat-members-count.phpDescription of error message: "HTTP status code 400 (Bad Request)"
Steps to reproduce old correct behavior:
Description of error message: "Bad Request: chat not found"
Added attachments of Tracy logging which is interactive, so you can check all parameters across call stack or environment.
Because Github is not allowing updating HTML files, I uploaded them as
.txt. Just rename them as.htmland open in browser.ping @Yoshi2889