Is your feature request related to a problem? Please describe.
When using the pass-secrets extension, the directory tree and password paths in pass are obfuscated using random codenames (e.g., Abcde/FgXyz), while real service names and associations are stored inside an encrypted .secrets.gpg map file located at identity boundaries (.gpg-id folders).
Currently, Android Password Store displays the raw, obfuscated codenames in the list and search views. Without native handling for mapping .secrets.gpg, it is extremely difficult to find or identify entries on mobile, as users have to manually decrypt .secrets.gpg to look up which codename corresponds to which account.
Describe the solution you'd like
Add support for resolving pass-secrets mappings in the app:
1- Map Resolution: Detect .secrets.gpg files within identity folders. When present, decrypt .secrets.gpg using the identity's GPG key and map the raw codename relative paths to their real names/descriptions.
2- UI Display: Render real service names/descriptions in the entry list and search results while keeping underlying file operations linked to the actual .gpg codename paths.
3 - Search Integration: Allow searching entries by their mapped real names (and optionally by email aliases defined in .mask.gpg if present).
Describe alternatives you've considered
Manual Lookup: Manually opening and decrypting .secrets.gpg via another GPG app or text viewer on Android to copy the codename, then navigating back to open the file. This is tedious and inconvenient on mobile devices.
Pass-Tomb: Using pass-tomb instead, which requires raw filesystem mount/Tomb support—something impractical or impossible on non-rooted Android devices. pass-secrets was created specifically as an alternative to pass-tomb for directory obfuscation without requiring filesystem-level mounts.
Additional context
Hello it's me again, I wrote the texts above with AI so as not to waste time, in case of errors I'm sorry in advance, here are some reference images. I hope that the support can be added would be very useful, since I already use this same extension and accessing the application on a daily basis without this support is a memory task, and that only allows me to make modifications at home.
Is your feature request related to a problem? Please describe.
When using the pass-secrets extension, the directory tree and password paths in pass are obfuscated using random codenames (e.g., Abcde/FgXyz), while real service names and associations are stored inside an encrypted .secrets.gpg map file located at identity boundaries (.gpg-id folders).
Currently, Android Password Store displays the raw, obfuscated codenames in the list and search views. Without native handling for mapping .secrets.gpg, it is extremely difficult to find or identify entries on mobile, as users have to manually decrypt .secrets.gpg to look up which codename corresponds to which account.
Describe the solution you'd like
Add support for resolving pass-secrets mappings in the app:
1- Map Resolution: Detect .secrets.gpg files within identity folders. When present, decrypt .secrets.gpg using the identity's GPG key and map the raw codename relative paths to their real names/descriptions.
3 - Search Integration: Allow searching entries by their mapped real names (and optionally by email aliases defined in .mask.gpg if present).
Describe alternatives you've considered
Manual Lookup: Manually opening and decrypting .secrets.gpg via another GPG app or text viewer on Android to copy the codename, then navigating back to open the file. This is tedious and inconvenient on mobile devices.
Pass-Tomb: Using pass-tomb instead, which requires raw filesystem mount/Tomb support—something impractical or impossible on non-rooted Android devices. pass-secrets was created specifically as an alternative to pass-tomb for directory obfuscation without requiring filesystem-level mounts.
Additional context
Hello it's me again, I wrote the texts above with AI so as not to waste time, in case of errors I'm sorry in advance, here are some reference images. I hope that the support can be added would be very useful, since I already use this same extension and accessing the application on a daily basis without this support is a memory task, and that only allows me to make modifications at home.