Viva Connections ACE – Graph /me returns null on Teams Mobile (Android only) – previously resolved after Teams app update

Question

Issue Description

We are currently facing an issue with a custom Viva Connections Adaptive Card Extension (ACE) built using SPFx, which retrieves user profile information via Microsoft Graph API (/me) using MSGraphClientV3.

Current behavior:

The /me Graph API call works correctly on:

Teams Desktop

  Teams Web

  
     Teams Mobile (iOS)

     
     However, on **Teams Mobile (Android)**, the response is **null**, and user profile properties such as `employeeId`, `mail`, and other basic fields are missing.
```This results in runtime errors such as:


```sql
TypeError: Cannot read properties of null (reading 'employeeId')

---

Important Note / Reference to Previous Ticket

This issue is not new.

We experienced a similar issue previously, where Graph /me returned null on all Teams Mobile platforms (iOS & Android).

At that time, the issue was resolved after Microsoft released an update to the Teams Mobile app, without any code changes on our side.

After the update, Viva Connections worked correctly across all mobile devices.

Difference this time:

The issue now occurs only on Android

iOS Mobile is working as expected

---

Teams App Version (Android)

Teams App Version: 1416/1.0.0.2026015202

---

Observed Behavior (Android Only)

Graph /me response is null

employeeId, mail, and other basic profile properties are null or undefined

Issue is reproducible consistently

---

Scope & Impact

Issue occurs across multiple tenants

Core Viva Connections mobile functionality is broken

Personalized content cannot be rendered on mobile (Android) due to missing user context

---

Troubleshooting Performed

Reconfirmed Graph permissions:

User.Read (Delegated) is granted

Tested on multiple tenants → same behavior

Verified proper initialization of MSGraphClientV3

Confirmed that Desktop (Teams Desktop/Web) still works correctly

---

Request to Microsoft

We would like Microsoft to:

Investigate whether this is a regression or service-side issue specific to Teams Mobile (Android)

Confirm whether there were recent changes affecting Graph API access from Viva Connections on Android

1. Advise on any workaround or fix to ensure consistent behavior across Desktop, iOS, and Android

Answer 1

Hi Fadel Hayeemare

Thank you for reaching out to Microsoft Q&A forum

I understand reliable functionality across all platforms is critical for your Viva Connections implementation, and it's certainly frustrating when a solution works everywhere except on one specific mobile client.

However, since I am a forum moderator, not a Microsoft employee or part of the product team. I do not have a dedicated testing environment to reproduce this specific mobile-only behavior, so the following insights are based on official documentation, similar community reports, and general SPFx troubleshooting experience.

1. Regarding the investigation into a potential regression:

While I cannot officially confirm a service-side regression without a public statement from Microsoft, the behavior you described where the code works perfectly on Desktop, Web, and iOS but fails only on Android- strongly suggests a platform-specific issue with the Teams Android client.

In my experience, when MSGraphClientV3 fails silently or returns null on a specific mobile OS while working elsewhere, it often points to a challenge with the Single Sign-On (SSO) token handoff between the Teams app and the SPFx runtime on that device. Since you mentioned this happened before and was fixed by an app update, it is highly plausible that a recent Android app update has reintroduced a similar behavior.

2. Regarding recent changes to Graph API access:

To the best of my knowledge, and based on the standard Microsoft Graph changelog, there have been no recent breaking changes to the /me endpoint or SPFx authentication flows that would specifically target Android devices while leaving others functional. If this were an API-level change, we would expect it to impact all platforms (iOS and Web) equally. The isolation to Android further reinforces the likelihood of a client-side behavioral change rather than an API policy shift.

3. Advice and suggested workarounds:

Since I suspect this might be a client-specific hurdle, I recommend a few steps to mitigate the impact while you await a potential official fix:

Defensive Coding: As a robustness measure, consider adding a fallback mechanism. If your Graph call returns null, try retrieving the user's basic profile using the SharePoint REST API (/_api/SP.UserProfiles.PeopleManager/GetMyProperties). This API uses a different authentication path (cookie-based/legacy) which sometimes remains functional even when the OBO Graph flow encounters friction on mobile.

Raise a Support Ticket: Since this appears to be out of your control as a developer, the most effective path is to have your administrator log a support ticket. Be sure to provide the specific Teams Android app version (1416/1.0.0.2026015202) and clarify that it works on iOS/Desktop. This helps the engineering team correlate your report with internal telemetry.

Link instruction: https://learn.microsoft.com/en-us/microsoft-365/admin/get-help-support?view=o365-worldwide

I hope this provides some clarity and a path forward!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.