Inform people kindly and understandably when they upload a debug build to the store by accident
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Click Reviewers tools (obsolete) |
Fix Released
|
Medium
|
Daniel Holbach |
Bug Description
I built my app and ran it on the emulator. I then uploaded that click package (because I was happy with it) to the click store, and it was rejected with messages:
found unexpected Exec with architecture 'all': ./qtcdevicedebu
(REJECT) reserved policy group 'debug': not for production use
This is because I uploaded the run-on-the-emulator click package, rather than using the Publish tab in Ubuntu SDK to make a proper release build and uploading that.
However, it's hard to tell that that's what the problem was. The store front end could be a lot more helpful here; in particular, in this situation, the store could say something like:
Rejected because you uploaded a debug build of your app. Debug builds are made to test your app on devices and emulators; to upload to the store, you need to create a release build. The Publish tab in Ubuntu SDK lets you create a release build click package; increase your version number and then create a release build click package from the Publish tab and then upload it to successfully publish to the store.
Related branches
- Daniel Holbach (community): Approve
-
Diff: 57 lines (+12/-3)2 files modifiedclickreviews/cr_security.py (+7/-2)
debian/changelog (+5/-1)
affects: | software-center-agent → click-reviewers-tools |
Changed in click-reviewers-tools: | |
importance: | Undecided → Medium |
Changed in click-reviewers-tools: | |
assignee: | nobody → Daniel Holbach (dholbach) |
status: | New → In Progress |
Changed in click-reviewers-tools: | |
status: | In Progress → Fix Committed |
Changed in click-reviewers-tools: | |
status: | Fix Committed → Fix Released |