Snap build failed to upload to the store (hard-expired auth)

Bug #1722904 reported by Matias Bordese
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

Previously authorized snap fails to automatically upload new builds to the store with an unauthorized response after a year: "Store upload failed: Authorization failed." This is because issued store macaroon auth hard-expires after 1 year, requiring a full re-authentication.

Right now the work-around is to disable the "Automatically upload to store option", saving and then re-enabling it, which will force a hard refresh of the credentials used for uploading to the store.

Revision history for this message
Colin Watson (cjwatson) wrote :

A better workaround is to go to the snap's +authorize page (e.g. https://code.launchpad.net/~snappy-dev/+snap/core/+authorize in this case).

Leaving aside improvements to the store's authz workflow which I think probably have to be out of scope for this bug, the user should have got an email instructing them to go to +authorize; but since email is often ignored or lost for some reason, I think a reasonable additional workaround would be to notice this type of failure and include a link on the build page as well.

tags: added: confusing-ui internal-api lp-snappy
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Colin Watson (cjwatson) wrote :

The lost-email mystery is solved, at least:

<mvo> cjwatson: aha, I think I know what is going on. only the "canonical-store" account was registered for this on my side, not my personal mail, this is why it only went there and not into my inbox. thanks for your help, this makes sense now

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.