BeFit Tracker Help
Browse help topics

Classic support

Troubleshoot BeFit Tracker Classic

Safely investigate slow opening, database errors, missing servings, provider failures, and blocked historical releases.

Start with the symptom below and protect the Classic database before taking any action that could change local information.

The app opens slowly after an update

  1. Allow the first opening additional time. Classic may be opening or migrating an existing local store.
  2. Confirm that the Mac has available storage.
  3. If the app remains unresponsive, quit it once and reopen it.
  4. Record the Classic version, macOS version, approximate database size, and what was visible when the delay occurred.

Do not delete the database to make the app open faster. First follow Protect your Classic data.

The app cannot open its database

  1. Take a screenshot of the complete error message.
  2. Quit Classic.
  3. Make a separate copy of BeFit.dat without replacing or renaming the original.
  4. Report the problem with the Classic version, macOS version, exact steps, and screenshot.
Do not overwrite the original database.

A failed migration or damaged store needs careful diagnosis. Replacing files without a preserved original can make recovery harder.

Open Food Facts search fails

Check the network connection, retry a specific product query, and try again later. Provider availability, rate limits, regional coverage, and record completeness are outside Classic’s control. See Open Food Facts imports.

A serving size is missing

The food may not contain a supported serving description and gram weight. Classic does not invent conversions. Use the source baseline where appropriate or maintain a carefully verified personal food. See Serving sizes and quantities.

Gatekeeper blocks an older release

Check the release card’s minimum macOS and architecture first. If the archive came from the official Classic collection and macOS shows the expected unchecked-developer warning, follow Apple’s supported per-app approval process.

Collect useful report details

  • BeFit Tracker Classic version
  • macOS version and Mac processor family
  • Whether this was a new installation or an update
  • The exact action sequence that produced the problem
  • A screenshot of the complete warning or error
  • Whether the same problem occurs after one normal relaunch

Send a Classic problem report →