Because its still the active screen when the call comes in.
This let the game pause and the ringer take audio over. It was all bundled into the same “phone” permission group, which appeared like this when the permission was requested.
But if you’re playing on your phone you don’t actually need the ringer to take control of your audio as you are already looking at it. And if you press answer the game is no longer an active screen. If you don’t press answer or press decline you don’t really need the game to pause either.
Memory management, it needs to save its state if you leave the app for the call. If it goes to background, and it stays there long enough, whatever was going on would just get dropped.
The issue was the lack of granularity in permissions that were provided.
Because its still the active screen when the call comes in.
This let the game pause and the ringer take audio over. It was all bundled into the same “phone” permission group, which appeared like this when the permission was requested.
But if you’re playing on your phone you don’t actually need the ringer to take control of your audio as you are already looking at it. And if you press answer the game is no longer an active screen. If you don’t press answer or press decline you don’t really need the game to pause either.
Memory management, it needs to save its state if you leave the app for the call. If it goes to background, and it stays there long enough, whatever was going on would just get dropped.
The issue was the lack of granularity in permissions that were provided.