【发布时间】：2019-09-25 21:39:46
【问题描述】：
我经常在 Firebase Crashlytics 中发生崩溃（在 Sentry 上测试 - 相同），但没有任何有意义的崩溃消息。所有这些 SIGABRT ABORT 0x、EXC_BREAKPOINT 0x 等。我是 iOS 和原生开发的新手（通常用于 Android 和 .NET 运行时，除了堆栈跟踪之外，您还会收到错误消息）。我是否想念 smth 并且这是 iOS 生产版本的常见内容？如果是这样，如何调试呢？只是堆栈跟踪和行号并不能准确回答发生了什么。我可以期望行号至少 100% 正确吗？
通常的崩溃如下所示：
Crash: Thread #1
EXC_BREAKPOINT 0x00000001011e3d78
Crashed: Thread
0 App 0x1011e3d78 TrackMyLocationService.determinateActivityType(withGeoCoordinate:) + 154 (TrackMyLocationService.swift:154)
1 App 0x1011e2b70 closure #1 in TrackMyLocationService.start() (<compiler-generated>)
2 App 0x1011c3e8c thunk for @escaping @callee_guaranteed (@guaranteed CLLocation, @unowned Bool) -> () (<compiler-generated>)
3 RxSwift 0x1035415f0 closure #1 in ObservableType.subscribe(onNext:onError:onCompleted:onDisposed:) (<compiler-generated>)
4 RxSwift 0x1035417f0 partial apply for closure #1 in ObservableType.subscribe(onNext:onError:onCompleted:onDisposed:) (<compiler-generated>)
5 RxSwift 0x1034f7360 AnonymousObserver.onCore(_:) (<compiler-generated>)
6 RxSwift 0x103544068 ObserverBase.on(_:) + 25 (ObserverBase.swift:25)
7 RxSwift 0x1035441b8 protocol witness for ObserverType.on(_:) in conformance ObserverBase<A> (<compiler-generated>)
8 RxSwift 0x103542bdc ObserveOnSink.run(_:_:) + 118 (ObserveOn.swift:118)
9 RxSwift 0x103543e40 partial apply for thunk for @escaping @callee_guaranteed (@unowned @callee_guaranteed () -> ()) -> () (<compiler-generated>)
10 RxSwift 0x103551c4c partial apply for thunk for @escaping @callee_guaranteed (@in_guaranteed A, @unowned @callee_guaranteed (@in_guaranteed A) -> ()) -> () (<compiler-generated>)
11 RxSwift 0x103551238 closure #1 in RecursiveImmediateScheduler.schedule(_:) (<compiler-generated>)
12 App 0x1010bc71c partial apply for thunk for @escaping @callee_guaranteed (@in_guaranteed ()) -> (@out Disposable) (<compiler-generated>)
13 App 0x1010bc8a8 partial apply for thunk for @escaping @callee_guaranteed () -> (@out Disposable) (<compiler-generated>)
14 App 0x1010bc71c partial apply for thunk for @escaping @callee_guaranteed (@in_guaranteed ()) -> (@out Disposable) (<compiler-generated>)
15 App 0x1010bc8a8 partial apply for thunk for @escaping @callee_guaranteed () -> (@out Disposable) (<compiler-generated>)
16 App 0x1010bc50c closure #1 in SingleBackgroundThreadScheduler.work() (<compiler-generated>)
17 App 0x1010bc870 partial apply for thunk for @callee_guaranteed () -> (@error @owned Error) (<compiler-generated>)
18 libswiftObjectiveC.dylib 0x1e21f9d3c autoreleasepool<A>(invoking:) + 64
19 ??? 0x59ca81010bc424 (Missing)
20 App 0x1010bc788 partial apply (<compiler-generated>)
21 App 0x10127da1c thunk for @escaping @callee_guaranteed () -> () (<compiler-generated>)
22 CoreFoundation 0x1b357549c <redacted> + 24
23 ??? 0x27df01b3fd061c (Missing)
24 ??? 0x755881b4106c54 (Missing)
【问题讨论】：
-
您能否分享更多有关崩溃的详细信息以及您的应用在哪个过程中崩溃？
-
你添加了观察者吗？
-
是的。这只是一个示例崩溃。问题的关键不是特定的崩溃。关键是 iOS 世界在生产崩溃中错过错误消息的常见情况有多少。对于 .NET，这很不寻常。
标签： ios crashlytics