Taking Control with Breakpoints
At this point, you might be looking at this and thinking, “There is something wrong with this. My Spidey sense detects Code Smell.” Trust your Spidey sense. This solution is fraught with potential problems for your project.
Even if this approach has uncovered the bug, we’ve sprinkled nasty print statements all over our project. Ideally, we should never include a print command in code that we send to Apple. Although they may help for debugging, print statements do nothing for the end user, and are thus inefficient and slow our app for absolutely no reason. Additionally, any code we add to our project opens up the possibility of breaking something. What’s the point of using something that might break our code ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access