blocks|key|2030133|text|当您有断开连接的出口时，您将得到一个SIGABRT错误。单击情节提要中的视图控制器，然后转到侧面板中的连接(箭头符号)。看看你是否有一个额外的出口，一个副本，或一个额外的没有连接。如果不是这样的话，那么您可能还没有正确地将您的出入口连接到代码上。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2030134|请记住，SIGABRT是在您试图调用不存在的出口(按钮、视图、文本字段等)时发生的。|2030135|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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.

blocks|key|2400318|text|为了解决这个问题，首先清理项目，然后重新构建。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2400319|要清理该项目，请转到MenuBar:+Product+->+Clean|2400320|然后，要重建该项目，只需像往常一样单击Run按钮。|2400321|entityMap^0|B|2|I|4|0|A|P|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

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.

blocks|key|2400401|text|对我来说不是出口。我解决了这个问题，走到错误的地方，读了它说的话。(也是Noob.)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2400402|这是一个错误：|2400403|​|2400404|📷|atomic|offset|length|2400405|2400406|解决办法就在这里：|2400407|2400408|2400409|只要在输出中向上滚动，错误就会显示出来。|2400410|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/e15554acbfef6514748946b587ccdf7f.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/f0a0093f0fa511ac92d9c8e087948fb9.png^0|0|0|0|0|1|0|0|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|15|8|@]|9|@$I|16|J|17|1|18]]|A|$]]|$1|K|3|E|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|G|5|H|7|1B|8|@]|9|@$I|1C|J|1D|1|1E]]|A|$]]|$1|O|3|E|5|6|7|1F|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1G|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y|Z|-4]]|10|$5|U|V|W|A|$X|11|Z|-4]]]]

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:

<a href="https://i.stack.imgur.com/D6et5.png" rel="noreferrer"><img src="https://i.stack.imgur.com/D6et5.png" alt="enter image description here"></a>

And The solution was here:
<a href="https://i.stack.imgur.com/1YwhA.png" rel="noreferrer"><img src="https://i.stack.imgur.com/1YwhA.png" alt="enter image description here"></a>

Just scroll up in the output and the error will be revealed.

blocks|key|2400436|text|我也有同样的问题。我在故事板上做了一个按钮，并将它连接到ViewController，然后删除了这个按钮。所以连接仍然存在，但是按钮没有，所以我得到了和你一样的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2400437|To+Fix:|offset|length|style|BOLD|2400438|转到连接检查器(右上角的箭头，故事板中的箭头)，删除所有未使用的连接。|2400439|entityMap^0|0|0|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

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.

blocks|key|2030236|text|这种错误的一个常见原因是您可能已经更改了您的IBOutlet或IBAction的名称，您只需查看源代码即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2030237|单击main.storyboard，然后选择open+，然后选择源代码|offset|length|style|BOLD|2030238|📷|atomic|2030239|​|2030240|源代码将打开|2030241|然后检查是否有您更改过的iboutlet或ibaction的名称，如果有，请选择该部分并删除它，然后再次创建iboutlet或ibaction。这应该能解决你的问题|2030242|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/4550eaa5703742adbac4eff562a2b346.png|imageAlt^0|0|2|F|M|5|W|3|0|0|1|0|0|0|0|6|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]|$D|13|E|14|F|G]|$D|15|E|16|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1C|8|@$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X|Y|-4]]]]

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
<img src="https://i.stack.imgur.com/dJV7M.png" alt="enter image description here">

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

blocks|key|2029136|text|在我的情况下，根本没有任何日志。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2029137|我的错误是将视图控制器推到已经是导航堆栈一部分的导航堆栈中。|2029138|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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.

blocks|key|2400586|text|在我的例子中，我得到的不只是AppDelegate中的崩溃，我不得不取消下一个选项：OS_ACTIVITY_MODE，然后我可以在我的.xib文件中得到真正的崩溃原因。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2400587|​|2400588|📷|atomic|2400589|2400590|希望这也能对你有所帮助|2400591|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/70bea63e38a225f17c88c9794de35a7c.png|imageAlt^0|16|G|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|K|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|15|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U|V|-4]]]]

In my case I wasn't getting error just the crash in the AppDelegate and I had to uncheck the next option: <code>OS_ACTIVITY_MODE</code> then I could get the real crash reason in my .xib file

<a href="https://i.stack.imgur.com/0rBOL.png" rel="noreferrer"><img src="https://i.stack.imgur.com/0rBOL.png" alt="enter image description here"></a>

Hope this can help you too :)

blocks|key|2400600|text|如果在Xcode+10中遇到这种情况，则必须在构建之前进行清理。或者，切换到遗留构建系统。文件->工作区设置..。->构建系统:遗留构建系统。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2400601|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|2030272|text|有时，当函数只需要在主线程中执行时，也会发生这种情况，因此您可以通过将其分配给主线程来修复它，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2030273|DispatchQueue.main.async{
++your+code+here
}|code-block|syntax|javascript|2030274|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

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 :-

<pre><code>DispatchQueue.main.async{
 your code here
}
</code></pre>

blocks|key|2400691|text|对我来说，这个错误是因为我有一个准备步骤，不适用于正在执行的segue。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2400692|说来话长：|2400693|override+func+prepare(for+segue:+UIStoryboardSegue,+sender:+Any?)+{

++++++++let+gosetup+=+segue.destination+as!+Update
++++++++gosetup.wherefrom+=+updatestring

++++}|code-block|syntax|javascript|2400694|在只有一个人的时候，所有的人都在做这件事。因此，我创建了一个布尔值，并将其放入其中。|2400695|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

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:

<pre><code>override func prepare(for segue: UIStoryboardSegue, sender: Any?) {

 let gosetup = segue.destination as! Update
 gosetup.wherefrom = updatestring

 }
</code></pre>

This was being done to all segue when it was only for one. So i create a boolean and placed the gosetup inside it.

blocks|key|1405055|text|在我的例子中，我使用RxSwift执行搜索。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1405056|我一直在onNext方法中广泛地使用特定类的共享实例，这可能使它无法访问(Mutex)。|offset|length|1405057|确保只有在绝对必要时才仔细处理此类实例。|1405058|在我的示例中，我预先使用了几个变量来安全地(并按顺序)存储共享实例的方法的返回值，并在onNext块中重用它们。|1405059|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/34524/what-is-a-mutex^0|0|11|5|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

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 (<a href="https://stackoverflow.com/questions/34524/what-is-a-mutex">Mutex</a>).

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.

blocks|key|2030316|text|我也有同样的问题。在我的例子中，我刚刚重写了文件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2030317|GoogleService-Info.plist|code-block|syntax|javascript|2030318|在这条道路上：|2030319|Platform\ios\YOUR_APP_NAME\Resources\Resources|2030320|在我的例子中，这些文件没有数据。|2030321|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I had the same problem. In my case I just overwrote the file 

<pre><code>GoogleService-Info.plist
</code></pre>

on that path: 

<pre><code>Platform\ios\YOUR_APP_NAME\Resources\Resources
</code></pre>

In my case the files were present without data.

blocks|key|1405138|text|这是一个非常常见的错误，可能由于多种原因而发生。最常见的情况是将连接到情节提要中的视图控制器的IBOUTLET/IBACTION从快速文件中删除，而不是从情节提要中删除。如果不是这种情况，请使用底部工具栏中的日志来找出错误所在并进行诊断。您可以使用断点和调试来帮助您查找错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1405139|要了解如何修复错误，请使用我在Google：https://rayaans.com/fixing-the-notorious-sigabrt-error-in-xcode上找到的这篇文章|offset|length|1405140|entityMap|0|LINK|mutability|MUTABLE|url|https://rayaans.com/fixing-the-notorious-sigabrt-error-in-xcode^0|0|M|1R|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

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: <a href="https://rayaans.com/fixing-the-notorious-sigabrt-error-in-xcode" rel="nofollow noreferrer">https://rayaans.com/fixing-the-notorious-sigabrt-error-in-xcode</a>

blocks|key|2400773|text|如果此崩溃发生在访问包中的视图控制器时，您可能必须从包中的视图控制器中删除Class和Storyboard+ID，然后再添加它们，运行项目，并找到视图控制器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2400774|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If this crash occurs when accessing a view controller within a package you may have to remove the Class and Storyboard ID from the view controller within the package and then add them again, run the project and the view controller should be found

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:

<pre><code>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"
 }
}
</code></pre>

It is supposed to be all right. However, an error appears which shows:

<blockquote>
 thread1:signal SIGABRT
</blockquote>

in file AppDelegate.swift line:

<pre><code>class AppDelegate: UIResponder, UIApplicationDelegate
</code></pre>

What is wrong with my code?

Swift error : signal SIGABRT how to solve it

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我只是一个Swift编码的初学者。我的想法很简单，这是一个有两个按钮的应用程序。单击时，textfield将更改其文本。在Main.StoryBoard中，我添加了一个textfield和两个按钮。在ViewController.swift文件中。我这样写：import UIKitclass ViewControlle...

问快速误差:信号SIGABRT如何解决
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问快速误差:信号SIGABRT如何解决EN