-
Notifications
You must be signed in to change notification settings - Fork 23
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
Sync org crashes on folder selection #31
Comments
Hi. It may have something to do with the app permission. Check if all permissions are enabled for the app. |
Happens to me as well. Storage permissions are turned on for the application |
Just re-tested with latest 2.0.5.3 app version. With cyanogenmod 11 still no problem with folder selection. With Android 4.2.2 (Replicant build) - still app crashes when I either try choosing directory in setup wizard or just try clicking OK without selecting any folder. On next app start after the crash - app opens main window (Todos and Agenda empty lists). But when I try creating/adding new org file by using bottom-left icon - name of newly added file appears in the list under Todos and Agenda for a second and then name of newly added file disappears from the Todos and Agenda list. Under 4.2.2 I checked permissions as good as I could. Nothing special. App properties say the app has:
The apps permissions seem like usual. Still the app crashes on folder selection and fails to add new file. Anything special I can do to force enabling all permissions for this app? |
Have this problem as well using 2.0.5.3 on Lineage 7.1.1(Nougat) installed from F-Droid. Doesn't crash but directory is empty and get "Failed to create folder" when I try to create one. Can't proceed from there. The app does have permission to do this. Could you please tell me what folder this is in? Can I go in with file manager and create a parent directory? Tried this in some likely candidates but the folders I create don't show up in the app. Thanks for all your work. Looking forward to using syncorg!! |
So this might be a workaround... Using a file manager, create a folder in your home directory on the internal SD. For example SyncOrg. When setting up the parent folder, select "create folder" and create a subfolder to the one you just created using the file manager. Use the full path. Mine was /storage/emulated/0/SyncOrg/foo Use the back button to go back one directory level. "foo" will be listed, indicating that what you think is happening is really happening. Click "select folder", making /storage/emulated/0/SyncOrg the parent folder. Using this, I was able to connect to a git repo on a local computer via SSH and get all the org files. So far I have been able to see changes I make on the computer appear on the phone, but not vice versa. |
You don't have to use a file manager. All you need to do is to create a directory |
Creation of /storage/emulated/0/SyncOrg made no difference. App still crashes of folder selection attempt. Strange? |
@sokolgeo it was a reply to FHulot that you don't need a file manager. |
I get the same error. Just for the record, I do not see a list of folders. I created a |
Hi, I'm encoutering this issue as well. Can't select a folder. I've allowed syncorg to access SD card. Android 7 on Huawei Mate 8. |
Hi all, I'm also experiencing this error. As soon as I press the "parent folder" button I get "Unfortunately, SyncOrg has stopped." Here's a logcat dump of the crash. Hopefully this helps.
I'm running Android 4.2 on a Galaxy Nexus. EDIT: Also, I'm running SyncOrg 2.0.5.3 from F-Droid |
For what is worth, with stock Android 7.1.2, and version 2.0.5.3 from the play store I get the exact same problem. (And apks for previous versions I cannot install: I am told they are corrupted). |
Hello. The latest version of the app (2.0.5.2) crashed on Replicate Android ROM (based on Android 4.2).
Crash always happens when you click "select directory". On another device with Android 4.4 ROM "select directory" does not lead to any problems, but with Replicant/Android 4.2 it is always app crash.
Hope it helps.
The text was updated successfully, but these errors were encountered: