EXC_BREAKPOINT<redacted>如何调试？
EXC_BREAKPOINT<redacted> how to debug?
我们最近向我们的用户群发布了我们的应用程序，我们在 Sentry 中看到了一堆编辑过的异常，我们无法以任何逻辑方式进行调试。
这些异常似乎唯一的共同点是它们永远不会在应用程序处于活动状态时发生：
并且这些设备上的可用内存似乎非常低：
我们的一个理论是 OS 由于可用内存不足而决定关闭所有后台应用程序。
但是当我更倾向于相信我们在自己的代码中犯了错误时，在这些时候做出一个相当大的假设。
关于我的问题，我们将如何着手调试这些编辑过的异常？我们是否正确地认为我们的应用程序在不活动时被关闭是没有理由担心的？
Sentry 的本地版本有几个与此特定问题相关的问题。根据 Sentry 团队的说法，这些问题将在即将发布的本地版本中得到修复。但总结一下。
起初我们很难让 dSYM 的上传脚本正常工作。 here 提到的 fastlane 车道根本不起作用。哨兵界面调试符号下提示的bash脚本也没有。
有用的是使用 sentry-cli（最新版本）并增加可接受的文件大小以上传到我们的本地 nginx 服务器。但是在成功让我们的 dSYMs 文件实际显示在 Sentry 中之后，我们遇到了更多问题。
我们遇到的问题如下所列：
A required debug symbol file was missing
@johan12345 Sorry for getting back to you so late. We've verified your debug symbols and can confirm they should process and symbolicate correctly. The issue you are referring to has been fixed a while back in both sentry-cli and sentry and will be available with the next release.
We have been preparing a major launch over the last couple of months which is why there have been no releases recently. However, since we've received a couple of requests regarding symbolication for on-premise customers, we will try to push a new release out soon. I cannot give you an exact timeline, though, so please stay tuned.
Again, I'm very sorry for the inconvenience this might have caused.
https://github.com/getsentry/sentry/issues/7595
Reprocessing 12 events …
Some users are reporting sometimes to be stuck on reprocessing. Mostly happens with self-installations but we also had two support issues.
This seems to be triggered by internal server errors in the processing pipeline in bad places.
Related: https://forum.sentry.io/t/stuck-there-are-x-events-pending-reprocessing/1518/6
https://github.com/getsentry/sentry/issues/5862
We've added a new button called "Discard all" which can be found above your processing issues list.
This will discard all processing issues and the corresponding events.
We've also found an error in our processing pipeline we've yet to fix.
I will close this issue for now and link new issues regarding processing errors later.
So the only thing I can advise you right now is basically deploy the master branch of Sentry because our last release was in November and we fixed a bunch of stuff since then.
Not sure if we release a new version before Sentry 9 (which still needs some time).
https://forum.sentry.io/t/ios-exceptions-shows-up-as-redacted/3681
TLDR：我们正在切换到 Crashlytics
我们最近向我们的用户群发布了我们的应用程序，我们在 Sentry 中看到了一堆编辑过的异常，我们无法以任何逻辑方式进行调试。
这些异常似乎唯一的共同点是它们永远不会在应用程序处于活动状态时发生：
并且这些设备上的可用内存似乎非常低：
我们的一个理论是 OS 由于可用内存不足而决定关闭所有后台应用程序。
但是当我更倾向于相信我们在自己的代码中犯了错误时，在这些时候做出一个相当大的假设。
关于我的问题，我们将如何着手调试这些编辑过的异常？我们是否正确地认为我们的应用程序在不活动时被关闭是没有理由担心的？
Sentry 的本地版本有几个与此特定问题相关的问题。根据 Sentry 团队的说法，这些问题将在即将发布的本地版本中得到修复。但总结一下。
起初我们很难让 dSYM 的上传脚本正常工作。 here 提到的 fastlane 车道根本不起作用。哨兵界面调试符号下提示的bash脚本也没有。
有用的是使用 sentry-cli（最新版本）并增加可接受的文件大小以上传到我们的本地 nginx 服务器。但是在成功让我们的 dSYMs 文件实际显示在 Sentry 中之后，我们遇到了更多问题。
我们遇到的问题如下所列：
A required debug symbol file was missing
@johan12345 Sorry for getting back to you so late. We've verified your debug symbols and can confirm they should process and symbolicate correctly. The issue you are referring to has been fixed a while back in both sentry-cli and sentry and will be available with the next release.
We have been preparing a major launch over the last couple of months which is why there have been no releases recently. However, since we've received a couple of requests regarding symbolication for on-premise customers, we will try to push a new release out soon. I cannot give you an exact timeline, though, so please stay tuned.
Again, I'm very sorry for the inconvenience this might have caused.
https://github.com/getsentry/sentry/issues/7595
Reprocessing 12 events …
Some users are reporting sometimes to be stuck on reprocessing. Mostly happens with self-installations but we also had two support issues.
This seems to be triggered by internal server errors in the processing pipeline in bad places.
Related: https://forum.sentry.io/t/stuck-there-are-x-events-pending-reprocessing/1518/6
https://github.com/getsentry/sentry/issues/5862
We've added a new button called "Discard all" which can be found above your processing issues list. This will discard all processing issues and the corresponding events. We've also found an error in our processing pipeline we've yet to fix. I will close this issue for now and link new issues regarding processing errors later.
So the only thing I can advise you right now is basically deploy the master branch of Sentry because our last release was in November and we fixed a bunch of stuff since then.
Not sure if we release a new version before Sentry 9 (which still needs some time).
https://forum.sentry.io/t/ios-exceptions-shows-up-as-redacted/3681
TLDR：我们正在切换到 Crashlytics