SPFx apps deployed in teams as personal app all result in error page

[GoldLudie]

Target SharePoint environment

SharePoint Online

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

💥 SharePoint Framework

Developer environment

Windows

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.21.1
• Node.js version: 22.17.1

Describe the bug / error

Hello,

as of the day im raising this issue, deploying SPFx solutions to teams as a personal app seems to be broken.
When trying to open existing Teams Apps they result in the following SharePoint Error Page (Couldn't switch to English, sorry):

Until yesterday the apps still worked, since then no changes have been made to them. I also tried creating a new solution, uploaded it to SharePoint and added it to Teams but it results in the same issue.

With that I tried the Add to Teams feature in the SharePoint Admin Apps Page as well as the manual Teams app package creation and upload but both ways resulted in the same error page.

The Apps work normally when running them as a normal web part on a SharePoint page.

Steps to reproduce

1. Create new SPFx WebPart project
2. Add TeamsPersonalApp to supportedHosts in manifest
3. Bundle and upload webpart
4. Provide to all Sites and press Add to Teams
5. Open the app in teams

Expected behavior

App opens and works normally.

[thomaskjaerulff]

Thank you for posting. We are seeing the exact same issue on multiple tenants. We have reports that this issue started happening today.

[AndresPita]

We have the exact same issue and error message since today on multiple tenants. We are using SPFx version 1.20.0.

[thomaskjaerulff]

Here is a screenshot of the error message we see.

[pheidler]

We are seeing the same issue in some tenants as well. Other tenants are unaffected (for now).

[Ashlesha-MSFT]

Thanks for reporting this issue.
I’ve checked in our tenant and I’m not seeing the SPFx personal app error in teams . However, since multiple developers across tenants are experiencing this problem, I’ll raise a bug to the engineering team for further investigation.
Appreciate your prompt update!

[iNick]

The error looks to be caused by a HTTP 409 response to a POST to this URL: https://substrate.office.com/sigsapi/v1.0/Me/Signals

The response payload:

{
    "result": {
        "error": {
            "code": "Conflict",
            "message": "{\"error\":{\"code\":\"Signal Conflict\",\"message\":\"Conflict Exception: Signal with same instance Id 9666ad5f-2dc3-4eea-9c4c-4f56ae452427 already exists. Signal type is ApplicationEngaged.\"}}"
        }
    },
    "id": 5111,
    "exception": null,
    "status": "RanToCompletion",
    "isCanceled": false,
    "isCompleted": true,
    "isCompletedSuccessfully": true,
    "creationOptions": "None",
    "asyncState": null,
    "isFaulted": false
}

Let me know if you need a complete HAR-file or any additional details.

[petrp314]

Hello, I can confirm to experience the same issues with dozens of apps in multiple tenants. I have created a simple HelloWorld app, deployed to one of the affected tenants and got the same results. Also getting the same HTTP 409 response to a POST to this URL: https://substrate.office.com/sigsapi/v1.0/Me/Signals

[remylaunay]

Hello,

We have two tenants — one for preproduction and one for production.
The SPFX solutions work in preproduction but not in production.

The issue was noticed yesterday morning.

[reiniersmit]

We’re experiencing the same issue and would appreciate an update when available.