Forum Discussion

Tomasz_Wojtasik's avatar
Tomasz_Wojtasik
Copper Contributor
Oct 16, 2023

Activity feed notification fails with error 'This app cannot be found.' on New Teams Client

I have an app that sends activity feed notification. The app has a static tab backed by SPFX webpart that redirects to an article when access from activity feed notification. 

On classic Teams desktop client the app works fine, but after updating to new Teams desktop client it fails with a message 'This app cannot be found'.

When I open the app from apps' list it works ok.

In new Teams client activity feed notification presents user avatar but app mini avatar is missing:

In classic Teams client or web client the same notification displays app mini avatar and works correctly:

Should I update my app to work in new Teams client? Or does it have something to do with known issue 'Personal static tabs aren't supported in one-on-one conversations with bots in the new Teams client. However, users can open their app from the app bar in Teams and view the personal static tabs' Introducing the new Microsoft Teams client - Teams | Microsoft Learn. In my case it is not one-on-one conversation with bot.

 

    • Tomasz_Wojtasik's avatar
      Tomasz_Wojtasik
      Copper Contributor
      Any updates on this issue?
      By the way app mini avatars display correctly on new teams client, after an update I think. But the main problem with 'This app cannot be found' message still occurs.
      • Sayali-MSFT's avatar
        Sayali-MSFT
        Icon for Microsoft rankMicrosoft

        Tomasz_Wojtasik -We are not able to repro the scenario, if possible, could you please share small video, so that we can try it from our end?

  • boydihend's avatar
    boydihend
    Copper Contributor
    We're experiencing the same issue in our company and we're having to direct users to switch back to Classic Teams
    • ChetanSharma-msft's avatar
      ChetanSharma-msft
      Icon for Microsoft rankMicrosoft
      Hello Everyone,
      We got an update from engineering team that this issue is fixed now.
      Could you please try it once from your end and let us know the updates?

Resources