[
https://issues.apache.org/jira/browse/CB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-109.
--------------------------------
Resolution: Fixed
This has been addressed with changes to the project structure.
The 'new' way to remove a capability and therefore the user presented
permission nag is to remove the assemblies and cordova commands from the
project.
The workaround verified by Dirkjan[~sano] is still available to projects using
external project linkage.
> PhoneGap Library confuses the Marketplace capability detection
> --------------------------------------------------------------
>
> Key: CB-109
> URL: https://issues.apache.org/jira/browse/CB-109
> Project: Apache Cordova
> Issue Type: Bug
> Components: WP7
> Affects Versions: 1.2.0
> Reporter: Jesse MacFadyen
> Assignee: Jesse MacFadyen
> Priority: Critical
> Fix For: 2.0.0
>
>
> Originally filed here: https://github.com/phonegap/phonegap-wp7/issues/40
> When WP7 applications are submitted to the marketplace the phone capabilities
> they use are determined via static code analysis. This means that
> applications which use PhoneGap are listed as having the following
> capabilities, regardless of whether they are used or not:
> data services, movement and directional sensor, microphone, music and video
> library, owner identity, camera, contacts, camera, compass
> See this article for more details:
> http://www.scottlogic.co.uk/blog/colin/2011/11/property-finder-the-first-html5-based-windows-phone-7-application/#comment-95352
> Unless the marketplace approval changes, I think PhoenGap for WP7 needs to be
> split into multiple assemblies based on the phone capability it uses.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
