You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 7, 2024. It is now read-only.
Relying on the user to pass in a valid path to the xposed module file is setting them up for a lot of different reasons for failure, now that this feature is used more than ever with forks still requiring this method of installation, it might be the best time to fix this
Instead of using the all files permission and using just a path string, you could instead use a pickFile function that opens a file manager for the user to pick a file from, ideally it would then copy that file to the app's storage to remove the need for the all files permission and to allow the user to delete the downloaded file
P.S.: needs a button to revert to default
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Relying on the user to pass in a valid path to the xposed module file is setting them up for a lot of different reasons for failure, now that this feature is used more than ever with forks still requiring this method of installation, it might be the best time to fix this
Instead of using the all files permission and using just a path string, you could instead use a pickFile function that opens a file manager for the user to pick a file from, ideally it would then copy that file to the app's storage to remove the need for the all files permission and to allow the user to delete the downloaded file
P.S.: needs a button to revert to default
The text was updated successfully, but these errors were encountered: