Turn off timeout in app?

[JeckGill]

Is there a way to disable the timeout on a tablet version of powerapps.
I have an time-clock app made and ready to go but when I use the Powerapps App on the tablet, it timesout after ~15 mins, going back into the app selection menu. I want to leave it on always, there's a collection in it for people who are currently checked into the building (this is for Health and Safety recording reasons - I'd explain more, but I'm not HR haha) and it's an extra step for people checking in and out having to open the app back up. 

Is there any way I can just leave it on always? I've tried on the actual tablet settings - the screen is always on, but not the app itself.
Any fixes?

[TheRobRush]

If your screen never shuts off, the app should not be just closing itself. This is not normal behavior. I have never experienced it and not sure what would cause it. Might need to try and monitor a session. Are you sure random employees are not just swiping the screen after their clock in and maybe you have back enabled on or something? If there's not an error in your setup that is I don't know constantly collecting in device memory and crashing the app, or an employee is doing it, my next guess would be your tablet device is managing resources and just offloading the app after a period of inactivity. Eventually it would probably crash or close. But definitely not 15 minutes. I have tablets at my location running display screens of info for employees for over 8 hours a day. The only time they fail is when the device battery dies. a

Guess you could put a timer set to always on auto start etc, leave at 60000 ms and set a button next to it and make both not visible, and have the OnTimerEnd Select(Button1) and just see if things taking place in bg of the app keep it awake. If not I would check those other things.

[JeckGill]

As it stands - I already have a timer that AutoStarts when the app runs. It's purpose is to update a variable that displays the current date and time; it updates every second. So, that should be enough to keep the app alive and ticking. I don't think it should be causing any issues with memory, it's only a variable being updated (see below) so I'm assuming the data is being overwritten and not just building on top of itself over and over? Just as a test I have set it to 20 seconds instead so maybe that would make a difference

UpdateContext({
    largeClock: Text(Now(), "hh:mm"),
    largeDate: Text(Now(), "dddd, d mmmm"),
    dateForPatching: Text(Now(), "dd/mm/yyyy")
})

As for people swiping out of the app - as far as I know any issues with it people will tell me and ask for help if something was going wrong. I'm sat not too far from it, so people would just mention to me while they're using it if something wrong.

Unfortunately the tablet I'm using doesn't have one of those "demo" modes where you can lock it to a certain app, but I don't think that would make too much of a difference. I just have it set so that the screen doesn't turn off/lock when it is plugged in, so there shouldn't be any problems there either.

[JeckGill]

SO, bit of a stretch - but I think I figured out what was kicking me out.

It wasn't the app itself, but a bluetooth keyboard I provided for searching names and for visitors to type in their name/company. Keyboard falls asleep after 5~10 mins of not being active, someone comes along and taps it to wake it up and it kicks them back to the home screen. Don't understand it, but glad to be closer to a solution 🙂