Open
Conversation
Unixityyy
approved these changes
Jan 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
mountcommand appears to be returning the output in a different way than the code is expecting.I've checked three linux devices (Android emulator, MacBookPro, and an Android Device) and they all return the output in the following format (after splitting on spaces, the indexes are):
[0] - The device that is mounted
[1] - The word "on"
[2] - The mount point
[3] - The word "type"
[4] - The file-system type
[5] - The comma separated options enclosed in parenthases
Alternate solution would be to change the indexes we use to 2, 5 (and make sure there are at least 6 args).
Just thought I'd put this up here. I found this while doing my research. The entire
checkForRWPathsappears to be broken.