Closed EkanshdeepGupta closed 6 years ago
A logcat would help. Otherwise, press on report button in fc dialog and mention this issue number in the message.
I did the second thing. Hope it helps...
Couldn't find it. Did you mention this issue number in it's message.
Ps. found it. Lemme look into it.
Would you please get back to the issue? It's critical (cause an FM must be able not just read but also write). Thanks.
New version, issue persists 🙁
I'm sorry, haven't had time to look into this issue.
Thanks anyway that you care! 👍 I'll wait. Have to use another FM in the meanwhile...
For the reference, can you please report this crash from crash dialog again and leave your device info here. I'll attach the logcat here, and will get back later and work on it. It's too difficult to find logs from a month ago. Thanks for being patient (:
With new version 3.2.1 I couldn't reproduce the crash, sorry.
But I accidentally found that something nasty happens (all paths are related to the external SD card root):
If I do create folder u1
in the Music/!2see
then it warns I need to permit it, then I do permit it for Music
. Then it appears that a new folder appeared: Music/Music/!2see
. And, yes, it asks for permission again.
The logic here is definitely harmed, could you check please?
You need to permit the root of SD Card not the Music folder.
Indeed. The trouble maker is the system dialog saying that Music is the root folder. Hence I naturally chose Music. Now it works and doesn't ask permission anymore. Though it sometimes glitches a bit: Amaze performs operation, refreshes, shows old state, says operation failed. But when I refresh again I see it's alright.
You can report this in a separate issue. I consider this fixed now (:
Sure! Just to make sure: @EkanshdeepGupta , does this solution help?
Actually, no. I've updated to v3.21 and still the app crashes whenever I make something in the root of the SD Card. The permissions are all given.
In the meantime, I have upgraded to a new phone, so now it's Moto Z2 Play, with Android 7.1.1 and it does not look good that the issue is persistent on this device as well...
However, the issue is still unsolved.
I'd suggest you to Clear the Amaze data. Did you try?
Whoa. That did the trick. Thank you so much!
I have Moto G3 running Android 6.0.3 and running Amaze v3.1.2 RC1.
It works great, and I love the app, however, when I want to write something on the root folder of the external sd card (ie /storage/9016-4EF8), be it pasting something there, or creating a new file/folder, I invariably get "Unfortunately, Amaze has stopped."
I can however write on directories inside my sd card (for example /storage/9016-4EF8/bluetooth). On those directories, the app functions like it should, flawlessly. And it also works flawlessly on the internal memory. Only, the root of the external storage is causing a problem. This is not an issue with other file explorer that I've downloaded from the PlayStore, so I'm certain this is an issue with the app itself.
What can I do to mitigate this issue / what additional information must I provide?