[mike_s_]

When logged in to BBO using the phone app (iOS in my case), temporarily switching to another app (to quickly respond to an important text msg, for example) causes the BBO app to log me off. That is very annoying. Switching apps should not cause BBO to log off. Please fix.

If your concern is responsiveness, then could you at least limit auto-logoff to when I am actively playing at a table (not when I’m dummy, kibitzing, or not even at a table)?

[smerriman]

This is a limitation on iOS's side. If it's moved into the background, they suspend the app shortly afterwards and do not allow it to run any code at all. (Things like music are handled via other means). So from BBO's perspective, there is literally no way to distinguish someone that switched apps from someone who disconnected.

BBO could potentially change how long it takes for someone who disconnected to get logged out, but I suspect it's small for a reason.

[mike_s_]

I’ve never written iOS code, so I had no idea that it might not support running background processes. That’s a very strange limitation for an OS. Apps like messaging and email (which receive when they are not in the foreground) must also be handled as special cases then.

[pescetom]

The same thing happens on Android, so it's not specific to iOS.

[mike_s_]

Settings -> General -> Background App Refresh

Looks like some apps, including my email program (I guess messaging is using some other background processing mechanism) can be configured to periodically refresh. It seems that the BBO app isn’t registered to offer that option — it’s not on the list.

[mike_s_]

https://developer.ap...ackground_tasks

Looks like you could kick off a recurring background task with a timeout just a little shorter than your disconnect timeout to check playing status and determine whether auto log off should be initiated.

[barmar]

 pescetom, on 2022-July-24, 01:55, said:

The same thing happens on Android, so it's not specific to iOS.

Not on my Android tablet (Kindle Fire HD 8). Unless the other application needs too much memory, then the OS kills the background Chrome to get more memory. But I regularly switch to my radio app to change stations and then go back to the browser, and it's usually still connected.

[pescetom]

 barmar, on 2022-July-27, 17:29, said:

Not on my Android tablet (Kindle Fire HD 8). Unless the other application needs too much memory, then the OS kills the background Chrome to get more memory. But I regularly switch to my radio app to change stations and then go back to the browser, and it's usually still connected.

I was talking about the app (like the OP), not browser. I haven't noticed it with a browser but then I rarely play that way on Android.

[barmar]

 pescetom, on 2022-July-28, 05:12, said:

I was talking about the app (like the OP), not browser. I haven't noticed it with a browser but then I rarely play that way on Android.

I realize that, but I think it's mostly the same code under the covers.