crashlytics

I have exported my Unity project to be able to use multidex. Problem is I have to set the android:name in the project's androidmanifest to "android.support.multidex.MultiDexApplication" when I already have this "io.fabric.unity.android.FabricApplication" set for fabric. I have tried initializing Fabric manually but then I get this error : AndroidJavaException: io.fabric.unity.android.FabricInitializationException: Fabric did not find a valid application context. I have found that someone had a similar problem but it didn't got solved: https://twittercommunity.com/t/unity-android-plugin

Fatal signal 11 (SIGSEGV), code 1, fault addr 0x48 in tid 21741 (RenderThread) in occured in the rearest case in some device.If anyone knows please answer.Due to this error android application crash at every activity. <activity android:name=".HomeActivity"/> crash ankit Solved. just add: android:hardwareAccelerated="false" in manifest file in activity <activity android:hardwareAccelerated="false" android:name=".HomeActivity"/> Reference: Hardware Acceleration . 来源： https://stackoverflow.com/questions/42966459/fatal-signal-11-sigsegv-code-1-fault-addr-0x48-in-tid-21741-renderthread-i

In my app there are two targets: Target 1 : MyApp - com.app.myapp Target 2 : MyAppQA - com.app.myappQa Email Id used for Fabric registration is same for both targets. I have created two apps using Fabric mac app . In MyApp Target Fabric is catching all the crash and working fine. But When I run using target MyAppQA then I am getting Missing DYSM file error. I am not able to get why crash is not captured in my second target. Here is the method which I tried: BitCode - Disabled (Although I am not using bitcode but even then I crosschecked) Debug Information Format - Set to DWARF with dSYM File

Everything works fine when I initialize my application with: Fabric.with(this, new Crashlytics()); However, I get an exception when I use: Fabric.with(this, new CrashlyticsCore()); The following exception: FATAL EXCEPTION: main Process: com.weightbook, PID: 19438 java.lang.IllegalStateException: Crashlytics must be initialized by calling Fabric.with(Context) prior to calling Crashlytics.getInstance() at com.crashlytics.android.Crashlytics.checkInitialized(Crashlytics.java:372) at com.crashlytics.android.Crashlytics.setUserName(Crashlytics.java:248) at com.weightbook.analytics.AnalyticsManager

Recently, we've upgraded our organization's Crashlytics account to Fabric, and I'm trying to replace the old Crashlytics SDK with the new Fabric SDK in our existing apps. I've followed the migration instructions , and it's been largely painless, except that I'm now receiving a build error when I try to compile. The line in question that's causing the error is the bootstrap call: Fabric.with(this, new Crashlytics()); The error that's being returned is: Error:(55, 11) error: no suitable method found for with(MyActivity,Crashlytics) method Fabric.with(Fabric) is not applicable (actual and formal

I have this stack trace in Fabric: My question : From the crash log, is the function 'formatMessageAuthorName' the only cause for this EXC_BREAKPOINT crash? E.g., are there other possible causes for the crash apart from the code inside this function? Here is my formatMessageAuthorName function: private static func formatMessageAuthorName(firstname: String, lastname: String?=nil) -> String { // Capitalise first character of firstname var Cap_firstname = firstname Cap_firstname.replaceRange(Cap_firstname.startIndex...Cap_firstname.startIndex, with: String(Cap_firstname[Cap_firstname.startIndex])

I have updated the Crashlytics but still I am getting this error on launch: Error: *** Terminating app due to uncaught exception 'FABException', reason: '[Fabric] It appears that "Crashlytics" is not a valid Fabric Kit. Please make sure you only pass Fabric Kits to [Fabric with:].' Here is my code: func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool { // Override point for customization after application launch. Fabric.with([Crashlytics.self]) return true } I was having a crash on the same line, and it was because I called