crashlytics

问题 I tried to integrate Crashlytics for iOS into an IBM Worklight 6.1 project, but I have got an error related to sqlcipher.framework. Does this means that Crashlytics and Worklight are not compatible? For info, you can know more about Crashlytics at: https://get.fabric.io/crashlytics The error that I am getting is: ld: warning: directory not found for option '-F"/Users/myUsername/MyProjectPath/ProjectName/apps/AppName/iphone/native/Frameworks"' ld: framework not found sqlcipher clang: error:

问题 Everytime I release a new version of an app, this version shows up in Fabric crashlytics service, and I can track crashes, non-fatals, etc. My issue is that I released a version on monday (11/19/18) but the version number is not showing up in crashes version filter. The next version (not on the store yet, but on testflight) is showing tho. I have no idea how this is possible, if it comes from changes in fabric/firebase, or if it's coming from me (I don't see a thing I did differently than

问题 Crashlytics does not report crash event to Fabric for Xcode 10 or higher and iOS 12 or higher. 回答1: To report crash to Fabric from Xcode 10 and iOS 12 or higher Step 1: Go to Build Settings Search "Debug Information Format" Change value of "Debug" from "DWARF" to "DWARF with dSYM File" Build your project again. Step 2: Set absolute path of Info.plist in "Input Files" - Add/Change "Input Files" value in Run Script added for Fabric under "Build Phases" - From "$(BUILT_PRODUCTS_DIR)/$(INFOPLIST

问题 I've created OOM crashes by growing an infinitely large NSArray of NSStrings, and I've even tried calling exit(0) just to make it look like an OOM. While these things to have worked to terminate the app unexpectedly, I don't see any OOMs reported on Crashlytics and it doesn't call the delegate callback, crashlyticsDidDetectReportForLastExecution: , on the next run of the app. I'm running the app on a real device that is not connected to a simulator, and any other kind of crash/error it

问题 There are two ways to log to Crashlytics according to the documentation. Crashlytics.log(int priority, String tag, String msg); In addition to writing to the next crash report, it will also write to the LogCat using android.util.Log.println(priority, tag, msg) . Crashlytics.log(msg); which will only write to the Crashlytics crash report [not logcat]. However, this second method does not allow me to set a tag and priority. Instead it automatically sets the resulting tag as "CrashlyticsCore"

问题 I am trying to set user information to crash reports in crashlytics in Android App, so that it will help me to find out which of our users experienced a given crash. I have explored and found there are 3 APIs can set user information in crash report. Those are, void Crashlytics.setUserIdentifier(String identifier); void Crashlytics.setUserName(String name); void Crashlytics.setUserEmail(String email); It is recommended to use all the APIs. All documented at http://support.crashlytics.com

问题 I have an Android project that uses the Crashlytics with Fabric plugin on the Android Studio , set up the proxy for the files : studio64.exe.vmoptions : -Dhttps.proxyPort=8080 -Dhttps.proxyHost=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -Dhttps.proxyUser=xxxxx -Dhttps.proxyPassword=xxxxxxxx gradle.properties: systemProp.http.proxyPassword=xxxxx systemProp.http.proxyHost=proxy-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx systemProp.http.proxyUser=xxxxxxxx systemProp.http.proxyPort=8080 systemProp.https

问题 Found Crashlytics.app issue. App not handling Xcode Build Success notification. To resolve this issue set "Build Settings -> Debug information format -> DWARF with dSYM File" for Debug mode. 来源： https://stackoverflow.com/questions/53652476/crashlytics-app-add-new-app-stuck-on-add-run-script-step

问题 I have setup all these steps and bundel id on Firesbase Dashboard and tried crash many times but not getting any report. pod 'Firebase/Core' pod 'Fabric', '~> 1.7.2' pod 'Crashlytics', '~> 3.9.3' In Build phase added run Script : "${PODS_ROOT}/Fabric/run" Debug Inforation Format : DWARF with dSYM File running in simulator with following steps (IBAction)crashButtonTapped:(id)sender { [[Crashlytics sharedInstance] crash]; } Click play_arrow Build and then run the current scheme in Xcode to

问题 After reading numerous beta testing strategy guides for iOS I'm still confused about if it's permitted by Apple's Developer Program to distribute an app for external beta testing without getting it approved by them and using TestFlight. For example, is it allowed to create an AdHoc signed app and use a 3rd party tool (Crashlytics, HockeyApp, others) to beta distribute to external entities. External in this case meaning not within your organization. Within an organization, there are other