zhanghai / zhanghai/MaterialFiles
[Bug]: Deleted folder remains accessible in path history, showing error when accessed
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 9k
- Forks
- 736
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
After deleting a folder, the folder’s path still appears in the path history, and accessing it leads to an error. The folder should be removed from the path history once deleted.
To Reproduce
Steps to reproduce the behavior:
- Open the app and create a folder "a" in any path "R".
- Access the folder "a".
- Use the path history to navigate back to the path "R".
- Delete the folder "a".
- The folder "a" still appears in the path history, and accessing it will show an error.
Screen recording
https://github.com/user-attachments/assets/6b0fb5d7-b4bd-4d52-aea0-caeec1b2f8a7
Expected behavior
Once a folder is deleted, its corresponding path should be removed from the path history to avoid errors when trying to access it.
Device Information:
- Device: generic_x86_64 (Android Studio x86 emulator)
- OS: Android 9
I look forward to your feedback and hope this can be addressed soon. Thank you for your attention to this matter!
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing the path history entry point and the folder deletion flow described in the reproduction steps. Reproduce the issue on Android, then follow how deleted folders remain in history and how selecting that entry produces the error. Done means deleting a folder also removes its path-history entry and no longer allows navigation to the deleted folder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100