What causes Godot export presets missing after cloning the project?

Export presets live in export_presets.cfg, which is frequently gitignored because it can hold secrets, so a clone has no presets and the export dialog is empty.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Godot Export Presets Missing After Cloning the Project

Quick answer: Commit a sanitized export_presets.cfg (with secrets moved to environment variables or the Godot keystore settings), or document and recreate the presets, so every clone can export.

After cloning, the Project > Export dialog has no presets and you cannot build. The configuration lives in a file that was not committed.

How to fix it

1. Commit export_presets.cfg

The export configuration is stored in export_presets.cfg at the project root. Commit it so collaborators inherit the platform presets instead of an empty export dialog.

2. Keep secrets out of the file

Move signing passwords and keystore paths out of the committed file into environment variables or per-machine editor settings, so you can share the presets without leaking credentials.

3. Document any local steps

Note any machine-specific paths (Android SDK, export templates) in the repo readme so a fresh clone can fill them in and export successfully.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.