Maybe it has something to do with the msgbox u are showing when you click on back key.
If u r using modal dialog it will hold the app and it may be the reason for that.
I would recommend u to replace the msgbox with a own libgdx msg dialog. I mean showing a text with 2 options and maybe an lgtexture behind that may be the background.
yeah, I thought that but I don't know why it doesn't crash on my devices? You may be right though, that I should code a proper pause screen without using system dialogs.
@Erel Hi, no it's not starting any services, except google play services for leaderboards and achievements.
If the player presses the back button during gameplay, then it pops up a standard system msgbox2 dialog. I've not been able to replicate the crash on my test devices using the back button here. the area I'm focusing on now is the google play services buttons on my main menu, they do crash for me sometimes.
It is important to add the starter service with the default Application_Error sub. Otherwise you will lose many crash reports and the reports will miss important information.
It's a different error but this is another one causing a lot of crash reports:
I recently added google play services, do I need to add a check that it's managed to connect first or just wait a little longer before loading achievements?
I'm not familiar with this library. However you shouldn't see this dialog at all. Your app should instead crash and print the correct logs. This will happen once you add Application_Error.