Debugging adaptive card extension in Teams for iOS or Android

[cwparsons]

What type of issue is this?

Question

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

• [ ] 💥 Internet Explorer
• [ ] 💥 Microsoft Edge
• [ ] 💥 Google Chrome
• [ ] 💥 FireFox
• [ ] 💥 Safari
• [X] mobile (iOS/iPadOS)
• [X] mobile (Android)
• [ ] not applicable
• [ ] other (enter in the "Additional environment details" area below)

Additional environment details

• SPFx 1.14
• Viva Connections (Microsoft Teams for iOS) 0.2.202203081239-release-vcm-FebT2

Issue description

I've created and built an adaptive card extension that works within SharePoint Online's Viva Connection dashboard, in all browsers.

However, when I attempt to use the same card in Microsoft Teams for iOS or Android's Viva Connections dashboard, it doesn't work. Tapping on the card button or the card selection action does not bring up a quick view.

I expect that something is erroring out or is unavailable in the JavaScript engine that is powering the card, but I have no idea what.

Is there any guidance on how to debug this? Is there any way to see logs?

I expect that I will have to comment areas of my code out and continuously deploy the .sppkg to figure this out. Is there any way to test my card in the Teams for iOS/Android apps without needing to package and deploy to the app catalog?

[ghost]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[anoopt]

@cwparsons - one way of testing the cards without needing to deploy the package every time is by using spfx-fast-serve's ngrok plugin. It allows us to continue local development and see how the card looks like inside Viva MS Team's mobile app.

[AJIXuMuK]

@cwparsons - you can use Android emulator from android studio. In that case you will be able to attach to the Teams app from Google Chrome to use debugging tools.

[ghost]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues