简体   繁体   中英

Crashlytics migration for Firebase ruins Twitter functionality from Fabric

I'm using the Twitter kit from Firebase

TwitterAuthConfig authConfig = new TwitterAuthConfig(BuildConfig.TW_CUSTOMER_KEY, BuildConfig.TW_CUSTOMER_SECRET);
Fabric.with(this, new Twitter(authConfig), new TwitterCore(authConfig), new TweetUi());

But I've migrated Crashlytics to Firebase. Firebase doesn't work if I keep having the key in the manifest

    <meta-data
        android:name="io.fabric.ApiKey"
        android:value="9249a2692d5c8xxxxxxxxxxxxxc" />

Problem is that if I remove it, I can't use Twitter anymore, it crashes with java.lang.IllegalStateException: Must start Twitter Kit with Fabric.with() first android.app.ActivityThread.performLaunchActivity

Is there a solution for this ?! I can't find a middle ground to support both of 'em.

Twitter kit is no longer part of Fabric or Crashlytics. However, it is available through the Twitter Developer site. Check there for how to update your SDKs.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM