Comment 2 for bug 1722904

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.