google-fabric

问题 We have application which depends on ndk library packaged as aar. Also this app builds it's own NDK code using cmake. We upload symbols using crashlyticsUploadSymbols<Flavor> task. And when I check build/fabric/<flavor>/release/csyms there is csym files for both libraries and all our supported architectures. Everything seems ok, but native crashes symbolicated like this. Lots info about system lines and no info about contents of libglmapview which is most interesting part of every crash. What

问题 I just get to know Fabric and integrated it into my project and trying to see how it brings value to me. I've used Crashlytics.crash(), and got the below "error log" but I'm wondering what language is that and how do we really able to understand it # Crashlytics - plaintext stacktrace downloaded by Isaac Lem at Thu, 18 Oct 2018 08:41:53 GMT # URL: https://fabric.io/mobile111539583220/ios/apps/com.xx.xx-xx/issues/5bc84705f8b88c29633d3016?time=last-seven-days/sessions

问题 I tried integrating my GitLab Account with Fabric using the respective service hook. I used these parameters: Your GitLab URL: https://gitlab.com/ Your GitLab Namespace/Project: my projectname Your GitLab Private Token: New Personal Access Token created in GitLab User settings -> Access Tokens Entering these values I get a Could not access project "my projectname" - HTTP status code: 308 error I also tried changing the GitLab URL to point directly at my project, then I get a 404. What am I

问题 Question - would like to allow access to Fabric & Crashlytics from our server which means that we need to allow it through our firewall for access. Can anyone share the domains or IPs that we should allow through ? Secondly, we would also like the fabric plugin for Android Studio and Xcode to work, would the above domains and IPs also apply ? 回答1: Mike from Fabric and Firebase here. We don't support IP whitelisting as our IP addresses can and do change quite frequently. You should whitelist

问题 I am trying to update Fabric Crashlytics from 2.6.8 to 2.7.1 But I am facing below crash with this update: 10-24 11:38:32.917 11352-11352/? E/AndroidRuntime: FATAL EXCEPTION: main Process: com.xxx.yyy, PID: 11352 java.lang.NoClassDefFoundError: Failed resolution of: Lio/fabric/sdk/android/services/common/FirebaseInfo; at com.crashlytics.android.CrashlyticsInitProvider.onCreate(CrashlyticsInitProvider.java:22) at android.content.ContentProvider.attachInfo(ContentProvider.java:1919) at android

问题 I am working in an iOS Library and I want to add Crashlytics so I can get notified if the library crashes to any user. I have already integrated the Crashlytics and Fabric frameworks: I added the .frameworks bundles, then I added the Fabric API Key into the library's info.plist as well as the run script phase into build phases, but when the library crashes inside a running app, nothing happens in the fabric dashboard. Is it possible to add Crashlytics to an iOS Library? 回答1: Looks like the

问题 Today fabric crashes after the pod update Fabric 1.9.0 [Fabric isCrashlyticsCollectionEnabled]: unrecognized selector sent to class 0x10c0bb918 Crashing line : Fabric.with([Crashlytics.self]) It crashes at app startup. Anyone having the same problem? 回答1: I reverted to a previous version of Crashlytics by updating my Podfile pod 'Fabric', '1.8' pod 'Crashlytics', '3.11' Then updating Cocoapods: pod update 'Crashlytics' Hopefully Google fixes this soon 回答2: Go to the "Update via Manual Steps"

问题 Currently, I'm trying to integrate Crashlytics into an Android Application. However I can't get the app to be recognized and added to the Fabric Dashboard. When using the Android Studio Fabric plugin following these steps: New App Select Crashlytics Apply Code changes Sync gradle Rebuild project Build app onto device (not virtual) However when I do this, the Fabric plugin is still stuck on the "Please build and run your application" screen, and eventually gives an error message "It's been a

问题 I'am having problems with crashylitics showing proper callstacks for native crashes. It used to work some time ago, but now callstacks either make no sense, or the names are missing. I have made sure that symbols are being uploaded by looking into ~/.crashylitics log file. Everything looks fine there. I have made a test crash and compared tombstone from logcat with what appears in crashylitics (I have connected fabric.io project with firebase). What bothers me is that we are uploading symbols

问题 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