简体   繁体   English

在构建服务器上使用APKTool进行Crashlytics

[英]Crashlytics with APKTool on build server

I´ve setup crashlytics for android using the suggested gradle method and while running in android studio things work fine. 我已经使用建议的gradle方法设置了Android的crashlytics,并且在android studio中运行时一切正常。 I get crash reports, statistics and everything just as expected (and looking great btw!). 我得到的崩溃报告,统计信息和所有事情都与预期的一样(顺便说一句!)。

The problem is when I want to use the same features in our release environment. 问题是当我想在我们的发布环境中使用相同的功能时。 We´re using APKtool on a build server to modify resources, package name and a few other things. 我们正在构建服务器上使用APKtool来修改资源,程序包名称和其他一些内容。 Basically, we are producing a lot of release APKs all based on exactly the same code. 基本上,我们基于完全相同的代码制作了许多发行版APK。 When I run the produced release APKs nothing gets reported to crashlytics. 当我运行生成的发行版APK时,崩溃解析程序未收到任何报告。 From what I´ve understood it seems crashlytics communicates with the fabric API during the build process and since we are essentially creating a new APK (with a new package name) we probably need to do this manually somehow. 据我了解,crashlytics似乎在构建过程中与Fabric API通信,并且由于我们实际上是在创建新的APK(具有新的包名称),因此我们可能需要以某种方式手动执行此操作。

I´ve seen it mentioned in the ios beta distribution docs that you can run a script to submit created builds to the API so is there something similar available for Android, preferably without changing our whole build process? 我已经在ios beta发行文档中看到了它,您可以运行一个脚本来将创建的构建提交到API,因此Android是否有类似的功能可用,最好不更改整个构建过程?

Thanks Magnus. 谢谢马格努斯。 We need to detect an IDE build and a device or simulator run event to show the app in your dashboard per package name. 我们需要检测IDE构建以及设备或模拟器运行事件,以按包名称在仪表板上显示该应用程序。

Reach out with your package names if you are running into issues and we can manually activate them. 如果遇到问题,请提供您的软件包名称,我们可以手动激活它们。 :) :)

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

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