Builds have been failing for a few days on our repo without any Travis configuration change on our side. An example: https://travis-ci.org/aframevr/aframe/jobs/642649644?utm_medium=notification&utm_source=github_status I see the following error: WARNING: The following packages cannot be authentica…

See Error installing APT packages Specifically for me, this change fixed things: https://github.com/appium/appium-base-driver/compare/90890df923e0...7cc9d308fbf9

[image] Get error when install google-chrome-stable -> W: GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 78BD65473CB3BD13 Travis CI Discussions & Feedback my …

Cool thanks. That seems to work

Help troubleshooting failing Travis builds - There were unauthenticated packages and -y was used without --allow-unauthenticated

Travis CI Discussions & Feedback

native-api January 28, 2020, 12:36am 2

Topic		Replies	Views
The following packages cannot be authenticated! google-chrome-stable Xenial build-env	6	2223	January 21, 2020
Packages cannot be authenticated. GPG error google-chrome-stable Xenial build-env	5	2599	April 15, 2019
Xenial: google-chrome-stable cannot be installed (not authenticated) Travis CI Discussions & Feedback bug	1	823	January 21, 2020
Packages authentication error. GPG error google-chrome-stable Linux	1	1236	January 29, 2020
Travis build stopped Linux	4	960	February 3, 2020

Help troubleshooting failing Travis builds - There were unauthenticated packages and -y was used without --allow-unauthenticated

Related topics