What causes Construct 3 icons and splash not applied in the export?

The export used the default placeholder icons because the project's icon images were not set at the required sizes or a stale exported package was reused, so the custom branding never made it in.

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 Construct 3 Icons and Splash Not Applied in the Export

Quick answer: Set all required icon sizes and the loader/splash images in the project, re-export fresh, and clear the wrapper's cached resources.

Your Construct 3 game ships with the default icon or no splash because the branding images were missing or an old export was reused. Setting them and re-exporting fixes it.

How to fix it

1. Set all icon sizes

In the project's icon and loader settings, replace every required size (including the largest source icon) with your art. A missing size makes the exporter fall back to the default placeholder.

2. Configure the loader layout

Choose a loader style that shows your splash/logo and assign the loader image, so the splash appears during load instead of a blank or default screen.

3. Re-export and clear caches

Export a fresh package rather than reusing an old one, and clear the mobile wrapper's cached assets, since a cached build can keep showing the previous default icon and splash.

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 Construct 3 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.

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.