{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', '推荐 Juvenile、少年° 的问题《Migrate Fabric's Crashlystic data to Firebase》','https://www.manongdao.com/q-1216293.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
As the title, I need to migrate all existing data from Fabric's Crashlytics to Firebase.
The problem here is after migrating, If I remove fabric key in AndroidManifest, My app can't push the crash report to firebase's Crashlytics anymore. But when I create Firebase's Crashlytics from the beginning (without Fabric migrate) They recommend me to remove existing Fabric key to make it work.
Is it ok?
Mike from Fabric here. Yes, now is a good time to start linking and migrating to Firebase.