Production app fails to load on desktop and web Teams clients

[LeonYasoon]

Hey team,

since Friday, when viewing one of our production apps "Smart Connect for Jira" from the app store, there is an error page:

The issue is only present on the latest Teams desktop (macOS & windows) & web clients, on mobile it works fine. Also the bot associated with this app is still functional in all install locations and RSC permissions are still working as expected in these cases. Also, whats missing is the messaging extension actions.

Take a look at the path im talking to reproduce the behaviour:

"fetch_app_def_failed: Unable to fetch app definition Cannot return null for non-nullable field AppDefinitionBackgroundLoadTabConfiguration.contentUrl., appId - 6402de97-ce33-4386-bf28-b37e9e139c09"

We have not changed anything regarding this app, so we are relatively sure this is a Microsoft issue.
Please advise :)

Best regards
Leon

[LeonYasoon]

Screen Recording 2026-02-16 at 09.25.42.zip

Zipped reproduction video because file size too large otherwise.

[LeonYasoon]

Apparently other production apps are also missing their messaging extensions in installed locations so this might be a more widespread issue.

[tobiasviehweger]

Please note - we recently moved to manifest schema 1.24 - this feels related as the error message seems to imply that the "backgroundLoadConfiguration" property is mandatory (which we do not use at all).

We were on 1.14 before.

[sayali-MSFT]

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

[tobiasviehweger]

Hi team,

this was shortly resolved but is now being back to broken, with the app not loading at all. Any kind of guidance would be appreciated as we have customers not being able to use the app at all. The app view (even the bot messages) are not loading at all due to this error. Also, all message extensions are breaking.

My normal message extension list:

[tobiasviehweger]

Hi team,

we have confirmed with our development apps, that using schema 1.24 breaks the app. Moving to 1.20 again fixes the bug. It seems the schema validation is broken for 1.24, incorrectly the mentioned property to be required, while it's not.

[mingnz]

This issue started happening for us a few days ago also.

Identical behaviour, bot works but tab application does not. Behaviour on clients is inconsistent, probably because of differing versions of Teams.

Teams Desktop (Mac): ✅
Teams Web (Mac): ❌
Teams Web Incognito (Mac): ✅
Teams Web (Windows): ❌
Teams Web Incognito (Windows): ❌

What's even more strange is that we have 3 versions deployed (different environments) with identical App Manifests (except different IDs), and it only affects one specific environment.

All 3 are currently using Schema v1.23

Any advice or updates would be greatly appreciated!

[sayali-MSFT]

Hello,
Could you please check and confirm? Many users have encountered the same issue, so the engineering team has resolved the bug and released the update.

[LeonYasoon]

Hello @sayali-MSFT
we circumvented this issue by fast-tracking an app source package release in which we only downgraded to schema version 1.20 which pretty much immediately fixed it for us. But this also means we can't test 1.24 now.