Forum Discussion
Custom App is not working anymore in Teams 2.0
Hello,
we created a custom app for Teams to connect to a SPO Site directly from MS Teams.
This app worked well for the last weeks. But now it could not be opened by many Teams 2.0 users.
The error message: "There was a problem reaching this app"
The custom app is working in Teams Classic, Teams Web, Teams Web New..
But not anymore in Team 2.0. It was already working for the users..
manifestVersion":"1.16
contentUrl:https://mycompany.sharepoint.com/sites/SiteName
validDomains":["mycompany.sharepoint.com"]
We already tried to clear the cache, reset the app, reinstall the app.. Nothing helped so far...
26 Replies
DominikA9522
The issue is resolved in the last update:Version
You have Microsoft Teams version 24152.408.2949.8308.You've got the latest version. It was last checked on 24.6.2024.The client version is 49/24053101417.- I had the same issue and I was able to solved it just by downgrading the manifest to 1.15 version
The header should look like this:
{"$schema":"https://developer.microsoft.com/en-us/json-schemas/teams/v1.15/MicrosoftTeams.schema.json","version":"1.0.0","manifestVersion":"1.15","id":"XXX...... - Hi,
any updates for this bug ?
I'm facing the same problem with cutsom app + sso enabled.
thanks - Hi,
I would like to add that we're having a similar issue here. Custom Teams app works fine on web browser but does not work using the new Teams 2.0 client. Switching back to classic loads the new version of the custom app. Hi DominikA9522 ,
Can you please share the deployed manifest so we can check from our end?- Hi,
attached with example data.
Thank you!
{
"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json",
"version": "1.0.5",
"manifestVersion": "1.16",
"id": ".........................",
"packageName": "com.package.name",
"name": {
"short": "App Name",
"full": "Long App Name"
},
"developer": {
"name": "Comanyname",
"mpnId": "",
"websiteUrl": "http://mycompany.de",
"privacyUrl": "https://mycompany.de",
"termsOfUseUrl": "https://mycompany.de"
},
"description": {
"short": "My App in Sharepoint",
"full": "My App in Sharepoint"
},
"icons": {
"outline": "outline.png",
"color": "color.png"
},
"accentColor": "#ededed",
"staticTabs": [
{
"entityId": "....................",
"name": "My App Tab",
"contentUrl": "https://mycompany.sharepoint.com/sites/mysite",
"scopes": [
"personal"
]
},
{
"entityId": "about",
"scopes": [
"personal"
]
}
],
"validDomains": [
"mycompany.sharepoint.com"
],
"showLoadingIndicator": true,
"defaultGroupCapability": {}
}Hello DominikA9522,
We tested using the manifest shared, however it seems to be working fine in Classic Teams and New Teams web client but not in New Teams desktop client. Can you let us know if you are facing the issue only in Web Client?
