saf path on the default file browser start dir can't get back to the base path menu.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
When you go up the directory hierarchy from the android file chooser you normally end up in a screen where you can select some "standard directories", home, the button to add a new saf path in android etc.
This happens when the path is ""
If your browser start path already is a saf path however, the path can only go up to "." (From "./" which seems weird).
Youre stuck there.
Expected behavior
No response
Steps to reproduce the bug
- Add a saf path -I dont think it needs to be accessible to test but a to add it as a unaccessible one you need to edit the cfg (sdcard, WebDAV from rsaf etc) to file browser default path in options , directories
- Open one of the many file choice options that start there (load content, start directory works. For the purpose of example, this one you can actually get out with the back arrow, and choose another because this screen starts on the screen we want available, but for some you cant, like the manual scanner dat file or content directory)
- Press up, up, up to the limit. You cant get to "", which is the usual sign in normal filesystem to show that screen, just "."
Version/Commit
1.22.2
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
android 15
Affected Cores
No response
Environment information
No response
Relevant log output
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce on Android 15 with a SAF path configured as the file browser start directory, then trace the file chooser's handling of the root path, especially the transition from "./" to an empty path. Done means repeatedly moving up returns to the standard-directories and SAF-path menu instead of leaving the user stuck at ".".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100