Quit Game blueprint node does not work on Android

Branch: binary
Build version: 4.2.0-2092659

Quit Game blueprint node does not work on Android, nor does the console command.

I’m assuming this was already known, [probably][2]. I wanted to make a post just in case.

The mobile and console platforms do not permit applications to quit to desktop so the fact that it doesn’t do anything is deliberate. Only on PC platforms (Windows, Mac, Linux) will they work.

Apologies for any inconvenience.

Wouldn’t it be possible to quit/exit to the home screen? I take it that there will be a solution in the future? (Or is there already a function I’m unaware of?)

No, it is working as expected and I don’t expect there will be a change in the future. This is a requirement of the platform creators that you do not provide an exit button. A quick google search pulled up this as a decent article on the matter:

http://android.nextapp.com/site/fx/doc/exit

I see. I guess supporting the android life-cycle will fix the major issue of needing an exit/quit (for example). However, it would still benefit having the ability to go to the home screen or launching an android intent (say from within a game menu). Although I guess this is a separate request/issue.

Ok that’s all nice and fine, except, my phone is hot to the touch even when Unreal isn’t the primary application in view. This suggests that the GPU or something else is generating heat / power draw while my device is not actively using the Unreal App. To allow the device to cool down, I have to go to the task manager and kill the app each time.
So it stands to reason, that something isn’t being put to bed properly.

Hey DCrosby,

You may wish to post this in a new Bug Report, as it is unrelated to the initial issue of the command not working. A new post will be easier for us to assign a developer to as well.

In your new post, also please include the phone model that you were working with when the issue occurred. Can you clarify how you are minimizing/closing the application? How are you deploying it? Any additional information may help as well.

Thank you,

I designed a game that did not provide an option to quit during a level because the player would lose any purchased items used on that level. After the level was complete, the user could exit the game. Google actually denied the app, demanding that the user always had the option to quit. Seems a little contradictory, doesn’t it? Regardless, it is good to allow the user to fire the equivalent of “finish()” using the back button.

Hi,have you found a way to solve it?