Quick answer: Load the soft reference before use with the streaming manager (async) or LoadSynchronous, and only access the resolved object after the load completes.
A soft reference being null is an unloaded asset. Loading it first fixes it. Here is how.
How to fix it
1. Load before using
A soft reference (TSoftObjectPtr) does not keep the asset in memory. Resolving it without loading returns null. Load it first — LoadSynchronous for immediate need, or async streaming to avoid a hitch.
2. Use async streaming
For runtime assets, request the soft reference through the asset manager's async loading and use the object in the completion callback, so loading does not block the frame.
3. Access after the load completes
Only use the resolved object once the load has finished. Accessing a soft reference mid-load, or assuming it is loaded, gives null. Gate access on the load completion.
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 Unreal Engine 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.
Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.