C++ crashlytics android本机崩溃无法在仪表板上报告

C++ crashlytics android本机崩溃无法在仪表板上报告,c++,android-ndk,android-gradle-plugin,native,crashlytics-android,C++,Android Ndk,Android Gradle Plugin,Native,Crashlytics Android,我正在android应用程序中集成crashlytics,以获得本机崩溃。我已按照链接上的说明进行操作: 我正在使用CrashlyticsUploadSymbolRelease或CrashlyticsUploadSymbolDebug编译项目,我可以在build文件夹中看到CSYM,但我不确定它是否被上传。 此外,我看不到手动将csym上载到crashlytics的选项 我在C++代码中崩溃了应用程序,但是崩溃并没有被报告给仪表板,但是java崩溃已经成功地被报告到仪表板上。 我可以在Cras

我正在android应用程序中集成crashlytics,以获得本机崩溃。我已按照链接上的说明进行操作:

我正在使用CrashlyticsUploadSymbolRelease或CrashlyticsUploadSymbolDebug编译项目,我可以在build文件夹中看到CSYM,但我不确定它是否被上传。 此外,我看不到手动将csym上载到crashlytics的选项

我在C++代码中崩溃了应用程序,但是崩溃并没有被报告给仪表板,但是java崩溃已经成功地被报告到仪表板上。 我可以在CrashlyticCore中看到以下异常:

D/CrashlyticsCore(8077): Could not generate ID for file /data/data/com.package.dummy/cache/1501670890290.dex (deleted)
01-02 12:19:58.499: D/CrashlyticsCore(8077): java.io.FileNotFoundException: /data/app/com.package.dummy-1/lib/arm/1501670890290.dex (deleted): open failed: ENOENT (No such file or directory)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at libcore.io.IoBridge.open(IoBridge.java:452)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at java.io.FileInputStream.<init>(FileInputStream.java:76)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at java.io.FileInputStream.<init>(FileInputStream.java:103)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.Sha1FileIdStrategy.getFileSHA(Sha1FileIdStrategy.java:28)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.Sha1FileIdStrategy.createId(Sha1FileIdStrategy.java:17)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.BinaryImagesConverter.parseProcMapsJson(BinaryImagesConverter.java:67)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.BinaryImagesConverter.convert(BinaryImagesConverter.java:33)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.NativeFileUtils.processBinaryImages(NativeFileUtils.java:85)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.NativeFileUtils.binaryImagesJsonFromFile(NativeFileUtils.java:72)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.NativeFileUtils.binaryImagesJsonFromDirectory(NativeFileUtils.java:62)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.CrashlyticsController.finalizeMostRecentNativeCrash(CrashlyticsController.java:883)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.CrashlyticsController.access$1500(CrashlyticsController.java:67)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.CrashlyticsController$16.call(CrashlyticsController.java:953)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at com.crashlytics.android.core.CrashlyticsController$16.call(CrashlyticsController.java:943)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at java.util.concurrent.FutureTask.run(FutureTask.java:237)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at io.fabric.sdk.android.services.common.ExecutorUtils$1$1.onRun(ExecutorUtils.java:75)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at io.fabric.sdk.android.services.common.BackgroundPriorityRunnable.run(BackgroundPriorityRunnable.java:30)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at java.lang.Thread.run(Thread.java:818)
01-02 12:19:58.499: D/CrashlyticsCore(8077): Caused by: android.system.ErrnoException: open failed: ENOENT (No such file or directory)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at libcore.io.Posix.open(Native Method)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at libcore.io.BlockGuardOs.open(BlockGuardOs.java:186)
01-02 12:19:58.499: D/CrashlyticsCore(8077):    at libcore.io.IoBridge.open(IoBridge.java:438)
D/crashlyticcore(8077):无法生成文件/data/data/com.package.dummy/cache/1501670890290.dex的ID(已删除)
01-02 12:19:58.499:D/crashlyticcore(8077):java.io.FileNotFoundException:/data/app/com.package.dummy-1/lib/arm/1501670890290.dex(已删除):打开失败:enoint(无此类文件或目录)
01-02 12:19:58.499:D/crashlyticcore(8077):位于libcore.io.IoBridge.open(IoBridge.java:452)
01-02 12:19:58.499:D/crashlyticcore(8077):位于java.io.FileInputStream。(FileInputStream.java:76)
01-02 12:19:58.499:D/crashlyticcore(8077):位于java.io.FileInputStream。(FileInputStream.java:103)
01-02 12:19:58.499:D/CrashlyticsCore(8077):位于com.crashlytics.android.core.Sha1FileIdStrategy.getFileSHA(Sha1FileIdStrategy.java:28)
01-02 12:19:58.499:D/CrashlyticsCore(8077):位于com.crashlytics.android.core.Sha1FileIdStrategy.createId(Sha1FileIdStrategy.java:17)
01-02 12:19:58.499:D/CrashlyticsCore(8077):位于com.crashlytics.android.core.BinaryImagesConverter.parseProcMapsJson(BinaryImagesConverter.java:67)
01-02 12:19:58.499:D/CrashlyticsCore(8077):在com.crashlytics.android.core.BinaryImagesConverter.converter(BinaryImagesConverter.java:33)
01-02 12:19:58.499:D/CrashlyticsCore(8077):位于com.crashlytics.android.core.NativeFileUtils.processbinaryImage(NativeFileUtils.java:85)
01-02 12:19:58.499:D/CrashlyticsCore(8077):在com.crashlytics.android.core.NativeFileUtils.binarymagesjsonfromfile(NativeFileUtils.java:72)
01-02 12:19:58.499:D/CrashlyticsCore(8077):位于com.crashlytics.android.core.NativeFileUtils.binaryImagesJsonFromDirectory(NativeFileUtils.java:62)
01-02 12:19:58.499:D/CrashlyticsCore(8077):位于com.crashlytics.android.core.crashlyticscontler.finalizeemostrecentnativecrash(crashlyticscontler.java:883)
01-02 12:19:58.499:D/CrashlyticsCore(8077):在com.crashlytics.android.core.crashlyticscontler.access$1500(crashlyticscontler.java:67)
01-02 12:19:58.499:D/CrashlyticsCore(8077):在com.crashlytics.android.core.crashlyticsconner$16.call(crashlyticsconner.java:953)
01-02 12:19:58.499:D/CrashlyticsCore(8077):在com.crashlytics.android.core.crashlyticsconner$16.call(crashlyticsconner.java:943)
01-02 12:19:58.499:D/crashlyticcore(8077):在java.util.concurrent.FutureTask.run(FutureTask.java:237)
01-02 12:19:58.499:D/crashlyticcore(8077):位于java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
01-02 12:19:58.499:D/crashlyticcore(8077):位于java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
01-02 12:19:58.499:D/crashlyticcore(8077):在io.fabric.sdk.android.services.common.execututils$1$1.onRun(execututils.java:75)
01-02 12:19:58.499:D/crashlyticcore(8077):在io.fabric.sdk.android.services.common.BackgroundPriorityRunnable.run(BackgroundPriorityRunnable.java:30)
01-02 12:19:58.499:D/crashlyticcore(8077):位于java.lang.Thread.run(Thread.java:818)
01-02 12:19:58.499:D/crashlyticcore(8077):原因:android.system.ErrnoException:open失败:enoint(没有这样的文件或目录)
01-02 12:19:58.499:D/crashlyticcore(8077):位于libcore.io.Posix.open(本机方法)
01-02 12:19:58.499:D/crashlyticcore(8077):位于libcore.io.BlockGuardOs.open(BlockGuardOs.java:186)
01-02 12:19:58.499:D/crashlyticcore(8077):在libcore.io.IoBridge.open(IoBridge.java:438)

你修好了吗?@Jordan还没有。Crashlytics回答了这个问题,并说这个问题在最新的更新中得到了修复。我也试过了,但还是有同样的例外。我会再次联系他们,如果我得到任何更新,我会更新你。我有完全相同的问题。相同的堆栈跟踪。你能告诉我bug报告/支持吗?这样我也可以问他们。