What causes a SerializeField not showing in the Inspector?

The field's type is not serializable, it is a property rather than a field, it lacks SerializeField on a private member, or a compile error stops the Inspector updating, so it does not appear.

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 a SerializeField Not Showing in the Unity Inspector

Quick answer: Use a serializable type, mark private fields with SerializeField, use fields not properties, and clear compile errors so the Inspector refreshes.

A field not showing in the Inspector is usually a serialization rule. Here is how to fix it.

How to fix it

1. Use a serializable type

Unity serializes primitives, common Unity types, and types marked Serializable. A field of a non-serializable type (an interface, a plain class without Serializable) does not show. Make the type serializable.

2. Mark private fields with SerializeField

Private fields are not serialized or shown by default. Add the SerializeField attribute to a private field to expose it in the Inspector while keeping it private in code.

3. Use a field, not a property, and fix compile errors

Properties are not serialized; use a backing field. And if the project has a compile error, the Inspector will not refresh to show new fields. Clear errors so it updates.

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 Unity 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.