本文介绍了在不更改代码的情况下,有什么可以破坏android构建的?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用 react-native-firebase react-native应用程序上工作.我已经在travis上设置了CI构建,目的是具有可复制的构建,但突然停止了工作,如以下所述:

I am working on a react-native app that uses react-native-firebase. I've setup a CI build on travis with the aim to have reproducible builds, and it has suddenly stopped working, as detailed here:

  • 之前:4天前,该版本可以正常运行
  • 之后:今天,完全相同的版本已被破坏,失败并显示以下消息:
  • before: 4 days ago, the build works
  • after: today, the exact same build is broken, failing with the following message:

我唯一合理的猜测是某些依赖关系发生了变化,但我不了解android的构建是否足够好,无法弄清发生了什么或为什么.

My only reasonable guess is that some dependency has changed, but I don't understand android builds well enough to figure out what has happened or why.

很明显,如何防止将来发生此类意外? (在我看来,此构建应该是完全可重复的)

And obviously, how do I prevent such surprises from happening in the future? (in my mind, this build should be perfectly repeatable)

作为旁注,当构建失败时,它还会显示一些警告,例如:

As a side note, when the build fails, it also shows several warnings like:

但是遵循该建议只会导致进一步的(不同的)错误.

but following that advice only causes further (different) errors.

推荐答案

根本原因是与向Androidx的迁移有关,而Google Play服务已更新为androidX

The root cause is related migration to Androidx, google play service updated to androidX

如果您使用的是real-native-info,请升级.它将通过 2.1.2

If you are using real-native-info, please upgrade. It will solve your problem with 2.1.2

请参见在此处应用链接

这篇关于在不更改代码的情况下,有什么可以破坏android构建的?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-13 13:00
查看更多