4.4.4
Bot framework connect to various channels including telegram.
Sending image from telegram as media will not work if the image is landscape or rectangle.
The channel logs the following error:
Sequence contains no matching element
Steps to reproduce the behavior:
Give a clear and concise description of what you expected to happen.
If applicable, add screenshots to help explain your problem.
Add any other context about the problem here.
[bug]
Hi @muminasaad
I am not able to reproduce this issue. I tried from both Telegram on Windows (desktop app) and Telegram on Android (phone).
A few questions/points:
If you want to share your images, I'd be happy to test. Or I can send you the images that I tested with.
Dear @dmvtech
i am using bot framework version 4.4.4, i cant upgrade as this is a big project for a client and we are too close to release date.
OS is windows
yes multiple landscape images and rectangular images.
yes i have connected to ngrok to my local bot but the call itself was not reaching the bot.
BotFramework .Net Version C#
Telegram Latest Version
Send images as media not files you are correct.

Image is attached
you can share the files with me
the bug is that the file doesnt reach the bot if it was as media but as files it reaches the bot.
Ok, I found some odd behavior, but not sure if it is the same as yours. I'm doing more testing.
Here's what I used to test:
https://github.com/dmvtech/randomstuff/blob/master/dog.jpg
https://github.com/dmvtech/randomstuff/blob/master/seattle2.jpg
Ok. My apologies. 馃槅
I don't know what strangeness I was witnessing last week, but I can definitely reproduce this now.
Tested entirely with .jpg files.
Tested square (410 x 410) image: failure to receive event.
Tested same image, one pixel thinner (portrait, 409 x 410): failure
Tested same image, one pixel wider (landscape, 410 x 411): failure
@dmvtech hhhhhhhhhhhhhhhh as usual we the developer need to return a bug unable to reproduce at least one to believe it is a bug :P
Fix available -- should be deployed before 10/18
@arturl This is still reproducing for me. Can you give us an update on the fix?
I'll update this ticket when the fix is deployed.
The fix has been deployed, enjoy!