Open ChetanSharma-msft opened 4 weeks ago
Hi ChetanSharma-msft! 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
Thank you for reporting this, we will check this and get back to you.
@Meghana-MSFT : This is really a huge issue for us. We are estimating that around 1/3 of all cards are omitted before the user is able to post it. Most of those users never come back.
In addition to the original case, we do not think that the focus of the message area is the root cause. It appears to happen random. If you repeat creating a card with our app 3-4 times, you will see the effect subsequently.
@Meghana-MSFT : We found a similar issue on Github. Maybe you connect with your collegues from team-js: https://github.com/OfficeDev/microsoft-teams-library-js/issues/2261
This issue is really affecting our business.
@jker-org - We checked this issue at our end, and we see that the issue occurs to us alternatively. I mean after the card is added to compose box, I can post the card to chat. When I try to create a poll again and preview it in the compose box, card disappears. If I try again, it works 3rd time and then card disappears 4th time and so on.
Could you please let us know if you also see any such pattern in the issue?
@Meghana-MSFT : That is great. At least you can reproduce :-) Let me know if there is anything where we can help.
Could you please let us know if you also see any such pattern in the issue?
Yes, we confirm. It is really random. Sometimes first card fails. Sometimes first card succeeds. Sometimes we have to try 2 or 3 times and then it fails. It is hard to predict, but it happens very often.
@jker-org - We raised a bug for this, we will keep you posted on the updates. Thank you.
@Meghana-MSFT : Thank you very much. From our perspective, the severity is high. Let us know if you need any help on this.
Hi @Meghana-MSFT, is there any timeline for the fix? This issue is costing us a lot of users every day.
Hi @jker-org - Unfortunately, we do not have any ETA to share. We are following up with engineering team for updates. We will keep you posted.
@Meghana-MSFT : Thank you very much. Is there any known workaround until the issue is fixed?
Yal why can't I work or make money with my phone. Drive app no. Amazon app no. I have to make money. Can you show me a way to make money. Emergency cat needs to go to the vet. My car headlights out. Please thank you.
On Wed, Aug 14, 2024, 12:18 AM ChetanSharma-MSFT @.***> wrote:
Steps to reproduce
Copied bug from: OfficeDev/teams-toolkit#12205 https://github.com/OfficeDev/teams-toolkit/issues/12205
Details from original post: Describe the bug
We have just published a new app to Microsoft Teams store. The app utilizes message extension feature and a bot from teams toolkit example. First users are complaining about something that most likely is a bug in the Teams app. You can reproduce the issue with our app: https://tinyurl.com/teams-issue-example-app . The link will expire automatically on 31th August 2024. Please do not share any screenshots of our app due to privacy. Thanks!
Our app gathers input from the user and returns an adaptive card for the message area. The user can then post the adaptive card to the chat. Under certain circumstances (see below), the adaptive cards collapses inside the message area and the user is forced to key in the data again. The users are already complaining to us, but it seems that this is a Teams bug that need to be fixed by Microsoft.
To Reproduce
Positive case (when it works):
Select the message area so that it has the focus (purple line at bottom). image
Add an app via '+' in message area that utilizes message extension and returns an adaptive card for the compose area (like our app): image
Adaptive card is shown in compose area. The user can submit the message: image
Everything works fine in this case.
Negative case:
Click the '+' button in the message area. The text box does not have the focus (no purple line at bottom): image
Add the app that return an adaptive card (like our app). image
The adaptive card can be seen for < 1 sec and then it collapses in the compose area. The user has to start again. (Note: Sometimes you have to repeat this scenario 2-3 times to see the effect.) Our app produces a very powerful adaptive card (universal adaptive card) with refresh capabilities. Maybe the preview in the compose area can not handle this when there is no focus? We have no tested this with other apps as we don't know which apps also produce adaptive cards via message extension. Expected behavior
The adaptive card must not collapse / disappear in the compose area when the control does not have the focus. Actual behavior
The adaptive card collapses / disappears in the compose area when the control does not have the focus. This leads to a bad user experience for our users and forces them to gather their data again. In worst case, it can lead to users stop using our app.
VS Code Extension Information (please complete the following information):
Teams Web (Edge) Teams Desktop (Windows 10) Error details
No response
— Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/msteams-docs/issues/11462, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4RHJIVMDQ42JCYBR5S5YGDZRMAEVAVCNFSM6AAAAABMPXCZHKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3DKMBYGQZTKNQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Steps to reproduce
Copied bug from: https://github.com/OfficeDev/teams-toolkit/issues/12205
Details from original post: Describe the bug
We have just published a new app to Microsoft Teams store. The app utilizes message extension feature and a bot from teams toolkit example. First users are complaining about something that most likely is a bug in the Teams app. You can reproduce the issue with our app: https://tinyurl.com/teams-issue-example-app . The link will expire automatically on 31th August 2024. Please do not share any screenshots of our app due to privacy. Thanks!
Our app gathers input from the user and returns an adaptive card for the message area. The user can then post the adaptive card to the chat. Under certain circumstances (see below), the adaptive cards collapses inside the message area and the user is forced to key in the data again. The users are already complaining to us, but it seems that this is a Teams bug that need to be fixed by Microsoft.
To Reproduce
Positive case (when it works):
Select the message area so that it has the focus (purple line at bottom). image
Add an app via '+' in message area that utilizes message extension and returns an adaptive card for the compose area (like our app): image
Adaptive card is shown in compose area. The user can submit the message: image
Everything works fine in this case.
Negative case:
Click the '+' button in the message area. The text box does not have the focus (no purple line at bottom): image
Add the app that return an adaptive card (like our app). image
The adaptive card can be seen for < 1 sec and then it collapses in the compose area. The user has to start again. (Note: Sometimes you have to repeat this scenario 2-3 times to see the effect.) Our app produces a very powerful adaptive card (universal adaptive card) with refresh capabilities. Maybe the preview in the compose area can not handle this when there is no focus? We have no tested this with other apps as we don't know which apps also produce adaptive cards via message extension.
Expected behavior
The adaptive card must not collapse / disappear in the compose area when the control does not have the focus.
Actual behavior
The adaptive card collapses / disappears in the compose area when the control does not have the focus. This leads to a bad user experience for our users and forces them to gather their data again. In worst case, it can lead to users stop using our app.
VS Code Extension Information (please complete the following information):
Teams Web (Edge) Teams Desktop (Windows 10)
Error details
No response