Disagreement on the Definition of the Latest Content During Synchronization
-
Hello team, I’ve encountered an issue with syncing a document between a Mac device and an Android device.
There is a document that exists on both devices:
- Both the Mac and Android devices open the document and switch the software to the background.
- The Mac opens the software, modifies the text content, and saves it.
- At this point, when the Android content is opened, because the software was located in the text editing interface before the screen lock or switching to the background, the Android content will be considered the latest and will overwrite the content edited by the Mac in step 2.
Based on the above problem, I think there should be a few restrictions added:
Plan One:
The first step when any device opens the software should be to confirm whether the sync is complete. The software should not be considered capable of any editing until the sync is complete, ensuring that the software can always update to the correct latest content. For example, adding a global black overlay style.Plan Two:
Add a submit button for users to decide which content needs to be saved to the backend. Unsaved content will only be retained locally. -
Hi @a18883281627. Thanks for posting. This is very helpful information. Yes, the entry with the last timestamp while in edit mode becomes the currently synced revision. There are a couple of ways to exit “edit mode”
Mobile:
- Tap the down arrow at the top left of the keyboard to exit edit mode and begin sync
- Tap Done at the top right to close the entry and begin sync
macOS:
- Click the X at the top left of the entry to close the entry and begin sync.
- Type Command+E or Command+Return to toggle between edit mode and read mode.
Day One does sync automatically while editing, but only every 30 seconds when you are not actively typing. Those above options will ensure content is uploaded to the server. Then, on a different device, launch the app and allow a few seconds for sync to occur before editing.
I would be happy to forward your requests to the team for consideration. While I am not able to provide detailed information on the point of time of any new release, I invite you to check the following for future feature announcements.
Join the Day One Facebook Community
https://facebook.com/groups/DayOneCommunity
Website
https://dayoneapp.com/
Follow us on social media
Twitter: @dayoneapp
Instagram: @dayoneapp
We appreciate your feedback and thank you for your support. Please let us know if we can help you with anything else. -
Here’s the problem:
When I edit a document on Android, switch to the background; when I open the document on mac to edit, save the latest
Then, when I unlock the app on Android again, I realize that it’s still in editing mode by default, and it overwrites the mac’s text with the old content as if it were the newest.Your mechanism requires me to exit edit mode every time I finish editing a document, but this perception is very weak, so I feel very insecure, I must require myself to open the sidebar after editing a document on Android to see the synchronization is complete; on the mac click on “today” to exit the document, in order to ensure that my operations are completely correct and secure.
-
Your mechanism requires me to exit edit mode every time I finish editing a document
This is the current behavior now. If you exit the entry, it saves the entry and will not be overwritten when adding more content on a different device.
I completely understand what you mean. I have submitted a feature request on your behalf! Thanks so much for your feedback.
-
This is a HUGE problem. I have this issue on Android also.
I edit in MacOS app. Then the moment I go to the Android app, it overwrites. It doesn’t matter whether I’m in edit or read mode. The only way I can make the MacOS app authoritative over Android app is have Android app closed first. Then edit in MacOS. Then Command-S to sync from Mac. Then open app on Android, click the user profile circle and choose to Sync. And THEN opening the journal entry on Android will show the latest and not revert back changes.
Very frustrating. I’m debating pulling back my commitment to annual sub, as I’m in a free trial. I paid for premium strictly for this multi-device support. This is an EASY defect/bug to fix on the Android app code. Don’t timestamp or sync authoritatively outwardly from Android when the app state triggers onResume() activity callback. First check for a newer version in the server-side version history than what was locally known. Hurry up with this fix guys.
-
Actually, even this isn’t reliable (what I just wrote above). This is a horrible bug. It’s unusable like this. And this thread is a year old and it still isn’t fixed.
-
Hi @bdbuhr,
Thank you for sharing more details. It sounds like this may be a bug. Would you share diagnostics with us, so we can investigate further?
- Try to reproduce the steps that created the issue.
- Go to Day One > Settings > Support > Report a Bug > Send in Diagnostics File
- In the email that opens up, please add
Attn: Ticket #10115386 to the subject line. - Please include any Entry IDs from affected entries. See here: Locating an Entry ID
We’ll be on the lookout,
-
@bdbuhr Just wanted to let you know, the fix for the Android sync overwrite issue is planned for version
2025.19.It’s not included in the upcoming
2025.18, but we’re working to have it ready in the following release as long as all goes well.We really appreciate your patience in the meantime!
Day One Forums 