Your next career begins with
Save 50% off your seat in our next iOS Bootcamp. Limited time only. Sessions start April 3.
Your First iOS & SwiftUI App: An App from Scratch
Jan 11 2022 Swift 5.5, iOS 15, Xcode 13
Part 1: Getting Started with SwiftUI
8. Solve Problems

Sign up/Sign in
With a free Kodeco account you can download source code, track your progress, bookmark, personalise your learner profile and more!
Create accountAlready a member of Kodeco? Sign in
About this episode
Learn how to solve problems beginners frequently run into, such as what to do when your code has an error.
Instructors
Contributors
Instructor
Instructor
Illustrator
Video Editor
Over 300 content creators. Join our team.
Version history
iOS 15, Swift 5.5, Xcode 13 (Selected)
Jan 11 2022iOS 16, Swift 5.7, Xcode 14
Feb 13 2023iOS 14, Swift 5, Xcode 12
Dec 15 2020iOS 13, Swift 5, Xcode 11
Sep 3 2019iOS 12, Swift 4, Xcode 10
Jul 24 2018iOS 11, Swift 4, Xcode 9
Sep 19 2017iOS 10, Swift 3, Xcode 8
Nov 7 2016Swift 2
Sep 1 2015Leave a rating/review
Sign up/Sign in
With a free Kodeco account you can download source code, track your progress, bookmark, personalise your learner profile and more!
Create accountAlready a member of Kodeco? Sign in
Sign up/Sign in
With a free Kodeco account you can download source code, track your progress, bookmark, personalise your learner profile and more!
Create accountAlready a member of Kodeco? Sign in
This video Solve Problems was last updated on Jan 11 2022
One of the biggest pitfalls when you’re first learning iOS development is understanding what to do if something goes wrong, so next I’ll show you how you can solve common beginner mistakes.
I recommend you watch this lecture even if you successfully completed the previous exercise, because chances are you will eventually make these mistakes, so it’s good to know how to deal with them. Let’s dive in!
- Show typo mistake
- Show case sensitivity mistake
- Show missing parenthesis
- Show missing curly brace
So far we’ve been dealing with errors - which are in red, but sometimes Xcode will give you a warning, which is in yellow.
What’s the difference? Well, errors are fatal. If you get one, you cannot run the app till the error is fixed.
On the other hand, warnings are informative. Xcode just says, “You probably didn’t mean to do this, but go ahead anyway.”
In my opinion, it is best to treat all warnings as if they were errors. Fix the warning before you continue and only run your app when there are zero errors and zero warnings. That doesn’t guarantee the app won’t have any bugs, but at least they won’t be silly ones :]
All videos. All books.
One low price.
A Kodeco subscription is the best way to learn and master mobile development — plans start at just $19.99/month! Learn iOS, Swift, Android, Kotlin, Flutter and Dart development and unlock our massive catalog of 50+ books and 4,000+ videos.
Learn more