You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Jesse MacFadyen (Created) (JIRA)" <ji...@apache.org> on 2011/12/08 19:33:40 UTC
[jira] [Created] (CB-109) PhoneGap Library confuses the Marketplace
capability detection
PhoneGap Library confuses the Marketplace capability detection
--------------------------------------------------------------
Key: CB-109
URL: https://issues.apache.org/jira/browse/CB-109
Project: Apache Callback
Issue Type: Bug
Components: WP7
Affects Versions: 1.2.0
Reporter: Jesse MacFadyen
Assignee: Jesse MacFadyen
Priority: Minor
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
[jira] [Commented] (CB-109) PhoneGap Library confuses the
Marketplace capability detection
Posted by "Dirkjan Mollema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402301#comment-13402301 ]
Dirkjan Mollema commented on CB-109:
------------------------------------
I can confirm this workaround.
The easiest way to do this is to open the source in Visual Studio, but open the CordovaClassLibBare. The Bare one only includes the basic modules, you can add modules you need.
Then build the solution and copy the new dll to your Phonegap project.
> 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: Minor
> 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
[jira] [Resolved] (CB-109) PhoneGap Library confuses the
Marketplace capability detection
Posted by "Jesse MacFadyen (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Comment Edited] (CB-109) PhoneGap Library confuses the
Marketplace capability detection
Posted by "Dirkjan Mollema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280843#comment-13280843 ]
Dirkjan Mollema edited comment on CB-109 at 5/22/12 9:43 AM:
-------------------------------------------------------------
I confirm this. Is there a workaround available for this?
Having simple apps which require all the user permissions will make users hesitate to download and install the app.
Imo this issue should have a higher priority
was (Author: sano):
I confirm this. Is there a workaround available for this?
Having simple apps which require all the user permissions will make users hesitate to download and install this.
Imo this issue should have a higher priority
> 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: Minor
> 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
[jira] [Commented] (CB-109) PhoneGap Library confuses the
Marketplace capability detection
Posted by "Dirkjan Mollema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280843#comment-13280843 ]
Dirkjan Mollema commented on CB-109:
------------------------------------
I confirm this. Is there a workaround available for this?
Having simple apps which require all the user permissions will make users hesitate to download and install this.
Imo this issue should have a higher priority
> 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: Minor
> 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
[jira] [Commented] (CB-109) PhoneGap Library confuses the
Marketplace capability detection
Posted by "Filip Maj (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402288#comment-13402288 ]
Filip Maj commented on CB-109:
------------------------------
First, we need to land support for programmatic installation of Cordova plugins. This is slated for 2.0; we are working hard to land this.
After that lands, then you as a user will be able to create a Cordova application and manually only add the plugins (APIs) that your application is using.
Until then, as a workaround: clone the source, remove any APIs (Commands) that your application is not using, build the library and rebuild your app.
> 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: Minor
> 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
[jira] [Commented] (CB-109) PhoneGap Library confuses the
Marketplace capability detection
Posted by "Christoph (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402180#comment-13402180 ]
Christoph commented on CB-109:
------------------------------
I agree, this is a show stopper. Please increase priority.
Any workaround would be appreciated.
> 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: Minor
> 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
[jira] [Updated] (CB-109) PhoneGap Library confuses the Marketplace
capability detection
Posted by "Jesse MacFadyen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse MacFadyen updated CB-109:
-------------------------------
Fix Version/s: 2.0.0
> PhoneGap Library confuses the Marketplace capability detection
> --------------------------------------------------------------
>
> Key: CB-109
> URL: https://issues.apache.org/jira/browse/CB-109
> Project: Apache Callback
> Issue Type: Bug
> Components: WP7
> Affects Versions: 1.2.0
> Reporter: Jesse MacFadyen
> Assignee: Jesse MacFadyen
> Priority: Minor
> 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
[jira] [Comment Edited] (CB-109) PhoneGap Library confuses the
Marketplace capability detection
Posted by "Dirkjan Mollema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402301#comment-13402301 ]
Dirkjan Mollema edited comment on CB-109 at 6/27/12 3:43 PM:
-------------------------------------------------------------
I can confirm this workaround.
The easiest way to do this is to open the source in Visual Studio, but open the CordovaClassLibBare. The Bare one only includes the basic modules, you can add modules you need.
Then build the solution and copy the new dll to your Cordova project (the app).
was (Author: sano):
I can confirm this workaround.
The easiest way to do this is to open the source in Visual Studio, but open the CordovaClassLibBare. The Bare one only includes the basic modules, you can add modules you need.
Then build the solution and copy the new dll to your Phonegap project.
> 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: Minor
> 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
[jira] [Updated] (CB-109) PhoneGap Library confuses the Marketplace
capability detection
Posted by "Jesse MacFadyen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse MacFadyen updated CB-109:
-------------------------------
Priority: Critical (was: Minor)
> 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