Teams Tab App - getting "Something went wrong" error when installing

Josh Brown 5

We are developing a tab app for MS Teams. As part of our testing we created a sandbox instance of Teams and tried uploading the app and adding it to a Team and to a Chat. When we try to add the tab we get this error in the console:

"CDL: {errorCode:Error,requestId:m-29,component:RequestHandler,requestWindowId:main,operationType:mutation,operationName:installApp,message:error while processing m-29: {name:Error,message:Unexpected error value: App definition not found,stack:[]} (reason: undefined),hostRendererId:our-id-goes-here}"

What is the App definition?

As far as I know all the permissions are correct and I ran the manifest through the MS validation service. Everything came back as correct.

Sayali-MSFT 2,266 Reputation points Microsoft Vendor

2023-03-23T06:01:53.9266667+00:00

@Josh Brown - Thanks for reporting your issue.
If Possible, could you please share the manifest so that we can try it from our end?

Josh Brown 5

{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.12/MicrosoftTeams.schema.json",
  "manifestVersion": "1.12",
  "version": "1.0.8",
  "id": "{{config.auth.objectId}}",
  "packageName": "com.herrmann.teams",
  "developer": {
    "name": "Herrmann International",
    "websiteUrl": "https://www.thinkherrmann.com/",
    "privacyUrl": "https://www.thinkherrmann.com/privacy-policy",
    "termsOfUseUrl": "https://www.thinkherrmann.com/terms-and-conditions"
  },
  "icons": {
    "color": "resources/color.png",
    "outline": "resources/outline.png"
  },
  "name": {
    "short": "{{{config.manifest.appName.short}}}",
    "full": "{{{config.manifest.appName.full}}}"
  },
  "description": {
    "short": "{{config.manifest.appDescription.short}}",
    "full": "FULL DESCRIPTION"
  },
  "accentColor": "#FFFFFF",
  "bots": [],
  "composeExtensions": [],
  "configurableTabs": [
    {
      "configurationUrl": "{{config.fx-resource-frontend-hosting.endpoint}}{{config.fx-resource-frontend-hosting.indexPath}}/config",
      "canUpdateConfiguration": true,
      "scopes": [
        "team",
        "groupchat"
      ],
      "context": [
        "channelTab",
        "privateChatTab",
        "meetingChatTab",
        "meetingDetailsTab",
        "meetingSidePanel",
        "meetingStage"
      ]
    }
  ],
  "staticTabs": [
    {
      "entityId": "index",
      "name": "Stop & Think",
      "contentUrl": "{{config.fx-resource-frontend-hosting.endpoint}}{{config.fx-resource-frontend-hosting.indexPath}}/tab",
      "websiteUrl": "{{config.fx-resource-frontend-hosting.endpoint}}{{config.fx-resource-frontend-hosting.indexPath}}/tab",
      "scopes": [
        "personal"
      ],
      "context": [
        "personalTab",
        "channelTab"
      ]
    }
  ],
  "permissions": [
    "identity",
    "messageTeamMembers"
  ],
  "validDomains": [],
  "webApplicationInfo": {
    "id": "{{config.auth.clientId}}",
    "resource": "{{config.auth.applicationIdUris}}"
  },
  "defaultGroupCapability": {
    "team": "tab",
    "groupchat": "tab",
    "meetings": "tab"
  },
  "defaultInstallScope": "team",
  "authorization": {
    "permissions": {
      "resourceSpecific": [
        {
          "type": "Application",
          "name": "TeamMember.Read.All"
        },
        {
          "type": "Application",
          "name": "Chat.Read.All"
        }
      ]
    }
  },
  "isFullScreen": false,
  "showLoadingIndicator": true
}

Josh Brown 5 Reputation points

2023-03-29T14:03:43.1633333+00:00

@Sayali-MSFT Any suggestions on this? I'm completely blocked and need to get this solved.
Sayali-MSFT 2,266 Reputation points Microsoft Vendor

2023-03-30T04:28:51.58+00:00

@Josh Brown-We have tried the scenario but not able to repro the issue as it is working fine from our end.
Microsoft Teams Version 1.6.00.7879 (64-bit).
We are checking internally, and we will update you once we get any update.
Josh Brown 5 Reputation points

2023-03-30T19:45:35.3233333+00:00

It magically works now all of a sudden. We did not make any changes. I can only guess that it needed more time to propagate the updated version of the app.