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
App crashes when zip-output-folder is root directory. Needs more errorhandling #20
Comments
hello @chrisbarth01 . thanks for the error report. In the video i saw that you choose the external-storage-root-directory for I assume that your device does not allow to write to root folder. Can you try if it works if you change to some subfolder? If this was not the reason: without an errorlog i have no clue what has happened. i assume that there is a permissin problem. To help me analyse the problem: can you open the togozip-settings and check " [X] Debug Mode". can you past the text in a text editor and attach it to this ticket? |
It's so unfortunate that I can't even open the settings which I think is in the three dots at the top of the screen because the app still crashes (I already reported that too). However, I don't think that it's permission issue because immediately I launch the app, it asked me to grant storage permission and I granted the app permission to my device's internal storage. |
i just updated myanswer: Can you try if it works if you change to some subfolder? |
i just checked. the app crashes if i try to write to root without error-log and without log in clipboard. i have to fix this. i keep this issue open to remind me to improve error-handling for this use case. thanks again for reporting. |
fixed. Will be available in v2.0.20.190606 which i have just released |
Expected behavior
I expected the app to save the LogCat to file as I had earlier selected the storage location.
Actual behavior
Immediately I clicked on the 'Save LogCat to file' option, the app crashed
How to reproduce
Device: Gionee f100s
Android version: v6.0
App version: v2.0.19.190413
Recording of the bug
The text was updated successfully, but these errors were encountered: