{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 放荡不羁爱自由 的问题《Android: Installing Crashlytics in an SDK and its》','https://www.manongdao.com/q-735306.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I'm developing an Andriod SDK project, intended to be imported by other applications.
Currently I have Crashlytics integrated in my SDK. The problem is that some of our clients who want to use the SDK already have Crashlytics integrated, which causes a conflicts between the two fabric libraries.
Is there a way to have Crashlytics installed in an SDK and in its embracing app?