Comment 9 for bug 1674093

When you originally downloaded the snap, if you did it with “snap download”, you will have had a .snap and a corresponding .assertion file; you can then add the assertions with “snap ack foo_NN.assertion” (*before* doing “snap install ./foo_NN.snap”; doing it after will not do what you want), and everything will be happy.

Note that you *could* download the assertions having just the snap, but it's a lot of work: you need the sha3-384 of the .snap file, and use “snap ack --remote” to get that, and then recursively get any assertions needed by that (for the developer id for example). It's a lot of manual work, which we could make easier, but as it's a bit of a corner case (given “snap download” does what most people need already), it's nowhere near the top of our priority queue right now.

I'm leaving this bug open but setting it to wishlist to reflect all this.

HTH.