Closed Bug 1192776 Opened 10 years ago Closed 10 years ago

Provide a more suggestive message when validation fails

Categories

(Marketplace Graveyard :: Validation, defect)

Avenir
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX
2015-08-11

People

(Reporter: madalin.cotetiu, Unassigned)

References

()

Details

Steps to reproduce: 1. Validate an app containing in manifest requirement for a permission but with "type" : "privileged" missing. Expected results: Validation is failing and a suggestive message is displayed stating that the app needs to be privileged in order to pass validation. Actual results: The validation is failing, a confusing message is displayed: "App requested unavailable permission". Notes/Issues: Verified in FF42(Win7) Issue can be reproduced in mp-dev and mp-stage. Screencast for this issue: http://screencast.com/t/WsGMIpO9VX I have used a packaged app with the following manifest: { "fullscreen": "true", "name": "permissionTest", "default_locale": "en", "icons": { "32": "/icons/32.png", "256": "/icons/256.png", "16": "/icons/16.png" }, "installs_allowed_from": [ "*" ], "description": "testUpdatePackageApp01", "version": "1.0", "launch_path": "/index.html", "developer": { "url": "https://mozilla.org", "name": "Mozilla" }, "locales": { "pt-br": { "name": "testPT-BR", "description": "Ousmemy shadtomcon tuourdwig yleri telbatwhim slilstwhoomre acrandmeasent floonlyl pondwioxer halfanan broardbaspled shadtomcon abertirym bipostred exingchar." }, "es": { "name": "testES", "description": "Itnowing telbatwhim io omcunmane ereaser adealor moundetmak io moundetmak nerthocylfon itnowing dispeent slilstwhoomre io aclivtournban." } }, "orientation": "landscape", "permissions": { "contacts": { "description": "Required for autocompletion in the share screen", "access": "readcreate" }, "moz-external-app": { "description": "test permission" } } }
While it could probably be clearer, the message returned is accurate.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.