Uploading a snap that requires a manual review shows an error that's not great

Bug #1602095 reported by Leo Arias
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Snapcraft
Fix Released
High
Joe Talbott
Software Center Agent
New
Undecided
Unassigned

Bug Description

When I upload a snap that requires a manual review, I get this error:

Publishing checks failed.
To release this to stable channel, please request a review on the snapcraft list.
Use devmode in the edge or beta channels to disable confinement.

There are some things I don't like about this.

It mentions the snapcraft list. I know what that is, but I bet many people will not. Maybe add a link, or use the email address?

It says I can use devmode. In this case, devmode will not help because my mistake is that I set an architecture but didn't include any binaries for that archs. I don't know how to fix this. Some ideas that come to mind are to show in the error the reason why the publishing checks failed, or run the checks before attempting the upload.

I'm filling this bug here to start the discussion.

Tags: store
Revision history for this message
Mark Shuttleworth (sabdfl) wrote : Re: [Bug 1602095] [NEW] Uploading a snap that requires a manual review shows an error that's not great

On 11/07/16 21:53, Leo Arias wrote:
> It mentions the snapcraft list. I know what that is, but I bet many
> people will not. Maybe add a link, or use the email address?

yes, let's say '<email address hidden> mailing list'

> It says I can use devmode. In this case, devmode will not help because
> my mistake is that I set an architecture but didn't include any binaries
> for that archs. I don't know how to fix this. Some ideas that come to
> mind are to show in the error the reason why the publishing checks
> failed, or run the checks before attempting the upload.

Ye, I think we want to provide more specific feedback on the checks that
failed and how the user can address them.

Mark

Revision history for this message
Sergio Schvezov (sergiusens) wrote :

El 12/07/16 a las 10:26, Mark Shuttleworth escribió:
> On 11/07/16 21:53, Leo Arias wrote:
> > It mentions the snapcraft list. I know what that is, but I bet many
> > people will not. Maybe add a link, or use the email address?
>
> yes, let's say '<email address hidden> mailing list'

We need to create such list, can we?
>
> > It says I can use devmode. In this case, devmode will not help because
> > my mistake is that I set an architecture but didn't include any binaries
> > for that archs. I don't know how to fix this. Some ideas that come to
> > mind are to show in the error the reason why the publishing checks
> > failed, or run the checks before attempting the upload.
>
> Ye, I think we want to provide more specific feedback on the checks that
> failed and how the user can address them.

Certainly, but this requires the store to provide such feedback, there's already a bug open for this but I will link this one as well just in case as the reasoning for it is better explained here.
>
> Mark
>

Revision history for this message
Leo Arias (elopio) wrote :

From Thomi in a dup:
"up to this point I've never had to open my browser to build, push, and release a snap. A user may well not know that 'myapps.developer.ubuntu.com' is a thing. Ideally we'd add something like:

"For more information about the specific error, please see: http://myapps...."

*or* perhaps we could include the review issues in the snapcraft output. Either way, we need to give the user more information than we do currently."

tags: added: store
Changed in snapcraft:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Sergio Schvezov (sergiusens) wrote :
Changed in snapcraft:
status: Triaged → In Progress
milestone: none → 2.27
assignee: nobody → Joe Talbott (joetalbott)
status: In Progress → Fix Committed
Changed in snapcraft:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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