Swift: Reference to property 'x' in closure requires explicit use of 'self' to make capture semantics explicit
In an escaping closure inside a class, Swift requires self. to make the capture (and potential retain cycle) visible.
Exact message you may see
requires explicit use of 'self' to make capture semantics explicitReference to property in closure requires explicit use of 'self'Call to method in closure requires explicit use of 'self'
Seen on:
iOS
Meaning
Add self. or capture [weak self] / [self] explicitly. For long-lived closures prefer [weak self] to avoid retain cycles.
Common causes
- Escaping closure referencing instance properties without self
- Copying code from SwiftUI structs into classes
⚡ Quick fix
- Write self.property
- Use [weak self] and guard let self
- Use [self] capture list when a strong capture is intended
Detailed fix by platform
Swift
- swift
api.load { [weak self] result in guard let self else { return } self.items = result }
How to diagnose
- Closure — Escaping and long-lived?
- Cycle — Does self own the closure?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in iOS
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 14 Oct 2026