This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 52%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
We are developing an MS teams app with a bot, which returns adaptive cards for link unfurling and other features.
Things work fine when working in local, with ngrok pointing to our machine, and the cards show up nicely in Teams.
However, in production, the cards don't show up, and inspecting the network shows that there is an error 1008, apparently related to Unexpected character during the bot "invoke" call.
We suspected something wrong with gzip handling, and disabled it on our side to check, and indeed the issue was solved for a while, but it is back again. Is anyone else experiencing this ?
The really weird thing is that if we configure the bot endpoint to ngrok, and forward that ngrok to our production server, things work fine, which is strange because when inspecting requests to ngrok or our server, the response bodies are 100% identical.
{
"errorCode": 1008,
"message": "<BotError>Error when processing invoke response: Unexpected character encountered while parsing value: �. Path '', line 0, position 0.",
"standardizedError": {
"errorCode": 1008,
"errorSubCode": 1,
"errorDescription": "<BotError>Error when processing invoke response: Unexpected character encountered while parsing value: �. Path '', line 0, position 0."
}
}
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Hi @Tanguy
Teams tag is mainly focused on the general issue of Microsoft Teams troubleshooting. According to your description, your question is related to Teams development, which is not in our support scope. So I will remove teams tag from your thread. Thanks for your understanding!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 10%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
@Tanguy - Thanks for reporting your issue. There might be an issue with how your production server is handling the requests. It could be related to the server configuration or the network setup. Could you please verify those ?
Hi @SaiPratap-MSFT , thanks for the reply. Is there anything specific that we need to verify ? The server woks fine with other services. Could I share some request identifier so that you can check if you have more info on your side ?
@Tanguy - Could you please share the bot id ,tenantid, and timestamp when it occured and log also would be helpfull.
@SaiPratap-MSFT I just pasted a link to the bot, and got the error. Here is the requested info:
BotID: 1cb5d22d-d073-4cad-954c-2547e23732c4
tenant ID: 34bee18b-abda-4305-868d-9db238623fbe
timestamp: Thu, 02 Nov 2023 08:04:25 GMT
Hi @SaiPratap-MSFT , any news on this ?
Kind regards,
@Tanguy - We are checking your query with engineering team and let you know once we get any updates from them. Thanks.
@SaiPratap-MSFT Here is an example response
HTTP/1.1 200 OK
Date: Mon, 20 Nov 2023 11:10:54 GMT
Content-Type: application/json
Content-Length: 583
Connection: keep-alive
Vary: Accept-Encoding
vary: Accept-Encoding
x-content-type-options: nosniff
cache-control: no-cache
x-xss-protection: 1; mode=block
referrer-policy: same-origin
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=15724800; includeSubDomains; preload
x-robots-tag: none
{"composeExtension":{"type":"result","attachmentLayout":"list","attachments":[{"contentType":"application/vnd.microsoft.card.thumbnail","content":{"title":"Team Building June 2023 — AI Workshop","text":"Purpose The goal of the workshop is to better understand how we could leverage AI tools and services in order to increase our productivity and maybe even unlock new insights from existing data. Schedule The workshop will last 2h30. 20min:[...]","images":[],"buttons":[{"type":"openUrl","value":"https://xxx.elium.com/tile/view/36117","title":"Ouvrir la visualisation"}]}}]}}
any update @SaiPratap-MSFT ?
@Tanguy - Provided your response to the engineering team.I will update you once i get the response from the engineering team
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 62%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Hello @Tanguy - Please let us know how you have collected this response example?
Is this the network trace or error logs?
I would suggest you share the repro steps, sample code and manifest package so that we can try it from our end.
Also, please let us know whether you have deployed this code to Azure App service or somewhere else?
@Tanguy - Provided your response with engineering team.I will update you once i get any resonse from the engineering team
@Tanguy - is this the above result what the bot is responding with and this response results in a 1008 error shown to the user?
Yes, but the same response works fine when I put a tunnel between the production server and the bot (by changing the bot endpoint). So I'm wondering if there isn't something wrong somewhere else, maybe in the headers...
Hello @Tanguy - We are not able to investigate this issue as we are not getting any error logs for provided details. Also, looks like there is some configuration or Header's issue which is actually not related to teams application and more related to server.
Hello, we have finally identified the issue !
When calling the bot, Teams does not set an accept-encoding header, unlike most services. Our production server was returning a response encoded with content-encoding: br in that case. We have fixed the issue and return the response un-encoded in this case, which solves the issue in Teams.
Thanks for the help.