Swift error signal SIGABRT how to solve it

Question

I m just a beginner in Swift coding  My idea is quite simple which is an app with two buttons  When clicked  a textfield will change its text  In the Main StoryBoard  I add a textfield and two buttons  In ViewController swift file  I write as this   import UIKit  class ViewController  UIViewController        IBOutlet weak var textfield  UITextField       IBOutlet weak var button  UIButton       IBOutlet weak var button2  UIButton        IBAction func action1   sender  UIButton            textfield text  you just clicked on button1             IBAction func action2   sender  UIButton            textfield text  you just clicked on button2            It is supposed to be all right  However  an error appears which shows      thread1 signal SIGABRT   in file AppDelegate swift line   class AppDelegate  UIResponder  UIApplicationDelegate   What is wrong with my code

User · Answer

I had the same problem  I made a button in the storyboard and connected it to the ViewController  and then later on deleted the button  So the connection was still there  but the button was not  and so I got the same error as you   To Fix    Go to the connection inspector  the arrow in the top right corner  in your storyboard   and delete any unused connections

User · Answer

In my case I wasn t getting error just the crash in the AppDelegate and I had to uncheck the next option  OS ACTIVITY MODE then I could get the real crash reason in my  xib file    Hope this can help you too

User · Answer

A common reason for this type of error is that you might have changed the name of your IBOutlet or IBAction you can simply check this by going to source code    Click on the main storyboard and then select open as  and then select source code   source code will open  and then check whether there is the name of the iboutlet or ibaction that you have changed   if there is then select the part and delete it and then again create iboutlet or ibaction  This should resolve your problem

User · Answer

Sometimes it also happens when the function need to be executed in main thread only  so you can fix it by assigning it to the main thread as follows  -  DispatchQueue main async    your code here

User · Answer

This is a very common error and can happen for multiple reasons  The most common is when an IBOUTLET IBACTION connected to a view controller in the storyboard is deleted from the swift file but not from the storyboard  If this is not the case  use the log in the bottom toolbar to find out what the error is and diagnose it  You can use breakpoints and debugging to aid you in finding the error  To find out how to fix the error please use this article that I found on Google  https   rayaans com fixing-the-notorious-sigabrt-error-in-xcode

User · Answer

I had the same problem  In my case I just overwrote the file   GoogleService-Info plist   on that path    Platform ios YOUR APP NAME Resources Resources   In my case the files were present without data

User · Answer

If you run into this in Xcode 10 you will have to clean before build  Or  switch to the legacy build system  File -  Workspace Settings    -  Build System  Legacy Build System

User · Answer

To solve the problem  first clean the project and then  rebuild   To clean the project  go to MenuBar  Product -  Clean  Then to rebuild the project  just click the Run button as usual

User · Answer

In my case  I was using RxSwift for performing search   I had extensively kept using a shared instance of a particular class inside the onNext method  which probably made it inaccessible  Mutex    Make sure that such instances are handled carefully only when absolutely necessary   In my case  I made use of a couple of variables beforehand to safely  and sequentially  store the return values of the shared instance s methods  and reused them inside onNext block

User · Answer

In my case there was no log whatsoever   My mistake was to push a view controller in a navigation stack that was already part of the navigation stack

User · Answer

For me  This error was because i had a prepare segue step that wasn t applicable to the segue that was being done   long story   override func prepare for segue  UIStoryboardSegue  sender  Any              let gosetup   segue destination as  Update         gosetup wherefrom   updatestring          This was being done to all segue when it was only for one  So i create a boolean and placed the gosetup inside it

User · Answer

You get a SIGABRT error whenever you have a disconnected outlet  Click on your view controller in the storyboard and go to connections in the side panel  the arrow symbol   See if you have an extra outlet there  a duplicate  or an extra one that s not connected  If it s not that then maybe you haven t connected your outlets to your code correctly   Just remember that SIGABRT happens when you are trying to call an outlet  button  view  textfield  etc  that isn t there

User · Answer

For me it wasn t an outlet  I solved the problem by going to the error And reading what it said   Also Noob     This was the error     And The solution was here    Just scroll up in the output and the error will be revealed

[ios] Swift error : signal SIGABRT how to solve it

Examples related to ios

Examples related to swift