此答案的最新更新时间是: -2021年2月12日

This answer is last updated on: 12-Feb-2021

我们不需要采取任何行动.请稍候，Google将在何时发布此已修复"的"

正如许多人指出的那样，事实证明存在一些 即使发生以下情况也会触发警告的设备配置 我上面提供的解决方法.

As many of you have pointed out, it turns out that there exist some device configurations that trigger the warning even with the workaround I provided above.

不幸的是，我们无法做更多的事情来沉默".警告 在SDK方面.该警告是由"Google Play服务"引起的. 本身.好消息是，问题的根本原因是现在 固定，但是它将在2月左右推出到设备上，因此我们将 必须忍受这个警告几个月.

Unfortunately there is nothing more we can do to "silence" the warning on the SDK side. The warning is caused by "Google Play Services" itself. The good news is that the root cause of the issue is now fixed, however it will roll out to devices around February, so we will have to live with this warning for a few months.

我知道这给开发人员带来了不便，但是 这是警告而不是崩溃.所以请耐心等待直到更新 推出.谢谢

I understand that it is causing inconvenience for developers, but fwiw it's a warning not a crash. So please bear with us till the update gets rolled out. Thanks

PS:你们中许多人评论说有时会出现此警告 崩溃(有其自身的例外)，我相当有信心 在这种情况下，崩溃与该警告完全无关，仅此而已 恰好发生在它之后.所以请调查您的崩溃 独立地，只是忽略警告.但是，如果您认为 崩溃是相关的，请提供:

PS: Many of you have commented that this warning is sometimes followed by a crash(with its own exception), I am fairly confident that in most cases, the crash is completely unrelated to this warning and just so happens to occur right after it. So please investigate your crashes independently, just ignoring the warning. If however you think that the crash is related, please provide:

在与您的崩溃相关的依赖项下发生完整堆栈跟踪 应用程序理想的步骤是重现再次转发此答复，因此更多 对人们可见.

full stack traces at the event of crash relevant dependencies of your app ideally steps to reproduce Bumping this reply again, so it's more visible for folks.

再次:警告是良性的，可以忽略.该修复程序将 在2021年2月左右推出，无需对开发者的产品采取任何措施 方面，此修复程序将适用于Google Play服务本身和现有的服务 应用程序将停止生成警告.

Once again: The warning is benign and is safe to ignore. The fix will get rolled out around Feb 2021, no action is required on developers' side, the fix will apply to google play services itself and existing apps will stop generating the warning.

来源: https://github.com/firebase /firebase-android-sdk/issues/1662#issuecomment-756917362