-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Crash on import #22
Comments
Hi, were the files to be imported under a time stamped folder under the Backup folder (which can be set by toggling Incremental Backup under Settings)? If so, would you try creating a test folder with only few test files using some other apps (like a file explorer app), then see if you are able to import from the test folder. |
Thanks. No, I'm importing files previously used in Markor. Do you still want me to do the test?
…On January 24, 2022 10:40:42 AM CST, AppML ***@***.***> wrote:
Hi, were the files to be imported under a time stamped folder under the Backup folder (which can be set by toggling Incremental Backup under Settings? If so, would you try creating a test folder with only few test files using some other apps (like a file explorer app), then see if you are able to import from the test folder.
--
Reply to this email directly or view it on GitHub:
#22 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
It would rule out basic issues like storage permissions using a basic folder with only a handful of files. Then try adding files to the set gradually and repeat the import, closing in onto the note that led to the crashes. |
Describe the bug
When I try to import, the app crashes after selecting the folder.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Files should be imported and usable.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: