Skip to main content

​
Installation Issues

​
macOS: “Trace is damaged and can’t be opened”

Fixed in v1.2+ — This issue has been resolved. Trace is now properly signed and notarized for macOS, including Sequoia (15+). If you’re on v1.2 or later, you should not see this. If you’re on an older version, update to the latest from buildwithtrace.com/download.
If you’re still on an older version and see this error, macOS has quarantined the app. To fix:
1

Open Terminal

Launch Terminal from Applications → Utilities.
2

Run the fix command

xattr -cr /Applications/Trace.app
3

Reopen Trace

Try opening Trace again — the warning should be gone.

​
macOS: “Trace can’t be opened because Apple cannot check it for malicious software”

Fixed in v1.2+ — This is resolved in the latest version. All binaries now use relative paths, the CLI is properly named, and Info.plist metadata passes Gatekeeper validation. Update to the latest version to avoid this entirely.
If you’re on an older version: go to System Settings → Privacy & Security, scroll down and click “Open Anyway” next to the Trace message.

​
Windows: SmartScreen warning

Click “More info” then “Run anyway”. This warning appears because Trace is new and hasn’t built up reputation with Microsoft yet.

​
Performance Issues

​
Trace is running slowly

  • Close other resource-intensive applications
  • Ensure you have at least 4GB of free RAM
  • For large designs, consider splitting into hierarchical sheets
  • Disable 3D view when not needed

​
High CPU usage during idle

This can happen if auto-save is running frequently. Go to Preferences → General and increase the auto-save interval.

​
Project Issues

​
Project won’t open

  • Check if the project file (.trace_pro) exists and isn’t corrupted
  • Try opening the schematic (.trace_sch) or PCB (.trace_pcb) file directly
  • Check for backup files in the project directory

​
Missing libraries or footprints

If components show as missing:
  1. Go to Preferences → Manage Symbol Libraries / Footprint Libraries
  2. Verify the library paths are correct
  3. Re-add any missing libraries from the Trace library collection

​
Schematic and PCB out of sync

Run Tools → Update PCB from Schematic to synchronize changes. If issues persist, check the annotation and footprint assignments in the schematic.

​
”Update PCB from Schematic” stuck on processing

If the update appears to hang or stays on “processing” indefinitely, the most likely cause is one or more schematic symbols without a footprint assigned.
  1. Go back to the Schematic Editor
  2. Click on each symbol and check the Footprint field in the properties panel
  3. Any symbol with a blank or missing footprint will block the update
  4. Assign the correct footprint, then retry Tools → Update PCB from Schematic
You can quickly find unassigned footprints by running Tools → Edit Symbol Fields and sorting by the Footprint column. Any empty cells need to be filled.

​
Export Issues

​
Gerber files rejected by manufacturer

  • Verify you’re using the correct layer mapping for your manufacturer
  • Check that drill files are included and in the correct format (Excellon)
  • Ensure board outline is on the Edge.Cuts layer
  • Verify units match manufacturer requirements (usually mm)

​
BOM export missing components

Components need proper values and footprints assigned. Check that all components have:
  • A reference designator (R1, C1, U1, etc.)
  • A value field populated
  • A footprint assigned

​
Network Issues

​
Can’t connect to Trace services

  • Check your internet connection
  • Verify firewall isn’t blocking Trace
  • Try disabling VPN if you’re using one
  • Check status.buildwithtrace.com for service status

​
Graphics Issues

​
”Graphics error: Unknown incomplete framebuffer error id 8219”

This error can appear when opening Trace or switching to certain views (3D viewer, PCB editor). It’s related to OpenGL framebuffer initialization on macOS, which has deprecated OpenGL in favor of Metal. You can safely click OK and continue working. The application will function normally after dismissing the dialog. If the error appears frequently, try:
  • Updating to the latest version of macOS
  • Closing other GPU-intensive applications
  • Checking for graphics driver updates
This is a known issue we’re working on resolving.

​
Footprint and Library Issues

​
Footprint loading warning

You may see a warning about footprint resolution when loading a design. This happens because KiCad and Trace use separate systems for resolving footprint libraries. This warning is safe to ignore. Your footprints are loaded and working correctly through Trace’s own library system. If footprints are actually missing from your design, see Missing libraries or footprints above.

​
AI Chat Tips

​
Use plan mode before complex edits

For best results, use plan mode before asking the AI to make significant changes to your design. Plan mode lets the AI:
  • Ask clarifying questions about your intent
  • Research components and reference designs
  • Outline an approach before modifying any files
This prevents wasted edits and ensures the AI fully understands what you want before touching your schematic or PCB. You can enable plan mode by typing “plan” or selecting it from the mode selector in the chat panel.

​
Found a Bug?

If you run into a bug, please open an issue on our GitHub Issues page so we can track and fix it. Include as much detail as possible:
  • Trace version (Help → About)
  • Your operating system and version
  • Steps to reproduce the issue
  • Any error messages or screenshots
Bug reports help us improve Trace for everyone.

​
Still Having Issues?

If you can’t find a solution here: