Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paths are incorectly parsed when SFM used as file selector. #217

Open
freed00m opened this issue Apr 25, 2018 · 2 comments
Open

Paths are incorectly parsed when SFM used as file selector. #217

freed00m opened this issue Apr 25, 2018 · 2 comments
Labels

Comments

@freed00m
Copy link

I use v3.4.0 on adroid 7.1.2 miui 9

I am having trouble in Signal messenger app, when selecting a custom notification sound using Simple File manager.

After navigating to desired sound, the filename is shown in Signal's settings but no sound being played on messages receive.

However if I attempt to select the notification with Amaze file manager, the filename is also shown in Singal's settings but with the difference that sound is being played during notification event.

My instincts telling me the path is parsed differently and I have limited knowledge of who should be responsible for the correct path format. You or the Signal devs.

@tibbi tibbi added the bug label Apr 25, 2018
@tibbi
Copy link
Member

tibbi commented Apr 25, 2018

if it works with Amaze, I can do it too on my side :)

@freed00m
Copy link
Author

Viewing crashlog of other apps like Protonmail Client, I see the SFM path is prepended to the path of the selected file.
Must be bad path resolving somwhere inside SFM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants