Marc Glasser

Looks related to `react-navigation`.

>Reasoning >When the AppState is active, we want to use the regular document.visibilityState behaviour. >The only concern is this comment: >Electron supports document.visibilityState, but switching to another app while Electron...

Nice, thanks @thienlnam !

Random thought.. but if electron has it's own sense for what is in the "background" or "focused" then maybe the chat page should use: **web:** AppState listener **mobile:** AppState listener...

All of these can probably just be renamed to `Identify source and fix crash: [crash name]`

@jasperhuangg I think this is related to our conversation [here](https://expensify.slack.com/archives/C03TQ48KC/p1663797332998359)

I'm inclined to keep this one `Internal` and assign whoever will fix the issue described in that thread.

Seems like we would have to update the participants on the associated reports: https://github.com/Expensify/App/blob/930f18b72829a414ac5e2e19f424871d924eded9/src/pages/ReportDetailsPage.js#L78-L78 I think re: "Optimized API" changes this would mean that we would have something like `InviteWorkspaceMember`...

Going to split this into two separate issues as we'll need to tackle "add" and "remove" as separate actions.

Created a couple of sub issues in E/E. They will probably require some engineering team feedback and more discussion. I've left them unassigned for now and put them on HOLD.