为什么与gitlab集成的fabric(crashlytics)不会将问题发送到gitlab? [英] Why integrated fabric(crashlytics) with gitlab does not send issues to gitlab?
问题描述
我在android应用中使用fabric-Crashlytics,并通过
Fabric.with(new Fabric。 Builder(this)
.kits(new Crashlytics(),new Answers())
.debuggable(true)
.build()
);
我将gitlab与Fabric集成到Fabric的服务挂钩中成功,这意味着当我按下发送测试蓝色时
但是当我通过[ Crashlytics.getInstance()。crash( );
],我在gitlab中没有任何问题,为什么?
如何解决此问题?
我的问题已解决正如我在评论中所说。感谢 MikeBonnell ,感谢评论:
Mike,来自Fabric。您选择了什么程度的集成?只有将影响级别设置为1时,才会触发新问题。此外,这需要是一个全新的问题,也就是说,如果您以前曾使用过测试崩溃,则不会发送新问题。
I use fabric-Crashlytics in my android app and initiate it in Application class via
Fabric.with(new Fabric.Builder(this)
.kits(new Crashlytics(), new Answers())
.debuggable(true)
.build()
);
I integrated fabric with gitlab in fabric's service hooks successfully, It means when I press "Send Test" blue button on fabric I'll receive an issue in gitlab.
BUT when I force app to crash via [Crashlytics.getInstance().crash();
] ,I don't get any issue in gitlab, Why?
How Can I fix this problem?
My problem solved as I said in comments.Thanks MikeBonnell for the comment:
Mike from Fabric here. What impact level did you choose on the integration? Only if the impact level was set to 1 would a new issue be triggered. Also, this needs to be a brand new issue, that is if you've used that test crash before, then a new issue wouldn't be sent over.
这篇关于为什么与gitlab集成的fabric(crashlytics)不会将问题发送到gitlab?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!