crashlytics | 易学教程

Crashlytics WebHook for Slack is not working

阅读更多关于 Crashlytics WebHook for Slack is not working

问题 I have successfully configured Crashlytics Webhook with Slack. I have also tested it with the Test Message given in Crashlytics console. Test message working fine. But, when I have an actual crash in Crashlytics, it is not getting triggered into the Slack. I don't know where is the issue. What am I doing wrong here? 回答1: Mike from Fabric here. I responded over email, but will make the answer public as well. For this integration, you've set the impact level to 5 which means that only issues

Crashlytics task cannot be added to gradle tasks

阅读更多关于 Crashlytics task cannot be added to gradle tasks

问题 I installed Crashlytics plugin to Android Studio project, but the gradle task crashlyticsUploadDistributionDebug is not added to gradle tasks. How can I add to gradle tasks? Installing Crashlytics is successed, but the command below is failed. $ ./gradlew assembleDebug crashlyticsUploadDistributionDebug The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. FAILURE: Build failed with an exception. * What

醒醒，Android开发居然只有cv最顺手，你还会什么？

阅读更多关于醒醒，Android开发居然只有cv最顺手，你还会什么？

作为一个Android开发，现在的你已经开发多少年了？你的代码质量有没有随着经验的增加而提高？没有的话就需要反思了。现在来分享一个有六年经验Android开发，都学到了什么？一，学习能力想要成长，学习能力尤为重要我们一直有句老话，学如逆水行舟，不进则退。就像我们Android进阶，需要学习的高级内容比较多 1）Java语言进阶与Android相关技术内核像泛型，多线程，反射，JVM，Java IO，注解，序列化等 2）App开发框架知识体系（app亦对象） Android 2013~2016年的技术，大家网上Copy代码习惯了对这块经常“使用”的代码熟悉而又陌生：熟悉的是几乎天天在和它们打交道，天天在复制这些代码；陌生的是虽然天天和这些代码打交道，从未深入研究过这些代码的原理，代码深处的内涵。我们需要从新的角度去分析这些知识点，深入研究他们，要学习源码，模仿源码，然后再hook源码，这样才能说自己懂这块的知识。这些都是做Android开发，做高级工程师的基础。 3）360° Android app全方位性能调优书写高性能代码，再调优 4）Android前沿技术比如热升级，热修复，App Instant，强制更新，组件化路由架构Arouter，RxJava，IOC架构方法，Hook技术等这些技术你不能只会用，你需要知道他的原理 5）NDK 模块开发 NDK

Can't release the project using crashlytics after upgrading to java 8

阅读更多关于 Can't release the project using crashlytics after upgrading to java 8

问题 After I move to java 8 , I get this error in app release, because of fabric crashlytics: Could not determine the dependencies of task ':app:crashlyticsStoreDeobsRelease'. > Task with path 'dexRelease' not found in project ':app'. I'm using Android Studio 2.2 , Gradle version 2.14.1 , Android plugin version 2.2.0 The project run without any problem, but I can't generate signed apk! I read this post Can't run project - Android Studio 2.0 Crashlytics issues and Could not determine the

Crashlytics crash with proguard

阅读更多关于 Crashlytics crash with proguard

问题 I did everything that fabric ask in their documentation: -renamesourcefileattribute SourceFile -keepattributes *Annotation* -keepattributes SourceFile,LineNumberTable -keep public class * extends java.lang.Exception -keep class com.crashlytics.** { *; } -dontwarn com.crashlytics.** But still got this error: E/Answers: Failed to submit events task java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@d2d2a84 rejected from

xCode 9.3 and Firebase Crashlytics not working

阅读更多关于 xCode 9.3 and Firebase Crashlytics not working

问题 I cannot get Firebase Crashlytics to show my crashes of my xCode iOS Swift app. Using xCode 9.3 I have manually (not using cocoapods) integrated the Crashlytics SDK as specified here: https://firebase.google.com/docs/crashlytics/get-started?authuser=0 I have tested both in the simulator and on the device I made both crash (using an own written crash function, but also the supplied crash function), I restarted the device/simulator (because the crash is only transmitted upon the next launch) I

Unable to integrate crashlytics in eclipse with ADT

阅读更多关于 Unable to integrate crashlytics in eclipse with ADT

问题 I followed setting up plugin to integrate crashlytics from this link https://www.crashlytics.com/onboard From eclipse, I logged into my fabric account and selected my project. Plugin made necessary changes to manifest and launch activity. It asked to build & run my app to complete step 1. But I am getting - ../kit-libs/com-crashlytics-sdk-android_crashlytics/bin(missing) ../kit-libs/com-crashlytics-sdk-android_crashlytics-core/bin(missing) ../kit-libs/com-crashlytics-sdk-android_beta/bin

Android Disable Crashlytics In Library Project For Debug

阅读更多关于 Android Disable Crashlytics In Library Project For Debug

问题 I have a project with multiple modules. The common code of the modules is in a library module. The problem is that we added recently Crashlytics to our project (in the library module), and we keep receiving error reports even when we are in Debug mode. I searched on the internet and I found out that a library is always seen as a Release mode. Now my question is, is there a way to disable Crashlytics in my case? Thanks 回答1: In my app (a single module, multiple flavors), I detect the flavor,

-[NSObject(NSObject) doesNotRecognizeSelector:] crash when call -[ViewController prepareForSegue:sender:]

阅读更多关于 -[NSObject(NSObject) doesNotRecognizeSelector:] crash when call -[ViewController prepareForSegue:sender:]

问题 I am using Crashlytics to detect the crashes in my app. I occasionally get the follow crash report. The key crash point is -[NSObject(NSObject) doesNotRecognizeSelector:] and MyViewController.m line 596 -[MyViewController prepareForSegue:sender:]. I don't know what's the problem of that from the log. Is is possible a multi-threading issue? I am also using Parse SDK to retrieve the data from Parse cloud. And prepareForSegue:sender: method will be invoked when the user tap the disclosure

com.apple.NSURLSession-work EXC_BAD_ACCESS Crash debugging

阅读更多关于 com.apple.NSURLSession-work EXC_BAD_ACCESS Crash debugging

问题 I'm seeing the following crash report, but it's not reproducible. How would I go about debugging it? Is this an AFNetworking issue? I'm using version 2.4.1. Crashed: com.apple.NSURLSession-work EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0x0000000000000000 Thread : Crashed: com.apple.NSURLSession-work 0 CoreFoundation 0x0000000184aad978 CFDictionaryGetValue + 56 1 Foundation 0x0000000185aa9300 _NSSetLongLongValueAndNotify + 72 2 Foundation 0x0000000185aa9300 _NSSetLongLongValueAndNotify + 72 3