Operating system
iOS
Joplin version
13.3.7
Desktop version info
Joplin 3.2.13 (prod, win32)
Client ID: a5f4dc5ef198419e8ca9ee313d88dbb6
Sync Version:3
Profile Version:47
Keychain Supported:No
Revision:a898e17
Backup: 1.4.2
Freehand Drawing: 2.14.0
Templates: 2.4.0
Sync target
OneDrive
What issue do you have?
Dear Joplin Team,
Thank you for your outstanding work on Joplin, which I use daily for note-taking across platforms.
Problem Description:
My diary notebooks are organized in a two-level hierarchy:
First, users navigate by clicking the parent notebook;
Then click the sub-notebook nested under it;
Finally, select the notes (diary entries) inside the sub-notebook.
Example structure:
- 2025 Diaries (Parent Notebook)
- January (Sub-Notebook)
- Entry 1
- Entry 2
- February (Sub-Notebook)
- Entry 3
This hierarchical structure syncs correctly initially between Windows desktop and iOS Joplin apps.
- Entry 3
- January (Sub-Notebook)
Issue observed on iOS:
After multiple syncs over time, the sub-notebooks suddenly disappear from the iOS app’s interface. Only the parent notebooks remain visible.
This breaks the normal navigation path (parent notebook → sub-notebook → note), making it impossible to browse diary notes in their original organized folders.
Despite the disappearance of sub-notebooks in the UI, all notes remain intact and are still accessible under “All Notes.”
However, without the sub-notebook level, the tree structure is lost, and finding or browsing notes becomes inconvenient.
Attempts to move notes back to sub-notebooks (which still appear in the “Move to notebook” dialog) have no visible effect.
Reinstalling the iOS app and syncing temporarily resolves the issue, but it reoccurs after a few syncs.
This issue does not occur on the Windows version; the sub-notebook structure remains stable there.
Questions:
Is this a known bug or limitation in the iOS Joplin app regarding nested notebook persistence?
Are there plans to improve the reliability of sub-notebook syncing and display in future iOS releases?
Should users avoid using sub-notebooks on iOS for now until this is fixed?
Thank you again for your dedication to this great open-source tool. I look forward to your guidance and possible fixes.
Best regards,
lingd