fix: adapt to upstream react changes for idle tracking

[bastidest]

It seems like the Teams developers changed some of the internal structure of how to access the core services components. This commit makes accessing the core services more robust by trying out different attribute paths.

Possibly related to #1198

[petterhs]

I'm having the same issue as in #577 (comment) and your fix works for me!

[jijojosephk]

@bastidest this is awesome! could you update the package.json and com.github.IsmaelMartinez.teams_for_linux.appdata.xml with version details?

[bastidest]

Done

[IsmaelMartinez]

Thanks a lot for contributing! I just merge it and it should hopefully be released soon. Thanks a lot!

[storm9c1]

Does this mean that --appIdleTimeout now works properly again?

If so, thank you, thank you, thank you! I work on multiple virtual desktops. And having it time out was causing me to miss notifications... Seems like after Teams idles for between 5-10 minutes, it would mark me idle even if I was working in other desktops. And then eventually after another period of time, it would show me as offline. Same was happening for a colleague. Once that happens, I stop getting notifications. And that caused me to miss chats and meetings. I'm hoping that by tweaking --appIdleTimeout to some high value, as I did for v1, I can prevent this.

EDIT: missed the tie to #1198 -- will try 1.4.35 and see if the situation is better. Thanks!

[IsmaelMartinez]

Hopefully it does work also for you and you can start using the work legend to describe @bastidest 😉