为什么Kotlin文件显示为.java并启用了Proguard的Fabric Crashlytics? [英] Why do Kotlin files appear as .java is Fabric Crashlytics with Proguard enabled?

问题描述

我最近为Android应用程序启用了Proguard最小化功能，该应用程序在Fabric控制台上使用Crashylics报告.该项目主要用Kotlin编写.

I have recently turned on Proguard minimisation for an Android app which uses Crashylics reporting on the Fabric console. The project is written mainly in Kotlin.

仍然收到崩溃报告.堆栈跟踪不再将Kotlin源文件列为.kt，而是列为.java

Crash reports are still received. The stack trace no longer lists Kotlin source files as .kt though, but as .java

例如MyFragment.java:20而不是MyFragment.kt:20

根据跟踪中的信息(例如函数和变量名)，堆栈中的行号与.kt文件中的行号匹配

From the information in the traces, such as function and variable names, the line numbers in the stack match up to those in the .kt file

我在配置指南中列出了Proguard排除项: https://docs.fabric.io/android/crashlytics/dex-and-proguard.html

I have Proguard exclusions as listed in the config guide: https://docs.fabric.io/android/crashlytics/dex-and-proguard.html

Kotlin是否需要采取其他措施?

Is there an extra action for Kotlin?

我想在崩溃报告中看到正确的文件扩展名

I'd like to see the correct file type extension in crash reports

推荐答案

此处的Fabric/Firebaser-

Fabric/Firebaser here -

默认情况下，我们假定扩展名为.java，但将来我们将寻求改善Kotlin的这种体验.

We assume a .java extension by default, but we'll be looking to improve this experience for Kotlin in the future.

这篇关于为什么Kotlin文件显示为.java并启用了Proguard的Fabric Crashlytics?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！