Comment 18 for bug 2019158

Thank you for the logs and the confirmation. I don't see anything out of the ordinary in the logs. Can you use `sudo systemctl edit snapd.service` (which will open an editor) to add the lines:
[Service]
Environment="SNAPD_DEBUG=1"
Environment="SNAPD_DEBUG_HTTP=3"

to snapd's override? This will add more information to the logs. Also, when this problem happens again can you run:
{ snap changes; sudo snap debug stacktraces; systemctl status --no-pager; } > snapd.log

Then close snapd with `systemctl stop snapd.{service,socket}`, copy the file `/var/lib/snapd/state.json` and send that file and the snapd.log file with the logs to me at `<email address hidden>`? Thank you.

To answer your question, the fact that the snap was downloaded again doesn't necessarily imply that it wasn't downloaded in the first place. This is because during an installation or refresh the downloaded snap is moved out of the cache. In that case, I'd expect there to be an auto-refresh attempt after the pre-download (even if it fails for some reason) but it seems like there isn't one. With the debug logs, we'll be able to get a better idea of what's happening.