You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We started using adaptive cards for our alerts that are sent to teams. Those alerts will contain exceptions or an object in a CodeBlock as they can be large so the CodeBlock ends up being a nice container (and make it very readable).
However, as documented CodeBlock does not work the mobile app. So this is a request to get that supported. It seems like CodeBlock works for a standard message on teams mobile, so the limitation doesn't seem unsolvable.
Proposed solution
Support CodeBlock in adaptive cards for mobile teams app.
Alternatives or Workarounds
If someone has a clever workaround to use the existing features in adaptive cards in meantime that would be appreciated. I haven't determined anything yet.
The text was updated successfully, but these errors were encountered:
We appreciate your input. To ensure your idea is considered for future updates, we recommend submitting it through the Teams Feedback Portal.
If you have any additional thoughts or feedback, please feel free to share them with us. Your contributions are valuable and help improve the product!
Problem Statement
We started using adaptive cards for our alerts that are sent to teams. Those alerts will contain exceptions or an object in a CodeBlock as they can be large so the CodeBlock ends up being a nice container (and make it very readable).
However, as documented CodeBlock does not work the mobile app. So this is a request to get that supported. It seems like CodeBlock works for a standard message on teams mobile, so the limitation doesn't seem unsolvable.
Proposed solution
Support CodeBlock in adaptive cards for mobile teams app.
Alternatives or Workarounds
If someone has a clever workaround to use the existing features in adaptive cards in meantime that would be appreciated. I haven't determined anything yet.
The text was updated successfully, but these errors were encountered: