HomeGauge Companion App Crashing or Stuck Syncing? Here's What to Do

Yes, it's common: inspectors on the InterNACHI forum report the HomeGauge Companion app crashing multiple times per inspection — sometimes losing recent entries and photos — and stuck web writer syncs are frequent enough that HomeGauge publishes an official troubleshooting article for them. The quick version: update the app and your device OS, free up storage, sync before you leave Wi-Fi or good signal, and never uninstall the app while it holds unsynced inspections — the details are below.

Quick Fixes When Companion Crashes

Honest framing first: these are generic mitigations, not a cure. Nothing on this list changes how the Companion app is built — they just reduce the odds of a crash and limit the damage when one happens. That said, they're worth doing, and most of them come straight from HomeGauge's own documentation:

1. Update the app and your device OS. Check the App Store / Play Store for a Companion update and confirm your phone or tablet meets HomeGauge's current platform requirements. Older OS versions and out-of-date builds are the single most common crash factor on any mobile app.
2. Free up device storage. A big inspection is hundreds of full-resolution photos. If your device is running near capacity, the OS starts killing apps under memory and storage pressure — which looks exactly like "the app crashed." Keep several gigabytes free before every job.
3. Sync before you leave good signal. Don't drive away from the property with an unsynced inspection on the device. Sync while you're still on the client's Wi-Fi or in an area with strong LTE, and confirm the sync actually completed rather than assuming it will finish in your pocket.
4. Sync (or back up) before closing the app. Inspectors in the long-running HomeGauge bug-and-gripe thread on InterNACHI describe losing the most recent entries when the app dies. The defensive habit: sync at natural breakpoints during the inspection (after each major section), not just once at the end.
5. Use a restart pattern, not a mid-job scramble. Force-close and reopen the app before each inspection starts, and restart the device itself at least daily. Long-running app sessions accumulate memory bloat; a clean start each job is cheap insurance.
6. Contact HomeGauge support before doing anything destructive. If the app is crash-looping or a sync is wedged, resist the instinct to delete and reinstall. Reinstalling can permanently wipe unsynced inspection data. Support can sometimes recover a stuck state; a reinstall usually can't be undone.

Web Writer Sync Stuck? Try This

If your inspection is stuck syncing to the web report writer (often at 0% or partway), HomeGauge's official sync troubleshooting guide walks through the supported steps. In summary:

• Verify your connection. Switch between Wi-Fi and cellular; a connection that's "up" but high-latency can hang a sync indefinitely.
• Confirm platform requirements. Both the app version and (for the web side) your browser need to meet the published requirements.
• Force-close and reopen the app, then let it retry the sync from the start.
• Sign out and back in to refresh the session if the retry doesn't take.
• Escalate to support if it's still stuck. Again: do not uninstall while unsynced data is on the device.

One practical addition from the field: if a huge inspection won't sync, the photo payload is usually the bottleneck. Getting to a faster connection (or tethering to a different network) resolves more stuck syncs than any settings change.

Why It Keeps Happening

If you've done all of the above and it still happens, that's not you — it's the architecture. A few factual points explain the pattern:

Desktop-era foundations. HomeGauge was founded in 2001, and its flagship report writer is a Windows-only desktop application. The Companion app and the newer web report writer were built to feed that ecosystem, which means the mobile experience is a sync layer bolted onto software designed for a different era. Sync-dependent architectures have an inherent failure mode: whatever hasn't synced yet is at risk every time the app closes unexpectedly.

The sync model itself. When an app treats the server as the source of truth and the device as a temporary buffer, a crash between "you entered it" and "it synced" can mean the entry is simply gone. That's precisely the loss inspectors describe in the forum threads — the most recent items, from the window since the last successful sync.

Post-acquisition uncertainty. HomeGauge was previously owned by American Family Insurance and was sold to Spectora on April 1, 2025 — Spectora itself being backed by private equity firm Radian Capital. Nobody outside the company knows how engineering resources will be allocated between Spectora's platform and HomeGauge's aging codebase, but in most software acquisitions, the acquired product's legacy components get maintenance attention rather than rebuilds. A ground-up rewrite of the Companion sync stack would be the real fix; it's fair to say that's less likely now than it was before the sale. (We covered the deal in depth in our Spectora-HomeGauge acquisition analysis.)

None of this means HomeGauge is bad software — it has served tens of thousands of inspectors for two decades, and at $89/month for the core plan it's competitively priced. But it does mean the crash-and-sync issues are structural, and "keep trying the workarounds" is the realistic ceiling on how much better it gets.

How to Protect Your Inspection Data

Vendor-neutral advice that applies no matter what software you run:

• Assume the device can die at any moment. Sync or export at section boundaries, not just at the end of the job. The cost of a 30-second sync is nothing next to re-walking a crawlspace.
• Keep an independent photo backup. If your app allows it, enable the device's native camera-roll saving (or take critical photos with the native camera too). Photos that exist only inside one app's sandbox vanish with that app's data.
• Export what you own on a schedule. Templates, comment libraries, client lists, and completed report PDFs should live somewhere you control — a cloud drive or local backup — refreshed monthly. This protects you from app failures and from vendor pricing or policy changes.
• Test your recovery path before you need it. Once, deliberately force-close your app mid-entry and see what survives. Knowing exactly what your software loses on a crash changes how often you sync.
• Don't run betas on inspection day. If your vendor offers early-access builds, run them on a spare device, not the one standing between you and a re-inspection.

If You're Ready for Something More Reliable

Full disclosure: we build InspectorData, so weigh this section accordingly. But the reason inspectors switch to us over sync problems is architectural, not marketing: the mobile app is local-first. Every entry, status, and photo is saved to the device the instant you make it — auto-save on every entry, not on a sync timer — and the app works fully offline (see how the offline inspection app works). Syncing happens opportunistically in the background when a connection exists, and if the app closes or the signal drops, nothing is lost because the device copy is the working copy. That design has a zero-data-loss record across multi-day offline inspections.

The practical details if you're comparing:

• $79/month flat — no per-report fees, and $10/month less than HomeGauge's $89 core plan. See the full InspectorData vs HomeGauge comparison.
• 90-day free trial, no credit card — long enough to run real inspections in parallel with HomeGauge before you cancel anything.
• Free migration — we move your HomeGauge templates and comment library for you. The HomeGauge migration page covers exactly what transfers.
• A sane switching process — our guide on how to switch home inspection software lays out the parallel-run approach that avoids any gap in your business.

If you want a broader look at the options first, the HomeGauge alternatives roundup compares the field, including platforms that aren't us.

And if you're not ready to switch — that's genuinely fine. Apply the quick fixes above, build the backup habits, and keep an export of your templates somewhere safe. The worst outcome isn't using HomeGauge; it's losing an inspection's worth of work to a crash you could have contained.

Frequently Asked Questions