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.

Sign up for GitHub

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

Jump to bottom

File system sync is not working on android #1654

Closed
xuhcc opened this issue Jun 14, 2019 · 2 comments
Closed

File system sync is not working on android #1654

xuhcc opened this issue Jun 14, 2019 · 2 comments

Comments

@xuhcc
Copy link
Contributor

xuhcc commented Jun 14, 2019 •
edited

Operating system

  • Linux
  • Android

Application

  • Desktop
  • Mobile

Description

Steps to reproduce:

  1. Start joplin-desktop 1.0.159 with fresh data directory. It will show "Welcome! (Desktop)" notebook.
  2. Configure joplin-desktop to use File System sync.
  3. Create new notebook and new note inside of it.
  4. Wait for joplin to copy its files to sync directory.
  5. Copy sync directory to android device (I'm using Syncthing for that).
  6. Start joplin-android 1.0.261 with fresh data directory. There will be "Welcome! (Mobile)" notebook.
  7. Configure joplin-android to use File System sync, select sync directory received from desktop.
  8. Hit sync button.

Result:

Notebooks from desktop are not appearing. The journal contains the following error:

06-14T14:57:16,30,"""Total resources: 3""
06-14T14:57:16,30,"""Total folders: 1""
06-14T14:57:16,30,"""Total notes: 4""
06-14T14:57:16,30,"""createRemote: 1""
06-14T14:57:16,30,"""Operations completed: ""
06-14T14:57:16,10,"""Error: Error: ENOENT: no such file or directory, open '/storage/emulated/0/Sync/joplin-test/84fcd68288b646aaa095d10f2b8f3afe.md'. Path: /storage/emulated/0/Sync/joplin-test/84fcd68288b646aaa095d10f2b8f3afe.md
Code: ENOENT
value@index.android.bundle:1144:328
index.android.bundle:1144:4003
k@index.android.bundle:144:3838
index.android.bundle:144:4912
index.android.bundle:144:4020
k@index.android.bundle:144:3838
n@index.android.bundle:144:4070
index.android.bundle:144:4248
f@index.android.bundle:109:155
index.android.bundle:109:882
index.android.bundle:112:1815
y@index.android.bundle:112:657
C@index.android.bundle:112:1021
callImmediates@index.android.bundle:112:3216
[native code]
value@index.android.bundle:25:3011
index.android.bundle:25:1402
value@index.android.bundle:25:2703
value@index.android.bundle:25:1372
[native code]
value@index.android.bundle:25:1307
[native code]""
06-14T14:57:16,30,"""Starting scheduled sync""
@xuhcc
Copy link
Contributor Author

xuhcc commented Jun 14, 2019

Solved by adding SD card permission. Does it make sense to show a more specific error to user in this case?

@laurent22
Copy link
Owner

Solved by adding SD card permission. Does it make sense to show a more specific error to user in this case?

If you can find how to do that, then yes. Otherwise we could at least mention it in the FAQ.

xuhcc added a commit to xuhcc/joplin that referenced this issue Jun 16, 2019
@xuhcc
Android: Suggest to check app perms in case of ENOENT error during FS…
6a093af 
… sync

This error can occur on Android if application doesn't have
SD card permission (laurent22#1654).
This was referenced Jun 16, 2019
Closed
Merged
@lock lock bot locked and limited conversation to collaborators Oct 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@laurent22 @xuhcc