How can we help?

Baby Tracker supports core baby-care records including sleep, feeds and nursing, diapers, pumping, solid foods, growth, temperature, medicine, vitamins, bathing and tooth brushing. Available quick actions may vary with the child and app configuration.

Yes. Use the child switcher at the top of the Today screen. History, Trends and other child-specific views follow the selected child.

A birth date allows Baby Tracker to calculate age-aware information such as nap guidance and growth-percentile context. You can still use the core tracker without it.

Start sleep when your child goes down and stop it when they wake. The app keeps the active session separate from completed History entries until it is finished, helping the Today screen and supported widgets show the current state.

Yes. Open the relevant History entry to edit it. Some recent entries can also be corrected directly from Today. Review the saved time, duration and details after editing, especially for clinically relevant records such as medicine or temperature.

No. Baby Tracker is a record-keeping tool. Growth charts, trends, nap estimates and logged health information are context for caregivers, not a diagnosis or medical recommendation. For medical concerns, use your child’s healthcare professional or local emergency services as appropriate.

Open the child’s settings and use the sharing controls. The owner can invite other iCloud users and grant edit or view-only access. Both people should be signed in to iCloud and have iCloud Drive/CloudKit access available on their devices.

A view-only caregiver can see the shared child’s data but cannot add or change entries. The child owner controls sharing permissions.

iCloud synchronization is not always instantaneous. Confirm both devices have internet access and are signed into the expected iCloud accounts, then reopen Baby Tracker. Avoid repeatedly deleting or recreating a shared child while sync is still catching up.

Supported widgets can show recent care state and provide quick actions such as sleep and common care logging. The app processes widget actions and refreshes the shared snapshot used by the widget.

Open Baby Tracker once to let it refresh its widget snapshot, then return to the Home Screen. If the problem continues, remove and re-add the widget. Also confirm the widget is configured for the intended child where configuration is available.

Keep an original backup file in a safe location and verify that it opens before changing or deleting data in the app. For a complete migration, prefer the app’s dedicated backup format when available; CSV is useful for portable history but may not contain every piece of child-profile or app state.

A CSV export focuses on a child’s history entries in a human-readable table. A full backup can preserve additional app information that does not naturally fit in CSV, such as child-profile or other structured state. Keep both when the data is important.

The restore code is designed to identify previously imported entries and avoid straightforward duplicate creation. However, before doing repeated or cross-child restores, make a fresh backup and verify the destination child after each import.

Do not use repeated cross-child import as a routine duplication workflow unless you have verified the exact app build you are using. Entry identity is important during deduplication, and moving the same exported identities between children can create conflicts or cause records to be skipped. Keep the original source data and test with a disposable child first.

Baby Tracker includes a Huckleberry CSV import path that previews the incoming records before commit. Review the preview carefully, particularly unsupported or skipped rows, before importing.

First fully quit and reopen Baby Tracker, then try the restore again from the app’s settings. If it repeatedly presents and dismisses itself, stop retrying so you do not accidentally start multiple restore flows. Keep the source file unchanged and report the app version, iOS version and the exact restore option you selected.

Confirm you are viewing the correct child and date range, then check History rather than only the Today summary. If you use sharing, check the other caregiver’s device as well. Do not create many replacement entries until you know whether iCloud is still synchronizing.

Include your Baby Tracker app version, iOS version, whether the child is local or shared, the approximate time the issue happened, the feature involved, and what you expected versus what occurred. For data issues, describe the export/backup type but do not send sensitive family records unless specifically needed.