blocks|key|679657|text|在实际设备上以调试模式运行应用程序。按“主页”按钮将应用程序发送到后台并继续调试。然后，您可以将应用程序带到前台并继续调试，或者在applicationWillEnterForeground上放置一个断点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|679658|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|$]]

Run the app in debug mode on a real device. Press the Home button to send the app to background and continue the debugging. Then you can bring the app to foreground and keep debugging, or put a breakpoint at applicationWillEnterForeground.

blocks|key|679705|text|这些事情可能会很艰难，我从类似的经历中知道。在不了解你的应用程序的情况下，我只能提供提示而没有明确的答案，但也许这对你有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|679706|尽管有两种尝试“捕获”进程的方法，但使用print直接日志记录的方法却是落后和乏味的。|offset|length|style|CODE|679707|然而，首先，我要强调，“背景”并不总是一样的，不幸的是，人们使用这个词往往很松散。取决于导致崩溃的状态转换，您可能会运气不佳，必须使用手动日志进行简单的实验。应用程序可以在后台，即不在前台，但仍在运行。在附加调试器时通常是这种情况，否则调试器无法完成它的工作。或者，它们可以被操作系统暂停(甚至终止)。调试器可以防止这种情况，您可能已经知道了。|679708|对你有帮助的两件事是：|679709|如果您使用后台提取，即“从后台模式返回”(正如您描述的那样)，那么您可以在构建方案的"Run“配置部分激活”由于后台获取事件而启动“选项。|ordered-list-item|679710|从主屏幕上运行你的应用程序，用Home按钮把它放到后台，等一会儿(你可能已经这样做了，以获得崩溃何时会发生的感觉)。您的应用程序最终会进入暂停状态(但您没有办法在任何地方看到AFAIK)。与其通过多任务UI再次将其附加到前台，不如通过“调试附加到进程”菜单再次附加调试器。这将使您的应用程序从挂起状态返回到后台状态，在该状态下，崩溃可能真的发生(如果从后台到前台，您可能会像往常一样调试它)。希望调试器能及时完成对它的附加，否则我就没有想法了。:(|679711|我本人还没有遇到过这个问题，但我知道背景问题可能会很棘手。也许这讨论对你也有帮助(我也从那里获取了我的部分信息)。|679712|entityMap|0|LINK|mutability|MUTABLE|url|https://forums.developer.apple.com/thread/14855^0|0|K|5|0|0|0|0|0|V|1|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|16|8|@]|9|@]|A|$]]|$1|O|3|P|5|N|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|18|8|@]|9|@$D|19|E|1A|1|1B]]|A|$]]|$1|S|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

These things can be tough, I know that from similar experiences. Without knowing more about your app I can only offer hints and no definitive answer, but perhaps this helps you.

The fallback and tedious approach to use direct logging with <code>print</code> and so on notwithstanding there are a two ways to try to "catch" a process.

However, first let me stress that "background" is not always the same and people unfortunately use the term often loosely. Depending on what state transition causes your crash you might run out of luck and have to simply experiment using manual logging. Apps can be in background, i.e. not in the foreground, but still running. This is usually the case when the debugger is attached, otherwise it couldn't do its job. Alternatively they can be suspended (or even terminated) by the OS. The debugger prevents this, which you probably already figured out.

The two things that might help you are:

<ol>
<li>If you're using background fetch, i.e. "coming back from background mode" as you describe it happens automatically you can activate the "Launch due to a background fetch event" option in your build scheme's "Run" configuration section. </li>
<li>Run your app from the Home screen, put it into background with the Home button and wait a bit (you've probably done so in the past already to get a feeling for when the crash would happen). Your app should eventually go into the suspended state (but you have no way to actually see that anywhere AFAIK). Instead of getting it to the foreground again via the multitasking UI, simply attach the debugger again via the "Debug - Attach to process" menu. This should get your app from the suspended state back into the background state, where the crash probably really happens (if it were to happen when coming from background to foreground you probably would have been able to debug it as usual). Hopefully the debugger has finished attaching to it in time, otherwise I'm out of ideas. :(</li>
</ol>

I haven't run into this specific problem myself personally, but I know background stuff can be tricky. Maybe <a href="https://forums.developer.apple.com/thread/14855" rel="nofollow noreferrer">this</a> discussion also helps you (I took part of my info from there as well).

blocks|key|1493149|text|你不能在真正的设备上调试这个。当调试器被附加时，您的应用程序将永远不会进入真实设备中的后台模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1493150|您可以尝试在模拟器上调试此功能。无论如何，请检查类属性，并将属性设置为“强”，以确保这不会因为缺少属性而发生。|1493151|我读过几个StackOverflow问题，这些问题都有FBApplicationProcess。通常情况下，这是在应用程序启动时缺少数组之类的。|1493152|诚挚的问候。|1493153|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

You can't debug this on the real device. When the debugger is attached, your apps will never go to background mode in the real device.

You can try to debug this on a simulator. 
Anyway please check your class attributes and set attributes to strong to make sure this is not happened by missing attributes.

I have read several StackOverflow questions that have FBApplicationProcess. Usually, this one happened by missing array or something when the app started.

Best regards.

blocks|key|2124146|text|我已经看过了以上所有的答案，并且都给出了正确的答案。不过，我想表达我的观点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2124147|如果该应用程序运行在任何具有调试模式和有线插件甚至模拟器上的iOS真实设备上，应用程序将永远不会出现在后台。|ordered-list-item|2124148|如果应用程序在没有有线插件的情况下运行，或者没有Xcode运行(直接在iPhone中启动应用程序)，然后将应用程序放在后台，则应用程序将在接下来的3分钟内运行。3分钟后，应用程序将自动挂起并从主线程中删除。现在，当我们再次打开应用程序，它将被认为是一个新的推出。|2124149|如果你的应用程序有任何背景功能，那么你的应用程序即使在后台也是活的，但是在这段时间里你不能做任何UI更改。|2124150|为了在后台保持应用程序的活力，必须正确地处理后台功能。即。如果在您的应用程序中使用“时间-应用程序处于前台”状态的位置，则应用程序在后台运行的时间不会超过3分钟。所以，如果你想在后台连续运行你的应用程序，你必须在Info.plist文件中用电池漏字来表示正确的原因，否则苹果会拒绝它。|2124151|想了解你问题的更多细节。|2124152|谢谢。|2124153|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|V|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|W|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|P|$]]

I have gone through all the above answers and all have given proper answers. Though, I would like to share my point of view.

<ol>
<li>If the app is running on any iOS real device with debug mode and wire plug-in or even on Simulator, App will never go in the background. </li>
<li>If the app is running without wire plug-in or run without Xcode(directly launch the app in iPhone) and then put the app in the background, the app will be running in the background of next 3 mins. After 3 mins, the App will automatically be suspended and removed from the main thread. Now, when we open the app again, It will be considered a fresh launch.</li>
<li>If your app having any Background Capabilities ON, then your app will be alive even in the background, but you can't do any UI changes during that time. </li>
<li>To keep app alive in the background, Background Capabilities must be handled properly. ie. If Location is used in your app with 'While-App is in Foreground' condition, app will not run more than 3 mins in background. So, If you want to run your app continuously in background, you must have to represent proper reason in Info.plist file with Battery drain word, or else, Apple will reject it.</li>
<li>Ping me for more detail on your question.</li>
</ol>

Thanks.

blocks|key|2124162|text|您的测试设备上仍然有崩溃日志。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2124163|要获得崩溃日志，请尝试以下步骤：|2124164|通过USB连接您的测试设备到Mac。|unordered-list-item|2124165|启动Xcode。转到Windows+>设备和模拟器。|2124166|从屏幕左侧的“设备”部分选择您的设备。|2124167|选择“查看设备日志”按钮。|2124168|标识并选择崩溃日志以查看内容。|2124169|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|V|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|W|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|P|$]]

Crash logs still available on your test device.

To get the crash log try the following steps:

<ul>
<li>Connect your test device to the Mac through USB.</li>
<li>Launch Xcode. Go to Windows > Devices and Simulators.</li>
<li>Choose your device from the devices section on the left side of the screen.</li>
<li>Select View Device Logs button.</li>
<li>Identify and select the Crash Log to see the contents.</li>
</ul>

There is a crash happen when coming back from background through app icon.

However I cannot see any detail info in console log. There is a signal to terminate, but we cannot find signal number.

<pre><code>&lt;FBApplicationProcess: 0x117bcb930; Maixxxx; pid: 1762&gt; exited abnormally via signal.

Process exited: &lt;FBApplicationProcess: 0x117bcb930; Maixxx; pid: -1&gt; -&gt; &lt;FBApplicationProcessExitContext: 0x17103f820; exitReason: signal; terminationReason: (none)&gt;
</code></pre>

<a href="https://i.stack.imgur.com/qjJc3.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/qjJc3.jpg" alt="console log"></a>

The procedures to reproduce my crash is as follow:

<ol>
<li>Start app through click on app icon.</li>
<li>Use the app as normal user.</li>
<li>Press home to put it in background.</li>
<li>Wait for some minutes.</li>
<li>Click the app icon on springboard screen in order to use it again.</li>
<li>The app crash&amp;exit.</li>
</ol>

Since the crash only happen when coming back from background, and required to enter background for some minutes, I cannot run in debug mode with lldb attached.

I didn't use any of background features.

Also, I didn't see any crash report in Fabric's Crashlytics. So I think signal handler could not be called neither?

How to investigate this kind of problem?

How to debug a crash which happened when come back from background

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

当从后台通过应用程序图标返回时，就会发生崩溃。但是，我在控制台日志中看不到任何详细信息。有信号要终止，但我们找不到信号号码。<FBApplicationProcess: 0x117bcb930; Maixxxx; pid: 1762> exited abnormally via signal.Process exite...

问如何调试从后台返回时发生的崩溃
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何调试从后台返回时发生的崩溃EN