[BUG] File picker not working in Secure Folder after One UI 8.0

[jonasmalacofilho]

Checks

• [x] I have read the FAQ section, searched the open issues, and still think this is a new bug.

Describe the bug you encountered:

When trying to open a local database, both KeePass2android regular and notnet, when installed inside a Samsung Secure Folder on a device running One UI 8.0 and Android 16, no longer list files inside the same Secure Folder. Only files outside the secure folder are shown in the system file picker.

The issue appears to be related to the recent update to Secure Folder that shipped in One UI 8.0, although I haven't used KeePass on my phone for a while (so the issue could perhaps be unrelated to the update after all).

Tested with the KeePass2android versions available in the Play Store right now: (regular) 1.13-r1 and (nonet) 1.14-r0.

Describe what you expected to happen:

When installed inside the Secure Folder, it should (only or at least optionally) list the files inside the Secure Folder.

What version of Keepass2Android are you using?

regular: 1.13-r1; nonet: 1.14-r0

Which version of Android are you on?

16

[jonasmalacofilho]

It's starting to look like Samsung might have borked what the file picker has access to, even for apps inside the Secure Folder. And then failed to catch the problem before releasing the One UI 8.0/Android 16 update.

A user reported a similar issue with Discord, and I could also reproduce it with the Gmail app. Neither can access files in the Secure Folder (of course: when they are themselves installed inside the Secure Folder).

https://us.community.samsung.com/t5/Galaxy-S25/One-ui-8-Secure-folder-bug/td-p/3363958

~~A workaround might be to find the database file using the file manager, then "share" it via KeePass2Android. But it doesn't look like KeePass2Android is currently able to handle this. Do you think it's something you could maybe support?~~

A workaround is to use a file manager that can open the file in KeePass2Android using a content:// URL (like Files by Google).

[CoolDom]

Hi, Galaxy S25+ phone, just update to one UI 8.0. The file picker on the app seem NOT looking at the knox container protected part but at the standard location on the phone. Even when moving out from the protected container to the normal zone, the file picker complain that the file IS ONLY at a temporary location and need to copy it elsewhere (by pressing OK and selecting a new location) then you can access the file. BUT the next time you want to access the file in the new location (you copied previously) again it refuse and want you to copy the file somewhere else..

This make the app not usable anymore and access to my password nearly impossible.

Anything you are working on that will have a fix for that?

Thanks, Dom

[KristerLundmark]

I can share a work-around I'm using now:

• Install another file manager in Secret Folder (I use solid explorer).
• Open the kdbx file using solid explorer, select keepass2android as default program

This will open the kdbx file using a "content://" path, but it will only work until solid explorer is closed. To open the kdbx every time, you need 2 more steps:

• Open solid explorer, find the kdbx file, create a shortcut (on regular home screen)
• Open the kdbx file from now on, by using the created shortcut.

I will use this work-around until Samsung gets around to fix the broken file selector.

Regards, Krister

[CoolDom]

Thanks KristerLundmark,

That work around work great! that help a lot.

the side question I would have is what make you think that the issue is with the Samsung file selector vs the way k2p is handling the file selection? (not working with Samsung ;o) ) because what is odd is that the file selection into k2p seems not to see the "protected container memory" (sorry I lack a better word for the Knox protected phone memory) at all but sees the regular phone memory.

just for my understanding, anyway you help me already quite a lot so thank you again

Best, Dom

[KristerLundmark]

I'm not sure, but I'm guessing a Samsung/Knox bug, since Keepass is not the only program affected by this. On my phone (Samsung A56) it affects all programs in Secret Folder that tries to use the standard file selector to read/write to files, the file selector only sees the standard filesystem (outside of Secret Folder).

Regards, Krister

[RayNeverLearns]

I can share a work-around I'm using now:

• Install another file manager in Secret Folder (I use solid explorer).
• Open the kdbx file using solid explorer, select keepass2android as default program

This will open the kdbx file using a "content://" path, but it will only work until solid explorer is closed. To open the kdbx every time, you need 2 more steps:

• Open solid explorer, find the kdbx file, create a shortcut (on regular home screen)
• Open the kdbx file from now on, by using the created shortcut.

I will use this work-around until Samsung gets around to fix the broken file selector.

Regards, Krister

Krister, I landed here not because I use Keepass2Android, but because I use other apps in Secure Folder that are also not able to pick any Secure Folder profile media or other files. Do you think I could use your workaround? I would try it, but I do not even know what the kdbx file is, assume it's something specific to Keepass2Android. Thank you.

[KristerLundmark]

Hello, I'm not sure, since I don't know how the content:// works in android, but I guess you could try. (kdbx is the keepass db file that you open from keepass)

Regards, Krister

[westerly57]

Salut tout le monde, ​Après de nombreuses recherches et pas mal de temps passé à éplucher les forums anglophones, nous avons enfin trouvé une solution à notre problème ! ​Il s'avère que le souci vient bien de l'application DocumentUI d'Android qui ne fonctionne plus correctement avec le Dossier Sécurisé. ​Voici la méthode qui a fonctionné nickel pour moi (et pour d'autres ayant fait la mise à jour) : ​Il faut mettre à jour manuellement l'application DocumentUI via un fichier APK. ⚠️ Important : L'installation de l'APK doit se faire sur le téléphone "normal", et non à l'intérieur du Dossier Sécurisé. ​Vous trouverez l'APK à télécharger et installer ici: https://drive.google.com/file/d/1R07x0p53cbkXRMVWm9RWL4Sq6i8ns8Xx/view?usp=drivesdk ​En espérant que ça vous débloque aussi !

[orlinilro]

@westerly57 Thank you very much 🙏 your solution worked as a charm. I downloaded 14 from APKpure.

Shame on you Samsung!!!

[CoolDom]

@westerly57 Merci bien! Votre solution proposée fonctionne à merveille!