阅读中文版本

Ruby NoMethodError — Undefined Method for Nil

Fix NoMethodError 'undefined method for nil:NilClass' by tracing the nil source and using safe navigation or explicit guards.

ruby -e "begin; nil.name; rescue => e; puts e.backtrace.first(5); end"

obj&.name.inspect

Symptoms

This debugging guide addresses “Ruby NoMethodError — Undefined Method for Nil”. Start from the symptoms, follow the ordered diagnostics, and confirm each hypothesis before moving on; the fix and verification steps then close the loop.

Observed symptoms include:

• NoMethodError: undefined method `name’ for nil:NilClass
• Works when the record exists and fails when it does not
• The stack names a chained call several levels deep

Reproduce and Diagnose

Reproduce the failure in isolation before changing any code. Work through the checks below in order; each one narrows the search space.

Step 1: Read the frame that produced nil

ruby -e "begin; nil.name; rescue => e; puts e.backtrace.first(5); end"

The frame just above the missing method shows which call returned nil.

Step 2: Use safe navigation to confirm the nil

obj&.name.inspect

&. short-circuits on nil; if the result is nil, the receiver was nil at that point.

Likely contributors, in order of frequency:

• A finder returns nil when no record matches and the caller chains a method
• A hash lookup returns nil for an absent key without a default
• A method returns nil on an early branch and callers assume an object

Root Cause

In Ruby, calling a method on nil raises NoMethodError because nil is an object whose singleton class defines only a small set of methods. The defect is the nil value flowing into code that assumed a live object.

The Fix

Use safe navigation (&.) for genuinely optional chains, provide defaults for hash lookups (fetch with default), and make helpers return a documented value on every branch to eliminate silent nils.

Watch out: Chaining &. everywhere hides design errors; prefer ensuring non-nil at the boundary when a value is required.

user = User.find_by(email: '[email protected]') # => nil

# ❌ user.name  raises NoMethodError for nil
# ✅ safe navigation
name = user&.name || 'anonymous'

# ✅ hash default
opts = {}
timeout = opts.fetch(:timeout, 5)

# ✅ fail fast at the boundary
user = User.find_by!(email: '[email protected]') # raises ActiveRecord::RecordNotFound

Verify and Prevent

Rerun with the missing-record input and confirm a controlled result rather than an exception; add tests for the nil path.

Once verified, add a regression test that reproduces the original symptom so the failure cannot silently return.

This class of failure is usually environmental rather than pure logic, so capture the exact command, the environment variables, and the working directory in your bug report. Reproduce it in the smallest possible script, then widen the scope only once the minimal case is understood. A short written checklist for this failure mode saves hours the next time it appears.