Keep open for quick launching grayed out

[disheet17]

Why I'm not able to select "keep open for quick launch feature for any of the applications. Here is the screen shot I've attached.

Same feature was there in one UI 2.1 as a lock app but after updating to one UI 2.5 it renamed as Keep open for quick launching. 

I tried reset/safe mode/restart phone but same issue.

Device : galaxy s10 lite 

[SliceSupport]

serms this happend after Your recent update !!

and Does it happens to all apps or for just selected app

General Solution

Go to Apps > Configure apps > Battery optimization > All apps. Find the apps you are seeing this problem with and disable them.If you want to make sure that an app keeps running in the background, you can “lock” the app. Open the app. Then launch the Recent Apps page. Tap the app icon and select “keep open for quick launching.” Once done, you can remove it by tapping on the lock icon at the bottom right of the app in the Recents page.

please note : there is limitation that how many apps you can keep running in the background.

[hesamhajati]

my problem is that when I close all apps in the recent app view, they all go away. now if I open an app and click "keep open" it says there are 2 apps kept open for quick launching (while I can only see one app that I chose with the lock icon beneath). tried your method it didn't work. 

[ForeverKnight]

Is this issue fixed for you? And which version of android was it when this happened? And how was it fixed?

[disheet17]

facing same issue after disabling or enabling battery optimization

[Ehsank]

do one thing may it will resolve
Reset App Preferences.
Settings >Apps> Tap on Top Right 3Dots and select Reset App preference

[hesamhajati]

tried it. didn't help

on galaxy note 10+ recently updated

[RobinB]

Did not work

[Fiz_Mad]

this is the solution

setting>biometrics and security>other security setting>pin window...this features to avoid app close...just same like quick launch

[hesamhajati]

this is a cool feature you just taught me, but it didn't solve the stated problem we're having. But really thanks tho