SPFX WebPart exposed as teams app not visible in New MS Teams version

[mdissel]

Target SharePoint environment

SharePoint Online

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

💥 SharePoint Framework

Developer environment

None

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 version 1.16.1
• MS Teams manifest version schema v1.16
• MS Teams Windows Desktop version 23231.412.2343.5284
• App is loaded via context "personalTab" and https://{teamSiteDomain}/_layouts/15/TeamsLogon.aspx?SPFX=true&dest=/_layouts/15/teamshostedapp.aspx%3Fteams%26personal%26componentId=....id...%26forceLocale={locale}%26theme={theme}"

Describe the bug / error

The webpart is loaded without any issues in the normale Teams version, but not in the "New" version. The loading indicator is shown for 1 second and after that a blank page.

Current manifest.json validdomains:

"validDomains": [
"{teamsitedomain}",
"cdn.XXXXXX.com", (our own cdn)
".login.microsoftonline.com",
"statica.akamai.odsp.cdn.office.net",
".sharepoint.com",
"*.office.com",
"spoprod-a.akamaihd.net",
"resourceseng.blob.core.windows.net"
],

Steps to reproduce

Expected behavior

Load the webpart from the sharepoint hosted webpage.

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

[nick-pape]

Thank you for filing a report. As this is definitely a potential bug, I've filed a ticket for the Product Group to take a further look at this.

[nick-pape]

@mdissel

Can you provide specific repro steps and/or a link to a repro repository?

Does this occur with a web part generated with yeoman and no other changes?

Additionally, do you have a custom Teams manifest? And if so, what is listed in webApplicationInfo?

[mdissel]

Can you provide specific repro steps and/or a link to a repro repository?

Currently not

Does this occur with a web part generated with yeoman and no other changes?
Additionally, do you have a custom Teams manifest? And if so, what is listed in webApplicationInfo?

{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json",
  "manifestVersion": "1.16",
  "packageName": "XX",
  "id": "XXX",
  "version": "2023.2.1",
  "developer": {
    "name": "XXX",
    "websiteUrl": "XXX",
    "privacyUrl": "XXXX",
    "termsOfUseUrl": "XXXX"
  },
  "name": {
    "short": "XXXX",
    "full": "XXXXX"
  },
  "description": {
    "short": "XXX",
    "full": "XXXX"
  },
  "icons": {
    "outline": "XXXX_outline.png",
    "color": "XXXX_color.png"
  },
  "accentColor": "#004578",
  "showLoadingIndicator": false,
  "isFullScreen": true,
  "staticTabs": [
    {
      "entityId": "XXX",
      "name": "XXX",
      "contentUrl": "https://{teamSiteDomain}/_layouts/15/TeamsLogon.aspx?SPFX=true&dest=/_layouts/15/teamshostedapp.aspx%3Fteams%26personal%26componentId=XXXXXX%26forceLocale={locale}%26theme={theme}",
      "scopes": [
        "personal",
        "team"
      ],
      "context": [
        "personalTab",
        "channelTab"
      ]
    }
  ],
  "configurableTabs": [
    {
      "configurationUrl": "https://{teamSiteDomain}/_layouts/15/TeamsLogon.aspx?SPFX=true&dest=/_layouts/15/teamshostedapp.aspx%3FopenPropertyPane=true%26teams%26componentId=XXXXX%26forceLocale={locale}%26theme={theme}",
      "canUpdateConfiguration": true,
      "scopes": [
        "team"
      ],
      "context": [
        "channelTab",
        "personalTab"
      ],
      "supportedSharePointHosts": [
        "sharePointFullPage",
        "sharePointWebPart"
      ]
    }
  ],
  "defaultInstallScope": "team",
  "validDomains": [
    "{teamsitedomain}",
    "cdn.XXXXX.com",
    "*.login.microsoftonline.com",
    "spoppe-a.akamaihd.net",
    "spoprod-a.akamaihd.net",
    "resourceseng.blob.core.windows.net",
    "msft.spoppe.com"
  ],
  "webApplicationInfo": {
    "resource": "https://{teamSiteDomain}",
    "id": "00000003-0000-0ff1-ce00-000000000000"
  }
}