"App not found" error on Mobile (iOS/Android) while Desktop works

Question

We are using the teams Microsoft.com/l/entity/ deep link format to navigate users to a specific Tab within our custom app. While the link resolves correctly on the Teams Desktop and Web clients, it fails on Mobile devices with an "App not found" or "This link is not supported" error. Error show: DeepLinkHandler: Failed to resolve entityId for appId. Error: Entity not found in app manifest.

Answer 1

Hi laurent reece,

Thank you for posting your question in the Microsoft Q&A forum.

Based on my research into the behavior you described for custom apps on Teams mobile, please confirm the following pre‑conditions:

• Has your app been uploaded to your tenant’s app catalog (or published) and is it installable on the mobile client?
• Deep link App ID: In your deep link, are you passing the manifest.id or the app_id from your Entra ID app registration? According to some community reports, the mobile client may require using the AppID as the Entra ID app registration’s objectId for the app to be found; otherwise, you may hit an “App not found” condition.

If you’re already using the correct ID and have validated the above but still see the error, could you share a bit more detail?

• Your full deep link format (with sensitive values redacted).
• Whether you’re using the shareDeepLink function.
• Whether the issue occurs during development or only after the app has been deployed.

Looking forward to your input.

---

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.

Answer 2

The "App not found" error on mobile devices when using the Teams deep link format can occur for several reasons. Here are some potential causes and solutions:

1. Entity ID Resolution: The error message indicates that the entity ID for the app could not be resolved. Ensure that the app ID and entity ID you are using in the deep link are correctly defined in your app's manifest. If the entity ID is not present or incorrectly specified, it will lead to this error.
2. Manifest Configuration: Verify that your app's manifest includes all necessary configurations for mobile support. Sometimes, certain configurations may work on desktop but not be properly set up for mobile environments.
3. Deep Link Format: Ensure that you are using the correct deep link format for mobile. The format you mentioned (teams.microsoft.com/l/entity/) should be compatible, but double-check that all parameters are correctly set.
4. Mobile Device Management (MDM): If your organization uses MDM tools, check if there are any policies that might affect how deep links are handled on mobile devices. Sometimes, MDM settings can restrict certain functionalities.
5. App Installation: Make sure that the app is installed on the mobile device. If the app is not installed, the deep link will not work as expected.
6. Testing on Different Devices: If possible, test the deep link on different mobile devices and operating systems to see if the issue is consistent across all platforms or specific to certain devices.

If the problem persists after checking these aspects, consider reaching out to Microsoft support or consulting the Microsoft Teams development documentation for further assistance.