It explains the basics of Objective-C thoroughly, and covers material that I didn't know even after programming in Objective-C for five years (half a decade and I didn't know all the property qualifier keywords!)... so I'd recommend it as filling holes for people who had to learn Objective-C on the fly, for practical purposes.
The main issue I have with the text is the underlying tone; through snide offhand remarks like "eek!" and the occasional mention of teams, it seems to assume that Swift is the better -- or more advanced -- language, and that Objective-C is some foreign entity that you may encounter if and only if you embed into a larger team of veteran developers. The discussion of auditing code for nullability and the frequency at which you may encounter certain terms seems to assume that you are (or should be) programming in Swift, and that certain Objective-C mechanisms surface only in existing (legacy) codebases. I would have preferred to read without those assumptions, i.e. that I may wish to write this Objective-C code for a new project from scratch, and think of concepts from a code creator's standpoint rather than a code modifier (or code cleaner)'s standpoint. Objective-C is a very powerful language if you know how to use it, and I think the text doesn't always do that perspective justice. It's still a very good text.