Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialZach McDonald
37 PointsThread 1: signal SIGABRT
I am in the process of making a vending machine app and I keep getting this error message when I start the app up any ideas on what is wrong and how to fix it. I am very new to coding and don't know a ton
import UIKit
class ViewController: UIViewController {
@IBOutlet weak var pressAddDoubleTap: UIButton!
@IBOutlet weak var totalPrice: UILabel!
var someValue: Double = 0.0 {
didSet {
totalPrice.text = "$\(someValue)"
}
}
override func viewDidLoad() {
super.viewDidLoad()
}
@IBAction func pressAddDoubleTap(_ sender: UIButton) {
}
@IBAction func buttonPressed(sender: UIButton) {
someValue += 2.00
}
@IBAction func pressAddQuickRevive(_ sender: UIButton) {
}
@IBAction func pressAddSpeed(_ sender: UIButton) {
}
@IBAction func pressAddJug(_ sender: UIButton) {
}
override func didReceiveMemoryWarning() {
super.didReceiveMemoryWarning()
}
}
2 Answers
Taylor Smith
iOS Development Techdegree Graduate 14,153 Pointsoften this happens when an outlet connection is missing or mislabeled some how. I would check to see if you have any outlets you made, and then deleted, and make sure there aren't any broken connections there
Everton Carneiro
15,994 PointsAlso happen when we commit a typo on the identifier of a cell or any other object. That's why is always a good practice to assign the identifiers to a constant. But in this case, might be missing outlet connections as Taylor Smith said. Look likes this error always happen when Xcode is looking for something that doesn't exist, don't match or has only a reference.
Steve Hunter
57,712 PointsSteve Hunter
57,712 PointsI changed this comment to an answer as it's precisely the advice I would have given.