crashlytics

react-native-firebase crashlytics not showing up on firebase dashboard

这一生的挚爱 提交于 2019-12-09 17:18:03
问题 I am using firebase crashlytics. I am causing a crash by doing firebase.crashlytics().crash() and I am not seeing the crash report on the firebase dashboard. The crash is working because on android i get this screen and on ios the app freezes and i get brought to this page on xcode But on the crashlytics dashboard on firebase the crashes are not showing up. Is there any reason why the crashes are not showing up on crashlytics dashboard? I am using react-native-firebase. I know i installed it

iOS xcode 5 crashlytics error - Shell Script Invocation Error - ./Crashlytics.framework/run: Permission denied

早过忘川 提交于 2019-12-09 14:20:06
问题 I have Crashlytics Framework added to my project, with a script. Run script: Shell: /bin/sh Script: ./Crashlytics.framework/run KEY_HERE When I try to run the project, I get the following error: Shell Script Invocation Error - ./Crashlytics.framework/run: Permission denied BUT if i delete the framework and add it again, it runs fine... ONCE. Then the next time I get the same error. Then i have to delete it, and re-add it, for it to only run once, and then the same story... Does anybody have

Crashlytics. Project dev is inactive

青春壹個敷衍的年華 提交于 2019-12-09 14:19:34
问题 When I'm trying to upload new flavor build, I get an error: WARN - Crashlytics had a problem uploading the distribution. Project dev is inactive How can I fix it and add new flavor for tests? 回答1: From another users response on Stackoverflow: That means your project hasn't been fully activated on the Fabric backend. After building your app, be sure to run the app as well. This will finish the activation so that you can then distribute your app. Running the app fixed the problem for me. 回答2:

Fabric Beta and APK splits

感情迁移 提交于 2019-12-09 11:36:19
问题 I'm splitting my app based on ABI, not on density, like so: splits { abi { enable true reset() include 'x86', 'armeabi', 'armeabi-v7a', 'mips', 'arm64-v8a' universalApk true } } I have multiple flavors, and 2 build types (debug and release). I want to put the universal apk file, that has native libs for all platforms, up on fabric beta. From what I understand, this is supported through the ext.betaDistributionApkFilePath attribute. I can define this either at the buildType level, or at the

Beta from Crashlytics fail to install build on testers' devices

大城市里の小女人 提交于 2019-12-09 07:23:11
问题 I'm sending my app to testers with Beta from Crashlytics which is an amazing tool to do app testing. I had every new tester's device UDID registered in my developer account and then distribute a new build. My testers got email invitation and accessed app's installation which could not be completed on their device. They kept seeing an alert showing up with message: Unable to download app - MyApp could not be installed at this time - Done / Retry Testers' testing status are " installed " in my

Scope of causes for EXC_BREAKPOINT crash

旧时模样 提交于 2019-12-09 03:29:27
问题 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

What's a good setup for React Native crash reporting? [closed]

心不动则不痛 提交于 2019-12-08 22:09:36
问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 3 years ago . I'm seeing that getSentry has crash reporting for React Native now: https://docs.getsentry.com/hosted/clients/javascript/integrations/react-native/ I like them because they do a good job correlating exceptions with your source maps. But I also want to catch native crashes. Do you

Fabric (Crashlytics): Newest build not visible in 'Latest release' section

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-08 20:37:57
问题 After the new version (3.5.9) of the app has been in production for couple of days, it is visible in Crashlytics secion of Fabric: but is not in 'Latest Release': What's interesting, on the top there is an old version of the app that isn't used that much now. What could be the reason of such behaviour? 回答1: I've reached out to Fabric support and got an answer: The Latest Releases page shows all builds that have been used by at least 10% of your Daily Active Users (DAU) on any single day in

Issue with Crashlytics and Answers kit

十年热恋 提交于 2019-12-08 20:21:07
问题 I am using Crashlytics in my app for tracking crashes and Answers kit too for custom events. I am integrating the frameworks into my project using pod file. But I am getting a linking error while both pods are added like pod 'Fabric' pod 'Answers' pod 'Crashlytics' When I remove one from Answers and Crashlytics, then all is fine. Error is : Apple Mach-O Linker (Id) Error Linker command failed with exit code 1 (use to see invocation) Any ideas? 回答1: Mike from Fabric here. Remove the Answers

Xcode 6: 'Answers.h' file not found after Fabric Crashlytics update

萝らか妹 提交于 2019-12-08 18:18:37
问题 I was working along in my storyboard in Xcode 6.3.2 on an Objective-C project. All of a sudden when I try to build I get an error: /.../Developer/ProjectName/Crashlytics.framework/Headers/Crashlytics.h:14:9: 'Answers.h' file not found I've had Crashlytics installed and working in my app for a few weeks. I have it running through the Fabric plugin. I switched over the the Fabric app and noticed it had recently updated Crashlytics. In Xcode if I go "Source Control" -> "Commit..." to look at my