“ [[Crashlytics：Crash]报告已禁用”。

问题描述：

我们的生产iOS应用程序初始化时，我收到以下错误消息：

I am getting the following error messages when our production iOS app initializes:

[Crashlytics] Version 3.8.4 (121)
[Crashlytics] Running on iOS Simulator (iPhone), 10.3.0 (16E195) 
[Crashlytics:Crash] Reporting is disabled 
[Crashlytics] Crash reporting could not be initialized 
[Answers] Initialized 
[Fabric] Initialized with kit versions: {
    "com.twitter.answers.ios" = "1.3.4"; 
    "com.twitter.crashlytics.ios" = "3.8.4"; 
    "io.fabric.sdk.ios" = "1.6.11"; 
}

每个随后的记录事件的调用都会出现以下错误：

Every subsequent call to log an event gets the following error:

[Crashlytics:Crash] WARNING: CLSLog has been used before (or concurrently with) 
    Crashlytics initialization and cannot be recorded. The message was: ...

该应用的非生产版本可以正常运行代码，但具有不同的bundleID。通常，当应用程序首次初始化时，我会在Fabric仪表板中看到该应用程序，但是在这种情况下，该应用程序没有显示。

The non-production versions of the app work fine running the exact same code but with different bundleIDs. Normally when the app initializes for the first time, then I see the app populate in the Fabric dashboard, but in this case the app is not showing up.

我们有一个Android版本和一个iOS版本的应用程序，它们都使用相同的bundleID，所以我想知道是否因此而发生冲突？我在仪表板上看到了该应用程序的Android版本，并且似乎工作正常。这是一个最初是Xamarin应用程序的应用程序，已编译到两个平台，但两个平台均未包含Fabric / Crashlytics。现在我们已经在每个平台上编写了本机应用程序，并且都在使用Fabric / Crashlytics。

We have an Android and an iOS version of the app, and they both use the same bundleID, so I am wondering if there is a conflict because of that? I see the Android version of the app in the dashboard, and it seems to be working properly. This is an app that originally was a Xamarin app that compiled to both platforms, neither of which incorporated Fabric/Crashlytics. We have now written native apps on each platform, and both are using Fabric/Crashlytics.

由于这是两个商店中都已存在的应用程序，因此我们没有

Since this is a pre-existing app in both stores, we do not have the option of changing either app’s bundleID.

答

显然，在某些情况下，Crashlytics不会自动激活新应用程序，因此它们不会出现在您的应用列表下，即使所有内容均已正确编码且数据仍在服务器上。在这种情况下，请发送电子邮件至Crashlytics支持（support@fabric.io），其中包含所涉及应用程序的info.plist条目的副本，他们将为您激活该电子邮件。我不得不这样做几次，尤其是对于应用程序扩展。

There are apparently cases where Crashlytics does not auto-activate new apps so that they show up under your list of apps, even though everything is coded correctly and data is going to their servers. In this case, send an email to Crashlytics support (support@fabric.io) that contains a copy of the info.plist entries for the app in question and they will activate it for you. I have had to do this several times, especially with app extensions.

“ [[Crashlytics：Crash]报告已禁用”。

相关推荐