10.
Debugging
Written by Florent Pillet
Heads up... You’re accessing parts of this content for free, with some sections shown as text.
Heads up... You’re accessing parts of this content for free, with some sections shown as text.
Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.
Unlock now
Understanding the event flow in asynchronous code has always been a challenge. It is particularly the case in the context of Combine, as chains of operators in a publisher may not immediately emit events. For example, operators like throttle(for:scheduler:latest:) will not emit all events they receive, so you need to understand what’s going on. Combine provides a few operators to help with debugging your reactive flows. Knowing them will help you troubleshoot puzzling situations.
Printing Events
The print(_:to:) operator is the first one you should use when you’re unsure whether anything is going through your publishers. It’s a passthrough publisher which prints a lot of information about what’s happening.
Even with simple cases like this one:
let subscription = (1...3).publisher
.print("publisher")
.sink { _ in }
The output is very detailed:
publisher: receive subscription: (1...3)
publisher: request unlimited
publisher: receive value: (1)
publisher: receive value: (2)
publisher: receive value: (3)
publisher: receive finished
Here you see that the print(_:to:) operators shows a lot of information, as it:
- Prints when it receives a subscription and shows the description of its upstream publisher.
- Prints the subscriber‘s demand requests so you can see how many items are being requested.
- Prints every value the upstream publisher emits.
- Finally, prints the completion event.
There is an additional parameter that takes a TextOutputStream object. You can use this to redirect strings to print to a logger. You can also add information to the log, like the current date and time, etc. The possibilities are endless!
For example, you can create a simple logger that displays the time interval between each string so you can get a sense of how fast your publisher emits values:
class TimeLogger: TextOutputStream {
private var previous = Date()
private let formatter = NumberFormatter()
init() {
formatter.maximumFractionDigits = 5
formatter.minimumFractionDigits = 5
}
func write(_ string: String) {
let trimmed = string.trimmingCharacters(in: .whitespacesAndNewlines)
guard !trimmed.isEmpty else { return }
let now = Date()
print("+\(formatter.string(for: now.timeIntervalSince(previous))!)s: \(string)")
previous = now
}
}
It’s very simple to use in your code:
let subscription = (1...3).publisher
.print("publisher", to: TimeLogger())
.sink { _ in }
And the result displays the time between each printed line:
+0.00111s: publisher: receive subscription: (1...3)
+0.03485s: publisher: request unlimited
+0.00035s: publisher: receive value: (1)
+0.00025s: publisher: receive value: (2)
+0.00027s: publisher: receive value: (3)
+0.00024s: publisher: receive finished
As mentioned above, the possibilities are quite endless here.
Note: Depending on the computer and the version of Xcode you‘re running this code on, the interval printed above may vary slightly.
Acting on Events — Performing Side Effects
Besides printing out information, it is often useful to perform actions upon specific events. We call this performing side effects, as actions you take “on the side” don’t directly impact further publishers down the stream, but can have an effect like modifying an external variable.
Using the Debugger as a Last Resort
The last resort operator is one you pull in situations where you really need to introspect things at certain times in the debugger, because nothing else helped you figure out what’s wrong.
Key Points
- Track the lifecycle of a publisher with the
printoperator, - Create your own
TextOutputStreamto customize the output strings, - Use the
handleEventsoperator to intercept lifecycle events and perform actions, - Use the
breakpointOnErrorandbreakpointoperators to break on specific events.
Where to Go From Here?
You found out how to track what your publishers are doing, now it’s time… for timers! Move on to the next chapter to learn how to trigger events at regular intervals with Combine.