IncomingCallCommand not working for Teams V2

[Flofler]

Describe the bug
After switching to Teams V2 the IncomingCallCommand won't be executed anymore, even with enabled "optInTeamsV2" flag.

To Reproduce

1. Switch to Teams V2
2. Command won't be executed anymore

Expected behavior
I would like to have my command being executed after Teams Classic is not available anymore.

Screenshots

Desktop (please complete the following information):

• OS: Linux Mint
• Installation package deb
• Version 1.4.21

teams-for-linux --incomingCallCommand command.sh

Additional context
My command is in my PATH, so the application should be able to find it.

[jijojosephk]

This may not be possible in react based new version of teams.

[IsmaelMartinez]

I believe this is one of those parts now broken because the move from angular to react by microsoft.

[elhennig]

Is there a way to fix this very useful functionality? Or a chance to have to have it fixed?

[IsmaelMartinez]

Aye, but currently it is pretty different. I basically have no clue how to listen to those events in react as we did in angular, but I do suspect MS will be following a similar pattern. Basically, once we find the way to listen to these events, it will be easy to implement

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[cs96and]

Would love a solution to this too

[IsmaelMartinez]

I had a few check and keep trying to think of alternatives, but I haven't been lucky. React is not my strongest area and the angular solution was brought by the community. Lets see if someone with those expertise can have a look at this.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[cs96and]

Any update on this?

[IsmaelMartinez]

Waiting to see if someone from the community can look into this. I did try finding alternative ways of doing this but haven't managed.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.