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

[Tomasz_Wojtasik]

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.

[#2]

@Tomasz_Wojtasik- Thanks for reporting your issue.
We will check this at our end and will get back to you.

[#3]

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.

[#4]

@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?

[#5]

@Sayali-MSFT 

Here is a video that shows how the same activity fails in new Teams client and later that it works fine in classic (web client in this case).

[#6]

@Tomasz_Wojtasik -Thanks for providing the information, we will provide this to internal team and let you know the update once we have any.

[#7]

I'm having the same problem as Tomasz. I'm following this discussion closely.

[#8]

@Tomasz_Wojtasik ,@ChristopherEdling -We are able to repro that issue, We have raised bug for the same , We will inform you once we get any update.

[#9]

@Sayali-MSFT thanks for the information. Any updates yet? Is there a place where we could monitor issue status?

[#10]

@Tomasz_Wojtasik -Currently we don’t have ETA or Update on this thread. We will let you know once we have any updates on it. Thanks.

[#11]

We're experiencing the same issue in our company and we're having to direct users to switch back to Classic Teams

[#12]

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?

[#13]

Hi,
It looks like it's working fine now.
Thank you.

[#14]

@Tomasz_Wojtasik  - Thanks for the confirmation.
Please share your valuable feedback for us: Microsoft Teams Developer Community Response Feedback