Quick answer: Download and install the export templates that match your Godot version exactly via Editor, Manage Export Templates, then re-run the export.
Godot cannot export without the platform templates for your precise version, and they are not bundled with the editor. The fix is a one-time install — but the version must match exactly. Here is how.
How to fix it
1. Install templates for your exact version
Open Editor, Manage Export Templates, and download the set. They must match your editor version including any rc or stable suffix; a 4.2.1 editor needs 4.2.1 templates, not 4.2.
2. Use the offline file if downloads fail
If the in-editor download is blocked, grab the .tpz template file from the official site and install it with Install from File in the same dialog.
3. Re-export after installing
Once the dialog shows the templates installed for your version, the export preset works. If you later upgrade the editor, reinstall matching templates or exports fail again.
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.