当我尝试使用 meta-data 标记的 value 作为字符串引用构建项目时，crashlytics 失败并出现以下错误:

Crashlytics found an invalid API key: @string/crashlytics. 
Check the Crashlytics plugin to make sure that the application has been added successfully! 
Contact support@crashlytics.com for assistance.

不起作用

<meta-data
    android:name="com.crashlytics.ApiKey"
    android:value="@string/crashlytics"/>

作品

<meta-data
    android:name="com.crashlytics.ApiKey"
    android:value="1234567890..."/>

我想在 string.xml 中为我的 android 项目的不同 productFlavors 定义不同的键。

更新

写入 crashlytics 支持后:

Currently we only are able to evaluate the AndroidManifest.xml at build time so we don't look at any strings resources so we only support a hard coded string. I'll definitely share this with the team that you're interested so we can look into supporting this in a future release.

最佳答案

Edit: The solution accepted is working only if you are using an old version of Crashlytics (I was using v1.1.11). If you are using Fabric SDK you will notice the tasks of the plugin have changed considerably and the script below will not work. Also the API secret is not needed anymore, therefore you can just use the <meta> in the manifest to specify the API key along with a manifest placeholder defined in your flavor:

• in build.gradle:

  flavor1 {
      ...
      manifestPlaceholders = [crashlyticsApiKey: CRASHLYTICS_API_SECRET_HERE]
      ...
  }
  

• 在 AndroidManifest.xml 中:

  ...
  <meta-data
      android:name="com.crashlytics.ApiKey"
      android:value="${crashlyticsApiKey}" />
  ...
  

还有另一种未记录的方式将 Crashlytics 键指定为 noted here , 就是使用 crashlytics.properties (在项目的根目录中)指定该值以及 API secret :

apiKey=YOUR_API_KEY
apiSecret=YOUR_API_SECRET

很遗憾，这将不允许您简单地指定不同的 crashlytics.properties对于每种 flavor ，因为它需要位于项目的根目录中才能被 gradle 插件正确选择。这意味着您需要动态生成该文件。 想法是将您的风格中的 key / secret 值添加为自定义属性，并生成 crashlytics.properties在构建时，使用当前风格的值来填充文件。

build.gradle在你的 android 模块中应该是这样的:

...
productFlavors {

    flavor1 {
        ...
        set("crashlyticsApiKey", CRASHLYTICS_API_KEY_HERE)
        set("crashlyticsApiSecret", CRASHLYTICS_API_SECRET_HERE)
        ...
    }
    ...
}

File crashlyticsProperties = new File("${project.projectDir.absolutePath}/crashlytics.properties")
applicationVariants.all { variant ->
    variant.productFlavors.each { flavor ->
        def variantSuffix = variant.name.capitalize()
        def generateResourcesTask = project.tasks.getByName("crashlyticsGenerateResources${variantSuffix}")
        def generatePropertiesTask = task("crashlyticsGenerateProperties${variantSuffix}") << {
            Properties properties = new Properties()
            println "...copying apiSecret for ${variant.name}"
            properties.put("apiSecret", flavor.crashlyticsApiSecret)
            println "...copying apiKey for ${variant.name}"
            properties.put("apiKey", flavor.crashlyticsApiKey)
            properties.store(new FileWriter(crashlyticsProperties), "")
        }
        generateResourcesTask.dependsOn generatePropertiesTask
        def cleanResourcesTask = project.tasks.getByName("crashlyticsCleanupResourcesAfterUpload${variantSuffix}")
        cleanResourcesTask.doLast {
            println "...removing crashlytics.properties"
            crashlyticsProperties.delete()
        }
    }
}
...

基本上，脚本在构建过程中 Hook ，并在 Crashlytics gradle 插件发挥作用之前生成/填充属性文件。

关于android - Crashlytics 发现无效的 API key ，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/25700680/