[Bug] Problem with SAF navigation (Waiting for data unexpected shutdown)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Steps to follow:
1- Install RSAF on Android.
2- Add the remote http “https://REDACTED/files” to RSAF and allow local connections.
3- Open RetroArch and change the default local folder path to the erista drive.
4- Browse through the folders and enter No-Intro.
5- Click on any of the folders.
You will see that RetroArch closes, without even showing an error. I imagine this is due to saturation.
Is there any way to fix this? Can't it be optimized in some way to make it work?
(Note that it works perfectly with the native Android file browser and with Material Files.)
(Android 11, TV Box, armeabi-v7a)
Thank you.
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 the crash in RetroArch on Android 11 using the reported RSAF remote, erista local folder, and No-Intro navigation steps. Start by investigating the SAF navigation path and capture the failure details; no source file or test is named in the report. Done means browsing into a folder no longer closes RetroArch unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100