twitter-fabric

问题 I have integrated Crashlytics in my project, Now when I enable proguard, App Crashes. Have tried to exclude all the classes from crashlytics with no success File proguard-rules.pro file has the following -keep class io.fabric.sdk.android.** { *; } -keep interface io.fabric.sdk.android.** { *; } -keep class com.digits.sdk.android.core.** { *; } -keep interface com.digits.sdk.android.core.** { *; } -keep class com.twitter.sdk.android.** { *; } -keep interface com.twitter.sdk.android.** { *; }

问题 There are two different initialisation method shown in the documents: A) From here Fabric.with([Crashlytics.self(), Answers.self()]) B) From here Fabric.with([Crashlytics.self, Answers.self]) C) This also doesn't make the compiler to complain Fabric.with([Crashlytics.self, Answers.self()]) D) From nowhere Fabric.with([Crashlytics(), Answers()]) As I know, A and D are identical. But B gets a Type array. Which one is the correct one? If they don't differ, how does it work? 来源： https:/

问题 Recently, we've upgraded our organization's Crashlytics account to Fabric, and I'm trying to replace the old Crashlytics SDK with the new Fabric SDK in our existing apps. I've followed the migration instructions, and it's been largely painless, except that I'm now receiving a build error when I try to compile. The line in question that's causing the error is the bootstrap call: Fabric.with(this, new Crashlytics()); The error that's being returned is: Error:(55, 11) error: no suitable method

问题 I'm using Twitter's Fabric SDK in my Android app. I need to acquire a Twitter user's Tweets & Status Messages. I have not been able to find any examples, and the documentation is not very clear on this, so I have posted a new question. Can someone provide an example of how to use the TwitterApiClient class ? 回答1: Twitter Kit has the ability to make API calls. The official documentation is here: https://dev.twitter.com/twitter-kit/android/api Everything starts with Statuses Service:

问题 I'm trying to automate my app build distribution via Jenkyns and Crashlytics. I configured all as indicated on the documentation but crashlyticsUploadDistributionRelease failed with this error: "Distribution upload failed" and "WARN - Crashlytics halted compilation because it can't distribute the unsigned APK:". how can I fix it ? 回答1: Mike from Fabric and Crashlytics here. Beta for Android only supports distributing a signed APK, unsigned APKs can't be distributed. For information on how to

问题 I'm using, with success the Fabric Login button (TWTRLogInButton, https://dev.twitter.com/twitter-kit/ios-reference/twtrloginbutton). In my Swift app I can authenticate myself, make calls and all. The only problem is that i've implemented a "Logout" button that calls Twitter.logOut(). As specified by the documentation (https://dev.twitter.com/twitter-kit/ios-reference/twitter) this deletes the local session but does not invalidate the remote session. The effect is that once I'm authenticated

问题 Disabling Crashlytics error reporting is relatively straight forward.. I'd also like to disable Answers for debug builds. However, new Crashlytics.Builder().answers(null); doesn't work since apparently answers can't be null and new Crashlytics.Builder().answers(new CustomAnswers()); with CustomAnswers being my class extending Answers gets me a NPE when calling Answers.getInstance() . But that approach is cumbersome to begin with compared to simply calling some enable() method. Any ideas? On a

问题 I'm building an iOS app using React Native and trying to get it testable on phones. If I plug my phone into the computer and "build" directly to the phone, the app is built correctly and opens/operates correctly, no problem. But if I try to archive it and send it to phones using iTunes Connect's TestFlight or Fabric with Crashlytics, the app crashes immediately upon opening. It briefly shows the launch screen, but no more. Moreover, there are no crash reports -- in TestFlight, in Crashlytics,

问题 I recently received this app after updating to Crashlytics 3.0 Not sure if it comes from my code or something else. The crash report is untraceable Here is the crash report Crashed: com.apple.main-thread EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0x000000009a0dbeb8 0 libobjc.A.dylib objc_msgSend + 16 release 1 CoreFoundation CFRelease + 524 2 CoreFoundation -[__NSArrayM dealloc] + 152 3 libobjc.A.dylib (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 564 4 CoreFoundation

问题 Does Crashlytics work with Google Play Instant and if so, how do you setup your project correctly? 回答1: Yes, Crashlytics does work with Android Instant Apps, in fact it is the recommended crash reporting solution at this stage as it has been tested and works fine. For setup: Step 1 Open the build.gradle file in your base feature module and follow the steps on the public docs site to configure Crashlytics as normal. Step 2 At the top level of your base feature module build.gradle file, add the