context.location Promise Never Resolves in Viva Connections ACE on Microsoft Teams Mobile

[AR-BI-Dev]

Target SharePoint environment

SharePoint Online

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

💥 SharePoint Framework

Developer environment

Windows

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

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

Additional environment details

• SPFx 1.22.1
• Node 22.22.0
• API used: AdaptiveCardExtensionContext.location (experimental feature)

Clients tested:

• ✅Browser (Viva Connections Dashboard in SharePoint): works
• ❌Microsoft Teams mobile (iOS): promise remains pending

Describe the bug / error

we would like to report an unexpected behavior we are observing with the experimental AdaptiveCardExtensionContext.location API when used in a Viva Connections Adaptive Card Extension (ACE), specifically in Microsoft Teams mobile clients.

Summary of the observation
When our ACE is running inside Microsoft Teams on mobile devices (iOS and Android), the promise returned by AdaptiveCardExtensionContext.location never resolves and never rejects. As a result, the application remains in a loading state indefinitely.
The same ACE works as expected when accessed via browser (e.g. Viva Connections in SharePoint), where the promise either resolves successfully with a location or rejects with an error.

Implementation details (simplified)

    // @ts-expect-error we are loading a beta feature
    props.context.location
      .then((location: ILocation) => {
        console.log("LocationACE: Acquired user location: ", location);
        // update user’s location
        setUserGeoLocation(location);
        // switch off the spinner
        setLoading(false);
      })
      .catch((error: Error) => {
        console.error("LocationACE: Error acquiring user location: ", error);
        // switch off the spinner
        setLoading(false);
      });

Request
Could you please:

1. Confirm whether this is a known limitation or issue with Viva Connections in Teams mobile?
2. Check on your side why AdaptiveCardExtensionContext.location does not resolve or reject on mobile clients?
3. Clarify if Teams mobile support for AdaptiveCardExtensionContext.location is considered

This information would help us handle the feature appropriately and set correct expectations for our users.

Thank you very much for your support — we are happy to provide additional information or having a chat to go deeper into details.

Steps to reproduce

use above-described code to acquire user's location using teams mobile

Expected behavior

promise will be resolved or rejected with appropriate error

[Ashlesha-MSFT]

Hello @AR-BI-Dev,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

Hello @AR-BI-Dev,

Thank you for the detailed report. We were able to reproduce the behavior internally using SPFx 1.23.0-rc.1 and tested across multiple hosting environments.

Findings

• ✅ SharePoint page (browser)
  Promise resolves successfully with location.

• ❌ Viva Connections in browser / Teams desktop
  Promise rejects with: "not supported in teams desktop / web".

• ❌ Teams mobile (iOS/Android)
  Promise remains pending indefinitely (no resolve/reject).

One clarification regarding browser behavior: the API appears to work when the ACE is hosted directly on a SharePoint page. However, when hosted inside the Viva Connections app shell (browser or Teams desktop), the promise rejects with "not supported in teams desktop / web".

Responses to your questions

1. Is this a known limitation in Viva Connections desktop/web?

Based on current behavior, the API does not appear to be supported in Viva Connections browser/Teams desktop hosts, where the promise is explicitly rejected with "not supported in teams desktop / web".

2. Why does the promise never resolve or reject on Teams mobile?

We were able to reproduce the same behavior on Teams mobile clients (iOS/Android), where the promise remains pending indefinitely instead of resolving or rejecting. This appears inconsistent with the behavior seen in other hosts and is being investigated further.

3. Is Teams mobile support expected for this API?

The API surface and typings suggest that mobile scenarios are intended to be supported. However, based on current testing, the Teams mobile host does not appear to complete the location request flow correctly.

Thank you again for reporting this and for providing detailed repro information.