Obsidian Git background sync on iPhone.

Establish a successful manual pull and push before enabling automation. GitSync.md’s iPhone and iPad purchase includes optional Background Sync; there is no extra subscription for that feature. Regional store prices vary.

Choose which app performs Git operations

You can write in Obsidian and use GitSync.md for Git, or configure the Obsidian Git plugin to perform Git inside Obsidian. The apps can use the same local notes, but they have different credentials, implementations, and automation settings.

Start with one automation path on that working copy. Overlapping timers make it harder to tell which client changed the repository or reported an error. The main setup guide explains both routes. The plugin’s mobile documentation describes its own limits; Connect does not remove them.

Enable native Background Sync deliberately

Before enabling publication, review which Obsidian files Git should track.

1. In GitSync.md, verify a manual pull and a reviewed commit and push for the repository.
2. Open the app’s Background Sync settings and enable Enable Background Sync. Review the opt-in explanation.
3. Choose Pull remote changes if you want incoming updates. Automatic pulls accept clean fast-forwards only.
4. Enable Commit and push local changes only if you want automatic publication. This control has separate consent and starts off.
5. Check repository inclusion and any network or power requirements. A newly published folder starts excluded; change its inclusion in Repository Settings if you want it included.

The global opt-in applies to current and future managed repositories unless excluded. Inspect the inclusion settings instead of assuming a newly added vault is covered. When both automatic actions are off, enabling the global setting alone does not run a Git action.

Automatic publication can stage all non-ignored edits, create a commit using the configured author and default message, and push it to the remote. Review ignore rules and the files you intend to share before enabling it. Keep publication manual if you want to inspect every diff first.

Why “every few minutes” is not a guarantee

A configured schedule is a request for execution, not proof that Git ran. iOS decides when to grant background time. Force-quitting, power conditions, networking, repository access, and the operating system’s scheduling can delay or prevent work.

Opening GitSync.md gives it a foreground opportunity to reconcile included repositories. Check its status and the remote commit before switching devices. Neither Connect nor an Obsidian plugin timer guarantees that a suspended app keeps running.

Apple’s background task documentation describes the available execution strategies. GitSync.md’s Background Sync terms explain its specific limits.

What stops automatic work?

• Local changes or divergent history: an automatic pull does not merge or rebase those edits.
• Wrong or missing branch: automatic work does not switch or recreate the branch.
• Authentication or host trust: open the app and handle the required sign-in or trust decision.
• Network or power policy: a Wi-Fi-only or external-power-only repository waits for those conditions.
• Unavailable files or failed push: review the reported state. A failed publication can leave a local commit that still needs pushing.

Automatic work does not force-push, resolve conflicts, merge, or rebase. If you turn automatic pull off but leave publication on, the app still checks remote state and stops when incoming changes require attention. Use the conflict recovery guide for a manual resolution.

Push Sync is an optional wake-up route

GitSync.md’s separately enabled Push Sync connects a GitHub App and delivers a push alert with a best-effort request for targeted background reconciliation. iOS can delay or suppress that attempt. An alert does not prove the notes have arrived.

The name refers to a notification route; it does not itself enable automatic publication of your local notes. Automatic commit and push remains a separate setting. Push Sync’s relay handles the repository and registration metadata described in the AboutContactprivacy policy, not local file contents or Git credentials.

Use an explicit trigger when you need one

Apple Shortcuts can request Pull, Push, or Sync actions from GitSync.md. They provide an explicit workflow but still need the operation to succeed. A Home Screen or Control Center pull button only pulls; it does not publish local edits.

Follow the Shortcuts tutorial and read the result rather than assuming a tap transferred every change. If automatic syncing is delayed, open GitSync.md and verify the manual operation first.

Check automation with a disposable note

1. Push a test note from another device. Check whether it arrives during an allowed attempt, then open GitSync.md if it has not.
2. If you separately enabled publication, edit that test note on the phone. Inspect the app’s result and verify the new commit on your Git server.
3. Repeat with the power and network policy you actually use. A successful foreground run does not establish a guaranteed background interval.

For errors, use the troubleshooting checklist. If managing Git and its execution timing is not the workflow you want, compare Obsidian Sync with Git.