An offline baby log needs to save entries on the phone itself. Closeby stores entries locally and exchanges shared history through iCloud separately. Without a connection, your partner may still see an older version of the log. Pass on recent events directly until you have checked both phones.
A saved entry may not have reached your partner
Suppose your phone loses mobile coverage during a trip. You record a feed at 2:10 p.m. and a diaper or nappy change at 2:35 p.m. Both entries may already be in your phone's history while your partner's phone still shows a morning feed as the latest one.
Saving an entry locally and delivering it to another device are separate results. One does not confirm the other. A missing row on your partner's phone also does not prove that the event never happened.
The log records care and helps you reconstruct a sequence. It does not decide when your baby should eat or sleep, or replace advice from a health professional.
Check offline storage before you need it
Try a short check at home using an ordinary event you were going to record anyway.
- Open the app while connected and check that your usual history is available.
- Temporarily turn off Wi-Fi and mobile data. Airplane mode alone is not proof of being offline if Wi-Fi has been turned back on.
- Save one real event and find its time and type in the history.
- Close the app normally, reopen it, and find that same entry.
- Restore the connection. If you share a log, check that the entry reaches the other phone.
Do not uninstall the app as part of this check. Reopening and reinstalling test different things, and reinstalling can affect local data.
If the check fails, use paper or available local notes until you know why. Record the event time, what happened, and any details you actually know.
Keep recording while disconnected
Choose one device for the current set of entries. If another adult is with you, agree who will record each event. Otherwise you may end up with two entries for one feed when the devices exchange updates.
For a late entry, use the time of the event. A note entered at 3 p.m. about a change at 2:35 p.m. should retain the earlier event time. Leave uncertain details unknown instead of inventing exact minutes.
During a handover, explain where the other phone's history stops: "I lost coverage at 1 p.m., so the last two entries are only on my phone." Then pass on those events. The guide to sharing a baby log with your partner covers the wider handover routine.
Compare the history after reconnecting
Open the app on both devices and allow them to exchange changes. Do not assume an immediate update. Network access, iCloud availability, and the app's state can affect delivery.
Check several events from the disconnected period. In this example, that means the 2:10 feed and the 2:35 change. Compare their times, types, and any notes. Seeing one new entry is not enough to establish that the whole history matches.
If both adults recorded one event, compare the details before removing a duplicate. Two entries close together may describe separate events. Keep the information you need when correcting a confirmed duplicate.
If the other phone still looks out of date
First confirm that the entry remains on the original phone. Then check both devices' connections and access to the shared history. Adding the event again is not a way to force delivery.
Keep the original records available while you investigate, and pass on recent events directly. Do not start by deleting the log or signing out of iCloud. If you contact support, describe when the problem happened and the app versions without sending your baby's personal entries.
In Closeby, local history lets you continue recording when the connection drops. Before your next trip, check one complete cycle: save offline, reopen the app, and find the same entry on your partner's phone after reconnecting.