Closed DivyaDev1992 closed 2 years ago
Hi DivyaDev1992! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.
Best regards, Teams Platform
We are looking into this. I will try to repro it at my end. Meanwhile can you please share bot Id and timestamp when you faced it, so we can try to looking into the logs as well.
Can you also share the manifest hiding important details? Thanks
You can reproduce it easily using the SignNow application. Try searching for a document, and first time it would appear. Second time onwards, it will not appear. This is a quick way of checking the issue, from an application in store.
I am also facing this with the signnow app, but only on Teams desktop client. Not on browser. Can you share your Teams desktop version?
Update: For some reason it has stopped working on web browser also. We have raised a bug. Internal team is looking into it. I will get back to you once got any update.
Thanks
Hello @DivyaDev1992 - We have confirmed with engineering team and this is by design. We don't support at-mention ME anymore.
You can raise a user voice here: https://microsoftteams.uservoice.com/forums/555103-public/filters/new
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 3 days of this comment.
I have created a messaging extension, and when an item is searched, I return the following. I have taken this code from the sample, provided in Microsoft documentation. The code works fine from the messaging extension popup, which is pinned to the ribbon, at the bottom of teams. As shown in the screenshot below.
However, when I type @ the name of messaging extension bot and then select search and type the same text as before, the pop up does not appear. Instead, I see console log errors. The error and behavior is as follows:
The search was working perfectly fine, a month ago. But, now, it seems broken. Kindly look into it. I see that this behavior is happening in few installed apps of mine, in the channel scope as well.