crashlytics

Crashlytics not transmitting crash event to Fabric.io (Debug mode only?)

一笑奈何 提交于 2019-12-11 07:43:46
问题 I'm having a problem similar to [xCode 9.3 and Firebase Crashlytics not working. I am able to force a crash in the debug version of the main app and the crash appears in the console on Fabric.io. I have also made a way (using an "Easter egg") to force a crash in the framework code. I have tried three different approaches. The first two are attempts to simulate a "real" crash originating in the framework code itself. The third uses a "bogus" callback to the main app. Note that in the code

Catch native crash: signal 7 (SIGBUS), code 2 (BUS_ADRERR)

纵饮孤独 提交于 2019-12-11 07:07:48
问题 On my Google Play Console I've got some reports for an application (FYI, it also uses JNI). This is the backtrace: native: pc 00000000002c0536 /system/lib/libart.so (_ZN3artL16Unsafe_putDoubleEP7_JNIEnvP8_jobjectS3_xd+31) native: pc 0000000073bb9609 /data/dalvik-cache/arm/system@framework@boot.oat I am not able to catch it with any crash reporting system (Google Analytics, Crashlytics) and of course have no clue on how to reproduce it. Interestingly, the devices affected for most are the ones

Fabric Crashlytics “Hmmm, seems like your kit isn't activating” whilst verifying install

大城市里の小女人 提交于 2019-12-11 06:27:18
问题 I am currently awaiting beta testing for my new app. I chose Fabric due to it's great reviews. However i am current getting the "Hmmm, seems like your kit isn't activating" message on the Fabric Controller after following the instruction to run the app in Xcode. I have looked around but the solutions i have found haven't made any difference. This is the message i am getting: This is my run script: This is my info.plist: And finally this is my code in the App Delegate: import UIKit import

Crashlytics report from exception in framework

感情迁移 提交于 2019-12-11 06:19:04
问题 I have an app and two app extensions (keyboard and iMessage extensions) that use three frameworks which we built. The frameworks are part of the project and each have their own target. The app and the extensions link in these frameworks and we use them to perform common tasks like accessing a database. If we have Crashlytics initialized in the AppDelegate like this func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey : Any]

Fabric missing DSYMs even though log says it uploaded them

走远了吗. 提交于 2019-12-11 05:44:14
问题 For my iOS app I use Jenkins to distribute my test builds. I use Fabric for crash reporting. I run the post build scripts on Jenkins to upload ipa, release notes and DSYMs to Fabric. This is the script I run to upload DSYMs: ${WORKSPACE}/Pods/Fabric/upload-symbols -a {api-key} -p ios ${WORKSPACE}/artifacts/TestDebug-iphoneos/${PROJECT_NAME}.app.dSYM source for the script In the build logs on Jenkins I see: upload-symbols[91261:22647730] Successfully submitted symbols for architecture arm64

Not receiving crashes on crashlytics while do internal testing

让人想犯罪 __ 提交于 2019-12-11 04:56:36
问题 I have integrated crashlytics with the pod. I used to test application with Testflight. I have noticed that there were few crashed on iTunes connect but Did not received any email from fabric/crashlytics. I Try app crash manually like exit(1) and I received an email on very next launch of the application. So assuming that crashlytics framework integrated successfully. Do you have any suggestion where I suppose to look? 回答1: Mike from Fabric here. Our email notifications will not be sent on

Fabric/Crashlytics - No data and crash reports for iOS

僤鯓⒐⒋嵵緔 提交于 2019-12-11 04:36:29
问题 I followed all the Fabric documentation concerning crash reports for iOS. I can see my first crash test on the dashboard, but now the App is on the AppStore, and I see no crashes, no active users, no data at all on the Fabric App. But I know there are a lot of users right now, we can see all the stats for Android. How can we make this solution working for iOS ? 回答1: you might want to check 3 things: missing dYSIM runscript plist 来源: https://stackoverflow.com/questions/41160661/fabric

Crashlytics doesn't work with Xcode 10 beta

空扰寡人 提交于 2019-12-11 02:57:26
问题 I use Firestore and some of sub-services Google offers. Crashlytics is one of them. I recently started to use Xcode 10 beta and I've started to receive this error: /Users/<user>/<some folders>/Pods/Fabric/iOS/Fabric.framework/Fabric(FABCompoundOperation.o) ld: 154 duplicate symbols for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) And Build Phase stuff: Here is Embed Pods Frameworks: How to fix this? P.S. I already cleaned and tried to

Could not execute build using Gradle with Crashlytics

こ雲淡風輕ζ 提交于 2019-12-11 01:26:57
问题 I'm trying to integrate my current projects with crashlytics, i'm following this step. my build gradle is : buildscript { repositories { mavenCentral() maven { url 'http://download.crashlytics.com/maven' } } dependencies { classpath 'com.android.tools.build:gradle:0.8.+' classpath 'com.crashlytics.tools.gradle:crashlytics-gradle:1.+' classpath 'com.neenbedankt.gradle.plugins:android-apt:1.1' } } apply plugin: 'android' apply plugin: 'crashlytics' apply plugin: 'android-apt' repositories {

As of Crashlytics 3.0.0, implementing a user prompt is the application's responsibility

大城市里の小女人 提交于 2019-12-10 21:31:35
问题 I am getting the following warning: [Crashlytics:Crash] WARNING: the user prompt feature is enabled. As of Crashlytics 3.0.0, implementing a user prompt is the application's responsibility. See Crashlytics.h's notes about -crashlyticsDidDetectReportForLastExecution:completionHandler: appearing in my app's log when I run it with Xcode. It looks like the version of Crashlytics I'm using is 3.0.8 (from the info.plist file in the Crashlytics.framework). Here's the relevant doc from the