2014-03-27 58 views
0

我正在使用Flurry Analytics和Xamarin.iOS編寫iOS應用程序。我使用here(Flurry SDK 4.2.3)的綁定。在FinishedLaunching()方法覆蓋我呼籲:Flurry和Monotouch的崩潰報告

Flurry.SetCrashReportingEnabled(true); 
Flurry.StartSession(FlurryAPIKey); 

一切都編譯和啓動成功。 後真實的數據顯示在儀表盤亂舞我看到許多錯誤,用相同的調用堆棧:

0 Fines        0x0049e500 -[FlurryPLCrashReporterConfig symbolicationStrategy] + 4334767 
1 Fines        0x0049e61c -[FlurryPLCrashReporterConfig symbolicationStrategy] + 4335051 
2 Fines        0x0049e908 -[FlurryPLCrashReporterConfig symbolicationStrategy] + 4335799 
... 
30 Fines        0x00685c53 -[FlurryPLCrashReporterConfig symbolicationStrategy] + 6331394 
31 libsystem_pthread.dylib    0x38a90919 <redacted> + 140 
32 libsystem_pthread.dylib    0x38a9088b __pthread_start + 102 
33 libsystem_pthread.dylib    0x38a8eaa4 _thread_start + 8 

是什麼調用堆棧是什麼意思?用Monotouch和Flurry跟蹤所有未處理的異常的正確方法是什麼?

回答

0

從亂舞FAQ:

My strack traces are de-symbolicated/obfuscated.
For iOS applications we have partnered with Plausible Labs to create an innovative technology that re-symbolicates most of the stack trace in the application itself so you do not need to provide a desym file to use the service. We also provide ways to upload your desym file to improve your stack trace detail and to support Android applications. On the stack trace detail page, there is the option to upload either the dsym file (iOS) or the Proguard mapping file (Android). Once you upload the file, we’ll try and symbolicate the stack traces for you.

DSYM文件意味着擴展名的文件.dSYM它應該與你的.ipa構建的文件夾中。另外dSYM文件是每個新版本的uniq,不要忘記保存在dsym文件的某個地方。

+0

問題不在desymbolication階段。錯誤本身發送不正確。看起來像特定的單聲道。 – alexey