google-fabric

问题 My fabric was working fine with previous versions whenever I tried to archive and submit to Appstore. However, I just submitted my latest build version and the fabric website doesn't have my latest build version but it does appear in the fabric Mac app. What should I do to get the latest build in Fabric website? 回答1: Mike from Fabric here. A version will show up in your Crashlytics dashboard when we've seen a run of that version with Fabric enabled. A new version may not show up on the Latest

问题 I've added crashlytics in my app and I've uploaded a build in our private download site which is available for test users. The version which I had uploaded my build used crashlytics version 3.9.0. In my fabric dashboard I was getting crashlog and last crash log was dated last Thu, Nov 9. For past few days(since last friday) I've been getting report from users that they have experienced few crash which they are unable to reproduce and happens occasionally. But when I look at the fabric

问题 I have integrated Crashlytic in reactNative application and tried to check crash logs generated from js files. Its able to capture them but not providing information about the file name. Logs are giving location from index.android.bundle file which are hard to provide any information about crash location. I have already tried react-native-fabric-crashlytics and react-native-fabric npm modules Setting default logger for react native as mentioned in https://www.mojotech.com/blog/fabric

问题 I'm using Crashlytics in fabric. I read privacy-policy.pdf to check privacy issue. I found stored information includes device state information, unique device identifiers and so on. I'd like to know what exact information is gathered for device state information and unique device identifier. Thanks & Regards, Michael Kim. 回答1: Mike from Fabric here. As referenced from Crashlytics' site An RFC-4122 UUID which permits us to deduplicate crashes. The timestamp of when the crash occurred. The app

问题 When I package from XCode via Fabric Plugin a Beta in debug mode, I got an error : Fabric Archive packaging Error -6 In Xcode I have check code signing manual (or auto same problem) for the app and the widget/extension with valid certificates and provisionning. I also check that I have all certificates (public/private keys) and provisionning on my keychain. If I build with fastlane last version 2.58.0, I got the same issue than direcly build from XCode. Note that without any changes, one day

问题 This question already has an answer here : How do you set the time zone in Crashlytics? (1 answer) Closed 2 years ago . Can I change the time zone in Fabric? Fabric got the UTC, but we located in other time zone. So when we checked the data in Fabric, we would be confused by the time. UTC time zone 回答1: Ah, currently I think there is not a way to change the timezone cause all the way to change timezone are based on the UTC. 来源： https://stackoverflow.com/questions/43338481/how-can-i-change-the

问题 Suddenly when Syncing Gradle, I get this error: WARNING: API 'variant.getJavaCompile()' is obsolete and has been replaced with 'variant.getJavaCompileProvider()'. It will be removed at the end of 2019. For more information, see https://d.android.com/r/tools/task-configuration-avoidance Affected Modules: app I've got this build.gradle for the app module: apply plugin: 'com.android.application' apply plugin: 'kotlin-android' apply plugin: 'kotlin-android-extensions' apply plugin: 'com.google

问题 I need some assistance understanding an aspect of this function provided by fabric As far as I understand by setting: ext.betaDistributionGroupAliases = "testers" When the APK is uploaded, those members of that testers group should receive an email invitation to test. This is not the case in my instance. The APK does upload and the users are associated with this build as can be seen by the console (it says 9 invited). But no emails are actually sent out. I would prefer to use the group alias

问题 We have released the latest build with the minimum deployment target 10.We are getting the same many crashes in iOS 13 related to the background issues. We are enabling the following capabilities:
 1.background fetch 2.push notification(FireBase) 3.data protection as NSFileProtectionComplete. When checking the link : https://forums.developer.apple.com/thread/122858 Most answers are switching to NSFileProtectionCompleteUntilFirstUserAuthentication from NSFileProtectionComplete. Is this correct

问题 We have released the latest build with the minimum deployment target 10.We are getting the same many crashes in iOS 13 related to the background issues. We are enabling the following capabilities:
 1.background fetch 2.push notification(FireBase) 3.data protection as NSFileProtectionComplete. When checking the link : https://forums.developer.apple.com/thread/122858 Most answers are switching to NSFileProtectionCompleteUntilFirstUserAuthentication from NSFileProtectionComplete. Is this correct