We build a custom development image model for our device where we don’t get a serial assertion to our private store (we save that for production devices only that need auto-updates). It seems like in the past, we could do snap login and then do snap refresh to refresh any outdated snaps both public and private snaps. However, it seems that it not longer possible (at least with snapd 2.73, not sure how early this goes). When we run snap refresh, as soon as it starts to download a private snap, we get a 404 error. If we refresh a specific snap snap refresh <snap_name>, it refreshes fine. Did something change where you can’t do a snap refresh to update all snaps or has this always been the case?
Hi @kileyhykawy-nureva , have you tried logging out (snap logout) and logging in(snap login) again?
Regards,
Puru
Yes, I did try snap logout and login again several times and no difference.
Hi kileyhykawy-nureva,
I want to double check, that if you do snap refresh that works for all private snaps?
Can you confirm that you can individually update all of the snaps private and public, one at a time without any failure?
We have identified the issue. Thanks for making us aware.
We will share the fix PR soon. It should be available to test in edge by the end of the week, and part of snapd 2.76 release that will be in stable around 10 July.
Hello! I’ve made the PR here: https://github.com/canonical/snapd/pull/16764
Thanks! Glad I could help.
This fix will be available in snapd 2.75.1. We are busy with this release and expect it to become available in beta channel in the next couple of days.