47aa14e9f6
Fix the "mute ping pong" for once and for all. This patch takes a new approach to the problem: it keeps track of the user generated CallKit transaction ations and avoids calling the delegate method in those cases. This results in a much cleaner and easier to understand handling of the flow: if the delegate method is called it means the user tapped on the mute button. When we sync the muted state in JS with CallKit the delegate method won't be called at all, thus avoiding the ping-pong altogether. In addition, make sure all CallKit methods run in the UI thread. CallKit will call our delegate methods in the UI thread too, thsu there is no need to synchronize access to the listener / pending action sets. |
||
|---|---|---|
| .. | ||
| CallKit.js | ||
| CallKitIcon.png | ||
| actionTypes.js | ||
| index.js | ||
| middleware.js | ||
| reducer.js | ||
