Affected versions:

• Fx 67.0b8

Affected platforms:

• Ubuntu 18.04

Steps to reproduce:

1. Download the build from
   https://archive.mozilla.org/pub/firefox/candidates/67.0b8-candidates/build2/snap/firefox-67.0b8.snap
2. In the directory where the .snap file is downloaded run the following
   command snap install <name>.snap (eg. firefox-67.0b8.snap)

Expected result:

• The snap build is successfully installed.

Actual result:

• The error "error: cannot find signatures with metadata for snap" appears.

Regression range

• Not a regression since it also happens to 67.0b6 which was the first version
  of snap from archive.org

Additional notes:

• Using any other method to install the snap build works as intended.

Thank you very much for filing this bug, Daniel!

That's a genuine concern. In the meantime, for testing (not for actual use), you can install this snap with:

snap install --dangerous <name>.snap

--dangerous means you know the APK isn't signed.

Bug 1450019 (re)automated the deployment to archive.mozilla.org. The root cause of this error is that Canonical didn't sign this build as well as no other build uploaded on there. I'm glad these Snaps remain in the candidates directory and not the release one.

The fix is to download the Snap from the Snap store and let beetmover upload this file onto archive.mozilla.org. That's a new thing, we've never done it before. I can update the push-snap task to expose this the signed snap as a Taskcluster artifact (which would then be consumed by beetmover.

Probably not something we're going to do now that canonical build the packages that are uploaded to the snap store.