[jira] [Updated] (CB-9460) Media Capture docs define missing properties
[ https://issues.apache.org/jira/browse/CB-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen updated CB-9460: Priority: Minor (was: Critical) > Media Capture docs define missing properties > > > Key: CB-9460 > URL: https://issues.apache.org/jira/browse/CB-9460 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media Capture >Reporter: Jesse MacFadyen >Assignee: Jesse MacFadyen >Priority: Minor > Labels: Android,, WP8, Windows,, iOS, > > The readme says that the plugin has the following properties: > supportedAudioModes: The audio recording formats supported by the device. > supportedImageModes: The recording image sizes and formats supported by the > device. > supportedVideoModes: The recording video resolutions and formats supported by > the device. > There is a test to make sure the properties exist, but they are ALWAYS empty > arrays. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-565) Somehow document how certain objects extend from others in cordova-js
[ https://issues.apache.org/jira/browse/CB-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-565. - Resolution: Fixed > Somehow document how certain objects extend from others in cordova-js > - > > Key: CB-565 > URL: https://issues.apache.org/jira/browse/CB-565 > Project: Apache Cordova > Issue Type: Improvement > Components: Docs >Affects Versions: 1.6.1, 1.7.0, Master >Reporter: Filip Maj >Assignee: Michael Brooks >Priority: Minor > Fix For: Master > > > Certain objects available to cordova users extend from properties of other > objects. In particular: > * FileEntry and DirectoryEntry extends Entry > * MediaFile extends File -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10029) Rename edge docs to dev
[ https://issues.apache.org/jira/browse/CB-10029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020213#comment-15020213 ] ASF subversion and git services commented on CB-10029: -- Commit 4e345abd9cf62672dfbbc3759f2f52191530bb99 in cordova-docs's branch refs/heads/master from [~dblotsky] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=4e345ab ] CB-10029 Adding edge -> dev redirect. > Rename edge docs to dev > --- > > Key: CB-10029 > URL: https://issues.apache.org/jira/browse/CB-10029 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Richard B Knoll >Assignee: Richard B Knoll > > Renaming edge to dev to prevent confusion among website visitors. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10056) sitemap.xml should have weights and change frequencies
[ https://issues.apache.org/jira/browse/CB-10056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020214#comment-15020214 ] ASF subversion and git services commented on CB-10056: -- Commit 4284140540c379c55ae672d2ff787f664b70a43d in cordova-docs's branch refs/heads/master from [~dblotsky] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=4284140 ] CB-10056 Adding more metadata for sitemap.xml. > sitemap.xml should have weights and change frequencies > -- > > Key: CB-10056 > URL: https://issues.apache.org/jira/browse/CB-10056 > Project: Apache Cordova > Issue Type: Improvement > Components: Website >Reporter: Dmitry Blotsky > Original Estimate: 2h > Remaining Estimate: 2h > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10056) sitemap.xml should have weights and change frequencies
[ https://issues.apache.org/jira/browse/CB-10056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020216#comment-15020216 ] ASF subversion and git services commented on CB-10056: -- Commit aa9e3195a60a7bec986467d42aa717d685c1dfa9 in cordova-docs's branch refs/heads/master from [~dblotsky] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=aa9e319 ] CB-10056 Making latest version more important, and dev version _less_ important. > sitemap.xml should have weights and change frequencies > -- > > Key: CB-10056 > URL: https://issues.apache.org/jira/browse/CB-10056 > Project: Apache Cordova > Issue Type: Improvement > Components: Website >Reporter: Dmitry Blotsky > Original Estimate: 2h > Remaining Estimate: 2h > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10020) Indicate latest version in version dropdown
[ https://issues.apache.org/jira/browse/CB-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020215#comment-15020215 ] ASF subversion and git services commented on CB-10020: -- Commit cb0c09bebc0396a7f66861d9467471e2da9ef944 in cordova-docs's branch refs/heads/master from [~dblotsky] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=cb0c09b ] CB-10020 Translating the (Latest) text in version dropdown. > Indicate latest version in version dropdown > --- > > Key: CB-10020 > URL: https://issues.apache.org/jira/browse/CB-10020 > Project: Apache Cordova > Issue Type: Improvement > Components: Docs >Reporter: Richard B Knoll >Assignee: Richard B Knoll >Priority: Minor > > Make it clear what version is latest in the dropdown version list for the docs -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10058) Add automatic checks for validity of images, links, and HTML
Dmitry Blotsky created CB-10058: --- Summary: Add automatic checks for validity of images, links, and HTML Key: CB-10058 URL: https://issues.apache.org/jira/browse/CB-10058 Project: Apache Cordova Issue Type: Task Components: Website Reporter: Dmitry Blotsky Right now, some links are broken, some HTML might be invalid, and some images are missing/incorrect. This task calls for automatic linting and testing of the website to rectify these issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10057) removing tag wildcard does not remove ATS entry
Shazron Abdullah created CB-10057: - Summary: removing tag wildcard does not remove ATS entry Key: CB-10057 URL: https://issues.apache.org/jira/browse/CB-10057 Project: Apache Cordova Issue Type: Bug Components: CordovaLib Affects Versions: 5.3.3 Reporter: Shazron Abdullah Assignee: Shazron Abdullah In config.xml: Add: Then `cordova prepare` NSAllowArbitraryLoads is still true in the Info.plist -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10048) clobbering of tags to ATS directives
[
https://issues.apache.org/jira/browse/CB-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah resolved CB-10048.
---
Resolution: Fixed
> clobbering of tags to ATS directives
> -
>
> Key: CB-10048
> URL: https://issues.apache.org/jira/browse/CB-10048
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: 5.3.3
>Reporter: Shazron Abdullah
>Assignee: Shazron Abdullah
> Labels: cordova-ios-4.0.x, iOS
>
> Example:
> {code}
> http://*.apache.org />
> https://*.apache.org />
> {code}
> In this case, we want the http exception, but it gets clobbered by the
> following tag with https.
> The parser should do a once over sweep to consolidate the tags, and re-run
> the generator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10048) clobbering of tags to ATS directives
[
https://issues.apache.org/jira/browse/CB-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020173#comment-15020173
]
ASF subversion and git services commented on CB-10048:
--
Commit fc74c6397d001db8513269da0fe197edbe87ad4a in cordova-lib's branch
refs/heads/master from [~shazron]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=fc74c63 ]
CB-10048 - clobbering of tags to ATS directives
> clobbering of tags to ATS directives
> -
>
> Key: CB-10048
> URL: https://issues.apache.org/jira/browse/CB-10048
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: 5.3.3
>Reporter: Shazron Abdullah
>Assignee: Shazron Abdullah
> Labels: cordova-ios-4.0.x, iOS
>
> Example:
> {code}
> http://*.apache.org />
> https://*.apache.org />
> {code}
> In this case, we want the http exception, but it gets clobbered by the
> following tag with https.
> The parser should do a once over sweep to consolidate the tags, and re-run
> the generator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10055) Cordova implementation for Geolocation plugin has wrong type for watchId
[ https://issues.apache.org/jira/browse/CB-10055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019260#comment-15019260 ] Jesse MacFadyen commented on CB-10055: -- (watchPosition)Returns String: returns a watch id that references the watch position interval. (clearWatch)Parameters watchID: The id of the watchPosition interval to clear. (String) Looks right to me?! > Cordova implementation for Geolocation plugin has wrong type for watchId > > > Key: CB-10055 > URL: https://issues.apache.org/jira/browse/CB-10055 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaCommon, CordovaLib >Reporter: Yasser Elsayed > > See the definition of the Cordova interface of the Geolocation plugin here: > http://docs.phonegap.com/en/edge/cordova_geolocation_geolocation.md.html#geolocation.watchPosition > The watchId variables in watchPosition() and clearWatch() are declared as > numbers, but that does not match the HTML5 specs for the GeoLocation on w3, > which state it's a string. See: > http://dev.w3.org/geo/api/spec-source.html#geolocation -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8917) Add api/way to get plugins results even when Cordova activity restarts
[ https://issues.apache.org/jira/browse/CB-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019247#comment-15019247 ] ASF GitHub Bot commented on CB-8917: Github user jasongin commented on the pull request: https://github.com/apache/cordova-docs/pull/428#issuecomment-158571671 Looks good. Very well-written! > Add api/way to get plugins results even when Cordova activity restarts > > > Key: CB-8917 > URL: https://issues.apache.org/jira/browse/CB-8917 > Project: Apache Cordova > Issue Type: Improvement > Components: Android >Reporter: Bnaya > > In android when you have a plugin that opens new activity the CordovaActivity > will be killed and you won't get the result from the plugin. > The new activity will get the results but because the plugin objects are dead > and the webview reloaded you can get the data to the js callback. > The most noticeable example is the camera plugin. (And maybe its the same > with even more platforms) > possible solution for this is to add metadata to the device ready event with > incoming data from plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10056) sitemap.xml should have weights and change frequencies
Dmitry Blotsky created CB-10056: --- Summary: sitemap.xml should have weights and change frequencies Key: CB-10056 URL: https://issues.apache.org/jira/browse/CB-10056 Project: Apache Cordova Issue Type: Improvement Components: Website Reporter: Dmitry Blotsky -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-8863) Fix potential problems with blocks usage in core plugins
[ https://issues.apache.org/jira/browse/CB-8863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-8863. - Resolution: Fixed > Fix potential problems with blocks usage in core plugins > > > Key: CB-8863 > URL: https://issues.apache.org/jira/browse/CB-8863 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > Labels: cordova-ios-5.0.x > > Audit the core plugins to check for proper blocks usage. > Problems that I see can be summed up in this (fixed) code: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292-L313 > 1. You need a weak reference to "self" in blocks to prevent retain cycle > problems. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292 > 2. Anything that calls UIKit methods, which includes plugins that write > JavaScript back to the UIWebView (commandDelegate functions), must be called > in the main thread. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L308-L310 > (UPDATE: we actually already handle this in evalJS) > 3. Avoid creating private variables like this in the first place -- I would > create a class extension which will effectively have "private" properties > (nothing is truly private in objc). This is to avoid this situation in the > block where you have to cast the weak self into a strong self (and check it's > still around), just to access a private variable: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L298-L304 > Of course since we are modifying UIKit items here, rule 2 above also applies. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8863) Fix potential problems with blocks usage in core plugins
[ https://issues.apache.org/jira/browse/CB-8863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019234#comment-15019234 ] ASF GitHub Bot commented on CB-8863: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-file/pull/150 > Fix potential problems with blocks usage in core plugins > > > Key: CB-8863 > URL: https://issues.apache.org/jira/browse/CB-8863 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > Labels: cordova-ios-5.0.x > > Audit the core plugins to check for proper blocks usage. > Problems that I see can be summed up in this (fixed) code: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292-L313 > 1. You need a weak reference to "self" in blocks to prevent retain cycle > problems. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292 > 2. Anything that calls UIKit methods, which includes plugins that write > JavaScript back to the UIWebView (commandDelegate functions), must be called > in the main thread. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L308-L310 > (UPDATE: we actually already handle this in evalJS) > 3. Avoid creating private variables like this in the first place -- I would > create a class extension which will effectively have "private" properties > (nothing is truly private in objc). This is to avoid this situation in the > block where you have to cast the weak self into a strong self (and check it's > still around), just to access a private variable: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L298-L304 > Of course since we are modifying UIKit items here, rule 2 above also applies. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8863) Fix potential problems with blocks usage in core plugins
[ https://issues.apache.org/jira/browse/CB-8863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019233#comment-15019233 ] ASF subversion and git services commented on CB-8863: - Commit a955993bfc5adf08271305f3c6eea3b4f285b07d in cordova-plugin-file's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file.git;h=a955993 ] CB-8863 [ios] Fix block usage of self > Fix potential problems with blocks usage in core plugins > > > Key: CB-8863 > URL: https://issues.apache.org/jira/browse/CB-8863 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > Labels: cordova-ios-5.0.x > > Audit the core plugins to check for proper blocks usage. > Problems that I see can be summed up in this (fixed) code: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292-L313 > 1. You need a weak reference to "self" in blocks to prevent retain cycle > problems. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292 > 2. Anything that calls UIKit methods, which includes plugins that write > JavaScript back to the UIWebView (commandDelegate functions), must be called > in the main thread. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L308-L310 > (UPDATE: we actually already handle this in evalJS) > 3. Avoid creating private variables like this in the first place -- I would > create a class extension which will effectively have "private" properties > (nothing is truly private in objc). This is to avoid this situation in the > block where you have to cast the weak self into a strong self (and check it's > still around), just to access a private variable: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L298-L304 > Of course since we are modifying UIKit items here, rule 2 above also applies. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8863) Fix potential problems with blocks usage in core plugins
[ https://issues.apache.org/jira/browse/CB-8863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019176#comment-15019176 ] ASF GitHub Bot commented on CB-8863: GitHub user purplecabbage opened a pull request: https://github.com/apache/cordova-plugin-file/pull/150 CB-8863 [ios] Fix block usage of self You can merge this pull request into a Git repository by running: $ git pull https://github.com/purplecabbage/cordova-plugin-file CB-8863 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-file/pull/150.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #150 commit a955993bfc5adf08271305f3c6eea3b4f285b07d Author: Jesse MacFadyen Date: 2015-11-21T00:24:31Z CB-8863 [ios] Fix block usage of self > Fix potential problems with blocks usage in core plugins > > > Key: CB-8863 > URL: https://issues.apache.org/jira/browse/CB-8863 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > Labels: cordova-ios-5.0.x > > Audit the core plugins to check for proper blocks usage. > Problems that I see can be summed up in this (fixed) code: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292-L313 > 1. You need a weak reference to "self" in blocks to prevent retain cycle > problems. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292 > 2. Anything that calls UIKit methods, which includes plugins that write > JavaScript back to the UIWebView (commandDelegate functions), must be called > in the main thread. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L308-L310 > (UPDATE: we actually already handle this in evalJS) > 3. Avoid creating private variables like this in the first place -- I would > create a class extension which will effectively have "private" properties > (nothing is truly private in objc). This is to avoid this situation in the > block where you have to cast the weak self into a strong self (and check it's > still around), just to access a private variable: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L298-L304 > Of course since we are modifying UIKit items here, rule 2 above also applies. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9445) executeScript callbacks not working for iOS
[ https://issues.apache.org/jira/browse/CB-9445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019156#comment-15019156 ] ASF GitHub Bot commented on CB-9445: Github user jcesarmobile commented on the pull request: https://github.com/apache/cordova-plugin-inappbrowser/pull/125#issuecomment-158564977 tested and working fine > executeScript callbacks not working for iOS > --- > > Key: CB-9445 > URL: https://issues.apache.org/jira/browse/CB-9445 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 5.1.1 > Environment: Cordova 5.1.1 (CLI), ios 3.8.0, android 4.0.2, > cordova-plugin-inappbrowser 1.0.1 (NPM) >Reporter: Scott Seitz >Assignee: jcesarmobile > Labels: Triaged, iOS > > Can someone please check to see if they are encountering the same problem I > am in the environment I've listed? (latest released builds of everything I > think) > I open an inappbrowser window and then run an executeScript command using > "code:" (not "file:"). Everything works fine on Android, but on iOS, it > simply will NOT fire the callback function after executing the injected code. > Make the "code:" as simple as you like to test it and see if you can get a > callback to fire. I've dumbed it down as much as possible and can't get one > to fire. I know that all instances of code I've injected have run fine in > the iab by using the console (against the iab) to check for the variables I > was creating in the code. I can't even get a callback to fire that doesn't > expect a parameter to be passed back... > Many thanks, > Scott -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8940) [Windows] Camera image z-index is too low. It sits behind JQuery mobile UI Elements (header / footer)
[
https://issues.apache.org/jira/browse/CB-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard B Knoll closed CB-8940.
---
Resolution: Fixed
> [Windows] Camera image z-index is too low. It sits behind JQuery mobile UI
> Elements (header / footer)
> -
>
> Key: CB-8940
> URL: https://issues.apache.org/jira/browse/CB-8940
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Camera
>Affects Versions: 4.1.0
> Environment: Windows Emulator / Nokia Lumia 920
>Reporter: david marshall
>Assignee: Raghav
> Labels: windows
>
> Changing the values in CameraProxy.js to below works a treat
> // z-index style element for capturePreview and captureCancelButton elts
> // is necessary to avoid overriding by another page
> elements, -1 sometimes is not enough
> capturePreview.style.cssText = "position: fixed; left: 0;
> top: 0; width: 100%; height: 100%; z-index: ";
> // Create cancel button
> captureCancelButton = document.createElement("button");
> captureCancelButton.innerText = "Cancel";
> captureCancelButton.style.cssText = "position: fixed;
> right: 0; bottom: 0; display: block; margin: 20px; z-index: 1";
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10055) Cordova implementation for Geolocation plugin has wrong type for watchId
[
https://issues.apache.org/jira/browse/CB-10055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yasser Elsayed updated CB-10055:
Description:
See the definition of the Cordova interface of the Geolocation plugin here:
http://docs.phonegap.com/en/edge/cordova_geolocation_geolocation.md.html#geolocation.watchPosition
The watchId variables in watchPosition() and clearWatch() are declared as
numbers, but that does not match the HTML5 specs for the GeoLocation on w3,
which state it's a string. See:
http://dev.w3.org/geo/api/spec-source.html#geolocation
was:
This is the definition of Geolocation in lib.d.ts:
{code:xml}
interface Geolocation {
clearWatch(watchId: number): void;
getCurrentPosition(successCallback: PositionCallback, errorCallback?:
PositionErrorCallback, options?: PositionOptions): void;
watchPosition(successCallback: PositionCallback, errorCallback?:
PositionErrorCallback, options?: PositionOptions): number;
}
{code}
watchId variables in watchPosition() and clearWatch() are declared as numbers,
but actually the Cordova documentation on w3 states it's a string. See:
http://dev.w3.org/geo/api/spec-source.html#geolocation
Component/s: CordovaLib
CordovaCommon
Summary: Cordova implementation for Geolocation plugin has wrong type
for watchId (was: interface Geolocation (lib.d.ts) has the wrong type for
watchId)
> Cordova implementation for Geolocation plugin has wrong type for watchId
>
>
> Key: CB-10055
> URL: https://issues.apache.org/jira/browse/CB-10055
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaCommon, CordovaLib
>Reporter: Yasser Elsayed
>
> See the definition of the Cordova interface of the Geolocation plugin here:
> http://docs.phonegap.com/en/edge/cordova_geolocation_geolocation.md.html#geolocation.watchPosition
> The watchId variables in watchPosition() and clearWatch() are declared as
> numbers, but that does not match the HTML5 specs for the GeoLocation on w3,
> which state it's a string. See:
> http://dev.w3.org/geo/api/spec-source.html#geolocation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10055) interface Geolocation (lib.d.ts) has the wrong type for watchId
Yasser Elsayed created CB-10055:
---
Summary: interface Geolocation (lib.d.ts) has the wrong type for
watchId
Key: CB-10055
URL: https://issues.apache.org/jira/browse/CB-10055
Project: Apache Cordova
Issue Type: Bug
Reporter: Yasser Elsayed
This is the definition of Geolocation in lib.d.ts:
{code:xml}
interface Geolocation {
clearWatch(watchId: number): void;
getCurrentPosition(successCallback: PositionCallback, errorCallback?:
PositionErrorCallback, options?: PositionOptions): void;
watchPosition(successCallback: PositionCallback, errorCallback?:
PositionErrorCallback, options?: PositionOptions): number;
}
{code}
watchId variables in watchPosition() and clearWatch() are declared as numbers,
but actually the Cordova documentation on w3 states it's a string. See:
http://dev.w3.org/geo/api/spec-source.html#geolocation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-9266) "cordova run" for iOS does not see non-running emulators
[
https://issues.apache.org/jira/browse/CB-9266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Blotsky closed CB-9266.
--
> "cordova run" for iOS does not see non-running emulators
>
>
> Key: CB-9266
> URL: https://issues.apache.org/jira/browse/CB-9266
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: Mac OS X Yosemite
>Reporter: Dmitry Blotsky
>Assignee: Simon MacDonald
> Labels: cordova-ios-4.0.x, found-by-ci, ios, simulator
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Steps to reproduce:
> 1. Open the iOS Simulator by opening XCode and clicking {{XCode > Open
> Developer Tool > iOS Simulator}}
> 2. While in the simulator, open the simulator device manager by clicking
> {{Hardware > Device > Manage Devices ...}}
> 3. Make sure that some simulators exist, but that there is no iPhone 6
> simulator
> 4. Create a blank Cordova app and add the iOS platform
> 5. Run the app without specifying a simulator
> Expected: running on another simulator
> Actual: inability to find iPhone 6 simulator
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8848) FileTransfer test failures on iOS and WP8
[
https://issues.apache.org/jira/browse/CB-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Blotsky closed CB-8848.
--
> FileTransfer test failures on iOS and WP8
> -
>
> Key: CB-8848
> URL: https://issues.apache.org/jira/browse/CB-8848
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
>Affects Versions: Master
> Environment: iOS
>Reporter: Dmitry Blotsky
> Labels: found-by-ci, ios, plugin-file-transfer, test-fail
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Test failures here:
> [http://ci.apache.org/builders/cordova-ios/builds/390/steps/running-tests/logs/stdio]
> Last failure also on WP8 here:
> [http://ci.apache.org/builders/cordova-wp8/builds/1071/steps/running-tests/logs/stdio]
> {noformat}
> cordova-plugin-file-transfer-tests.tests >> FileTransfer methods download
> filetransfer.spec.6 should get 401 status on http basic auth failure
> cordova-plugin-file-transfer-tests.tests >> FileTransfer methods download
> filetransfer.spec.11 should call the error callback on abort()
> cordova-plugin-file-transfer-tests.tests >> FileTransfer methods download
> filetransfer.spec.10 should be stopped by abort() right away
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8749) FileTransfer test failure often crashes Android test app
[
https://issues.apache.org/jira/browse/CB-8749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Blotsky closed CB-8749.
--
> FileTransfer test failure often crashes Android test app
>
>
> Key: CB-8749
> URL: https://issues.apache.org/jira/browse/CB-8749
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
>Affects Versions: Master
> Environment: Android 21 on Nexus S emulator on Windows
>Reporter: Dmitry Blotsky
>Priority: Critical
> Labels: cordova-medic, crash, file-transfer, found-by-ci, medic,
> mobilespec
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Steps to reproduce:
> 1. Create mobilespec app with {{--android}} for platform
> 2. Run {{cordova-medic/bin/updateconfig.js --android}} from a directory above
> the created mobilespec app
> 3. Run the app with {{cordova run android -- --ant --debug}}
> 4. Wait for the app to open, and then click the buttons to start the Auto
> tests
> 5. Run `adb logcat` to capture the output
> App runs and often (but not always) crashes with the following exception in
> the {{logcat}} output:
> {noformat}
> D/FileTransfer( 2225): download http://cordova-filetransfer.jitsu.com/404 to
> file:///data/data/org.apache.mobilespec/files/files/testFile.txt
> D/FileTransfer( 2225): Download file:http://cordova-filetransfer.jitsu.com/404
> E/FileTransfer( 2225):
> {"code":1,"source":"http:\/\/cordova-filetransfer.jitsu.com\/404","target":"file:\/\/\/data\/data\/org.apache.mobilespec\/files\/files\/testFile.txt","body":"You
> requested a
> 404","http_status":404,"exception":"http:\/\/cordova-filetransfer.jitsu.com\/404"}
> E/FileTransfer( 2225): java.io.FileNotFoundException:
> http://cordova-filetransfer.jitsu.com/404
> E/FileTransfer( 2225): at
> com.android.okhttp.internal.http.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:197)
> E/FileTransfer( 2225): at
> org.apache.cordova.filetransfer.FileTransfer.getInputStream(FileTransfer.java:556)
> E/FileTransfer( 2225): at
> org.apache.cordova.filetransfer.FileTransfer.access$500(FileTransfer.java:69)
> E/FileTransfer( 2225): at
> org.apache.cordova.filetransfer.FileTransfer$4.run(FileTransfer.java:844)
> E/FileTransfer( 2225): at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
> E/FileTransfer( 2225): at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
> E/FileTransfer( 2225): at java.lang.Thread.run(Thread.java:818)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8820) Ensure platform guides are actual
[ https://issues.apache.org/jira/browse/CB-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-8820. -- > Ensure platform guides are actual > - > > Key: CB-8820 > URL: https://issues.apache.org/jira/browse/CB-8820 > Project: Apache Cordova > Issue Type: Task > Components: Docs >Reporter: Sergey Grebnov > Labels: android, docs, ios, windows > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8701) Documentation for versions 3.5 & 3.4 is unavailable for File API
[ https://issues.apache.org/jira/browse/CB-8701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-8701. -- > Documentation for versions 3.5 & 3.4 is unavailable for File API > - > > Key: CB-8701 > URL: https://issues.apache.org/jira/browse/CB-8701 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.4.0, 3.5.0 >Reporter: Omer Sinai > Labels: documentation > > I'm working with cordova version 3.5. There is a problem with the > documentation: http://docs.phonegap.com/en/3.5.0/index.html If one navigates > to the Plugins API documentation, from there any attempt to navigate a single > plugin API documentation results to *HTTP 404* not found error page on git > hub. It happens too for cordova 3.4 plugins documentation. But NOT in > cordova 3.6 . -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8885) Dead Link in Docs
[ https://issues.apache.org/jira/browse/CB-8885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-8885. -- > Dead Link in Docs > - > > Key: CB-8885 > URL: https://issues.apache.org/jira/browse/CB-8885 > Project: Apache Cordova > Issue Type: Bug > Components: Docs > Environment: the live site >Reporter: Erik >Priority: Minor > Labels: easyfix, longtime > Fix For: 5.2.0 > > > Trying to read how to compile and deploy to an iOS device. The page here : > http://cordova.apache.org/docs/en/3.4.0/guide_platforms_ios_index.md.html#iOS%20Platform%20Guide > has a dead link that leads to > https://developer.apple.com/legacy/library/documentation/Xcode/Conceptual/ios_development_workflow/00-About_the_iOS_Application_Development_Workflow/introduction.html#//apple_ref/doc/uid/TP40007959 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8821) Ensure Android Platform Guide is actual
[ https://issues.apache.org/jira/browse/CB-8821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-8821. -- > Ensure Android Platform Guide is actual > --- > > Key: CB-8821 > URL: https://issues.apache.org/jira/browse/CB-8821 > Project: Apache Cordova > Issue Type: Sub-task > Components: Docs >Reporter: Sergey Grebnov > > I see that some docs are outdated or not actual anymore so I want to improve > this. > Android: >1. Add changes in favor of replacing Ant w/ Gradle >a. Remove Ant from requirements >b. Replace Eclipse example w/ Android Studio as officially recommended > option/tool >2. Add more details about particular Android packages/components required > to be installed. > Android 5.0.1 (API 21) platform SDK > Android SDK Build-tools version 19.1.0 or higher > Android Support Repository (Extras) > 3. Add information how to list available deploy targets and run app on > specific target/device -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-5090) Storage plugin officially supported?
[
https://issues.apache.org/jira/browse/CB-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Blotsky closed CB-5090.
--
> Storage plugin officially supported?
> -
>
> Key: CB-5090
> URL: https://issues.apache.org/jira/browse/CB-5090
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Docs
>Affects Versions: 3.1.0
>Reporter: Peter
>Assignee: Andrew Grieve
>Priority: Minor
>
> Latest docs for Storage
> http://cordova.apache.org/docs/en/3.1.0/cordova_storage_storage.md.html#Storage
> says
> {quote}
> "Cordova provides access to both interfaces for the minority of devices that
> don't already support them"
> {quote}
> and also mentions
> {code}
>
>
>
> {code}
> But this plugin class doesn't seem to exist anymore in the (official ?) list
> https://github.com/search?p=1&q=%40apache+cordova-plugin&type=Repositories
> Furthemore, other JIRAs #CB-4505, #CB-4506 now advise to use
> *org.apache.cordova.websql* plugin instead...
> So latest advice, and latest docs seem to have conflicting information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-5116) Link to config.xml guide broken on Android Configuration guide
[ https://issues.apache.org/jira/browse/CB-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-5116. -- > Link to config.xml guide broken on Android Configuration guide > -- > > Key: CB-5116 > URL: https://issues.apache.org/jira/browse/CB-5116 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.1.0 >Reporter: Mike Billau >Assignee: Andrey Kurdyumov >Priority: Minor > > When on the Android Configuration Guide, there are links to the Config.xml > guide but the link is broken: > http://cordova.apache.org/docs/en/edge/guide_platforms_android_config.md.html#Android%20Configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-5089) console plugin not documented
[ https://issues.apache.org/jira/browse/CB-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-5089. -- > console plugin not documented > - > > Key: CB-5089 > URL: https://issues.apache.org/jira/browse/CB-5089 > Project: Apache Cordova > Issue Type: Improvement > Components: Docs, Plugin Console >Reporter: Brian LeRoux > Labels: easyfix, longtime > Fix For: 3.6.0, 5.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Blotsky closed CB-5122.
--
> Document supported workflows
>
>
> Key: CB-5122
> URL: https://issues.apache.org/jira/browse/CB-5122
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 3.1.0
>Reporter: Mike Billau
>Assignee: Mike Sierra
>
> Based on the recent discussion here [1]we should document the two different
> supported Cordova workflows: using the CLI, and using plugman and bin
> scripts.
> Some of this documentation already exists but needs to be clarified and
> improved:
> {{Overview guide --> "Development Paths" section}}. This talks about getting
> started with the CLI and then mentions that you can switch to the
> platform-specific SDK tools. This section should be rewritten to make it
> clear that there are two distinct workflows, and that both are okay and
> supported. It could list out some pros and cons of each workflow (I'm sure we
> won't have any trouble finding those ;)). It should be prescriptive in that
> users should be following one of the two workflows, but it shouldn't make any
> statements about which is better.
> {{"The Command-line Interface" guide}} --> The "CLI workflow" guide. It
> generally looks complete except for some missing functionality that is
> documented in the CLI's README.md file (tests, hooks, some commands (serve),
> some merges info).
> {{Platform Guides --> (Platform) --> (Platform) Command-line tools}} --> Each
> platform has a "Command-line tools" doc that explains all of the command line
> tools for that project and how to use them. We need to go through these
> guides and verify that they are up to date and include all of the lower level
> command line tools and scripts. It should read like a tutorial in the same
> way that the Command-line Interface guide does.
> {{"Using Plugman to Manage Plugins"}} First, this guide needs to get exposed;
> I can't find any way to get to this guide from the docs and even had to ask a
> user how she managed to find it (a link from Plugman's readme!). This guide
> needs to be expanded quite a bit; we can probably fold most/all of Plugman's
> README.md file into this guide since it will be platform agnostic.
> I think those are the only pieces in the docs that need to be changed.
> [1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
> [2]
> http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
> [3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-5095) Capture - API documentation / plugin.xml permission mismatch
[
https://issues.apache.org/jira/browse/CB-5095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Blotsky closed CB-5095.
--
> Capture - API documentation / plugin.xml permission mismatch
>
>
> Key: CB-5095
> URL: https://issues.apache.org/jira/browse/CB-5095
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Docs, Plugin Media Capture
>Affects Versions: 3.1.0
>Reporter: Peter
>Assignee: Mike Billau
>Priority: Minor
>
> The plugin for *cordova-plugin-media-capture* plugin.xml
> https://github.com/apache/cordova-plugin-media-capture/blob/3.1.0/plugin.xml
> says it needs the following permissions
> {code}
>
>
>
> {code}
> but the documentation
> http://cordova.apache.org/docs/en/3.1.0/cordova_media_capture_capture.md.html#Capture
> says it only needs
> {code}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-5064) docs do not describe the possibilities for the "plugin add" parameter
[ https://issues.apache.org/jira/browse/CB-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-5064. -- > docs do not describe the possibilities for the "plugin add" parameter > - > > Key: CB-5064 > URL: https://issues.apache.org/jira/browse/CB-5064 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Marcel Kinard >Assignee: Marcel Kinard >Priority: Minor > Fix For: 3.2.0 > > > The docs don't describe anything other than the npm-based id. See > https://groups.google.com/forum/#!topic/phonegap/PNrI03olx3M -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8729) Link to statusbar from plugin doc is 404ed
[ https://issues.apache.org/jira/browse/CB-8729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-8729. -- > Link to statusbar from plugin doc is 404ed > -- > > Key: CB-8729 > URL: https://issues.apache.org/jira/browse/CB-8729 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Raymond Camden >Priority: Minor > > The link to the Statusbar plugin from > http://cordova.apache.org/docs/en/4.0.0/cordova_plugins_pluginapis.md.html#Plugin%20APIs > leads to a 404. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-5034) Document plugin registry
[ https://issues.apache.org/jira/browse/CB-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-5034. -- > Document plugin registry > > > Key: CB-5034 > URL: https://issues.apache.org/jira/browse/CB-5034 > Project: Apache Cordova > Issue Type: Bug > Components: Docs, Registry >Affects Versions: Master >Reporter: Mike Billau >Assignee: Andrew Grieve > > I can't find any reference to the plugin registry anywhere in our > documentation. Am I looking in the wrong place or are we waiting for the web > component to be more polished before announcing the registry? > I think some places the registry should be mentioned: > Plugman: readme.md > CLI: > cordova help command (CB-5031) > readme.md > docs: > http://cordova.apache.org/docs/en/edge/guide_cli_index.md.html#The%20Command-line%20Interface > (I think it's best to split the "Add Platforms" section into "Add > Platforms" and "Add Plugins", and in this new section talk about adding > plugins, automatic plugin installation (plugin dependencies), and the > registry) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-5043) github.com/apache/cordova-ubuntu needs to be created
[ https://issues.apache.org/jira/browse/CB-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-5043. -- > github.com/apache/cordova-ubuntu needs to be created > > > Key: CB-5043 > URL: https://issues.apache.org/jira/browse/CB-5043 > Project: Apache Cordova > Issue Type: Bug > Components: Docs, Ubuntu >Reporter: Marcel Kinard >Priority: Minor > > ... and an "Ubuntu" component needs to be added to Jira. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-5055) Wrong hyperlink for plugin source code
[
https://issues.apache.org/jira/browse/CB-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Blotsky closed CB-5055.
--
> Wrong hyperlink for plugin source code
> --
>
> Key: CB-5055
> URL: https://issues.apache.org/jira/browse/CB-5055
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Docs
>Affects Versions: 3.1.0
>Reporter: Peter
>Assignee: Marcel Kinard
>Priority: Minor
> Fix For: 3.2.0
>
>
> The document "Android Plugins"
> http://cordova.apache.org/docs/en/3.1.0/guide_platforms_android_plugin.md.html#Android%20Plugins
> says
> {quote}
> *Use the Source*
> One of the best ways to prepare yourself to write your own plugin is to look
> over existing plugins.
> {quote}
> but the hyperlink in that text is to the git source directory to where
> plugins _used to be_ in v2.9, not where they are now...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8724) Windows Phone 8 Platform Guide missing information about needed Visual Studio Update
[ https://issues.apache.org/jira/browse/CB-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-8724. -- > Windows Phone 8 Platform Guide missing information about needed Visual Studio > Update > > > Key: CB-8724 > URL: https://issues.apache.org/jira/browse/CB-8724 > Project: Apache Cordova > Issue Type: Bug > Components: Docs, Windows 8, WP8 >Affects Versions: 4.0.0 > Environment: Windows 8.0 >Reporter: James Dubee >Assignee: Jesse MacFadyen >Priority: Minor > Labels: documentation > Original Estimate: 1h > Remaining Estimate: 1h > > The Windows 8 Platform Guide does not state that at least the Visual Studio > 2012 Update 2 must be installed on a user's computer in order to deploy via > the command-line using the Windows Phone 8.0 SDK. Otherwise, XapDeployCmd.exe > will not be present on the user's machine, and Cordova will not be able to > deploy applications via command-line for Windows Phone 8. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8715) Update docs for Android 4.0 features
[ https://issues.apache.org/jira/browse/CB-8715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-8715. -- > Update docs for Android 4.0 features > > > Key: CB-8715 > URL: https://issues.apache.org/jira/browse/CB-8715 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Docs >Reporter: Andrew Grieve >Assignee: Andrew Grieve > > * Gradle docs (done) > * Whitelist guide (done) > * Upgrade guide (done) > * Embedders guide -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8822) Ensure iOS Platform Guide is actual
[ https://issues.apache.org/jira/browse/CB-8822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-8822. -- > Ensure iOS Platform Guide is actual > --- > > Key: CB-8822 > URL: https://issues.apache.org/jira/browse/CB-8822 > Project: Apache Cordova > Issue Type: Sub-task > Components: Docs >Reporter: Sergey Grebnov > > I see that some docs are outdated or not actual anymore so I want to improve > this. > iOS: > 1. Xcode 4.x->5.x > 2. Add information about ios-sim required to deploy app from command line > 3. Add information how to list available deploy targets and run app on > specific target/device -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8823) Ensure Windows Platform Guide is actual
[ https://issues.apache.org/jira/browse/CB-8823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Blotsky closed CB-8823. -- > Ensure Windows Platform Guide is actual > --- > > Key: CB-8823 > URL: https://issues.apache.org/jira/browse/CB-8823 > Project: Apache Cordova > Issue Type: Sub-task > Components: Docs >Reporter: Sergey Grebnov > > I see that some docs are outdated or not actual anymore so I want to improve > this. > Windows: > 1. Remove 'To develop apps for Windows 8.0 only:' > 2. Hardware requirements to run Windows Phone emulator (Client Hyper-V > and Second Level Address Translation (SLAT)) > 3. Add information how to list available deploy targets and run app on > specific target/device -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10054) Random webview crash on Nexus6P
[ https://issues.apache.org/jira/browse/CB-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018750#comment-15018750 ] Edouard Lafargue commented on CB-10054: --- That's what I was afraid of, I understand. This happens on the latest WebView, unfortunately. Well, this affects only users who have a Nexus 6P so far, so unless I see an uptick in complaints, I'll continue distributing without an alternative webview for now. Thanks for the quick feedback! > Random webview crash on Nexus6P > --- > > Key: CB-10054 > URL: https://issues.apache.org/jira/browse/CB-10054 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0, 4.0.0, 5.0.0 > Environment: Only happens on Android 6.0 on Nexus 6P only (Adreno > GPU). This happens on all Cordova lib versions I have tried, even 5.0.0. >Reporter: Edouard Lafargue >Priority: Critical > > On Nexus 6P, the same code that works great on all other platforms (including > Android 6.0 on Nexus 5) crashes the application randomly during various UI > draw operations. Looking at the crash dump below, this seems to be related to > OpenGL/GPU. > When using the Crosswalk Webview, the application does not crash, this only > happens with the system webview. > This is a blocker for this particular device. Any hints on how to debug > further will be appreciated! > This crash always happens at the same location: > 1-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ ### ### ### ### ### ### > ### ### ### ### ### ### ### > 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ Chrome build fingerprint: > 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ a0.1.7 > 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ 1070 > 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ > 61966e6e-3fdc-4984-9d79-401e23ee5095 > 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ ### ### ### ### ### ### > ### ### ### ### ### ### ### > 11-17 17:00:18.590 25264-25321/? A/libc﹕ Fatal signal 11 (SIGSEGV), code 1, > fault addr 0x440 in tid 25321 (GpuThread) > 11-17 17:00:18.6933829-3829/? A/DEBUG﹕ *** *** *** *** *** *** *** *** > *** *** *** *** *** *** *** *** > 11-17 17:00:18.6933829-3829/? A/DEBUG﹕ Build fingerprint: > 'google/angler/angler:6.0/MDB08L/2343525:user/release-keys' > 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ Revision: '0' > 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ ABI: 'arm64' > 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ pid: 25264, tid: 25321, name: > GpuThread >>> io.wizkers.safecast.drive <<< > 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ signal 11 (SIGSEGV), code 1 > (SEGV_MAPERR), fault addr 0x440 > 11-17 17:00:18.7233829-3829/? A/DEBUG﹕ x0 06d8 x1 > x2 x3 0001 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x4 0010 x5 > x6 0010 x7 0007 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x8 x9 > 0010 x10 x11 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x12 x13 > 0028 x14 0078 x15 007f71520780 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x16 007f71520030 x17 > 0003 x18 0001 x19 0780 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x20 007f716ba000 x21 > 0003 x22 007f71564000 x23 007f71567000 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x24 007f71567cb8 x25 > 0001 x26 x27 007f9a7bc140 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x28 007f7167edfc x29 > 007f7167eb50 x30 007fa0666024 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ sp 007f7167eb50 pc > 007fa07195c4 pstate 6000 > 11-17 17:00:18.7383829-3829/? A/DEBUG﹕ backtrace: > 11-17 17:00:18.7393829-3829/? A/DEBUG﹕ #00 pc 0024d5c4 > /vendor/lib64/egl/libGLESv2_adreno.so > (EsxGfxMem::UpdateTimestampBucketId(EsxContext const*, unsigned int, > EsxAccessType)+64) > 11-17 17:00:18.7393829-3829/? A/DEBUG﹕ #01 pc 0019a020 > /vendor/lib64/egl/libGLESv2_adreno.so (EsxContext::BucketRenderingCmds()+596) > 11-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9971) Cordova outputs "Picked up _JAVA_OPTIONS" in stderr
[ https://issues.apache.org/jira/browse/CB-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018705#comment-15018705 ] ASF GitHub Bot commented on CB-9971: Github user dblotsky commented on the pull request: https://github.com/apache/cordova-android/pull/240#issuecomment-158513479 I'm pretty sure we can modify this line: https://github.com/MarcDiethelm/superspawn/blob/master/lib/index.js#L166 to return both the stdout and stderr. To me it seems like writing a whole new function is going to result in maintenance bugs in the future. > Cordova outputs "Picked up _JAVA_OPTIONS" in stderr > --- > > Key: CB-9971 > URL: https://issues.apache.org/jira/browse/CB-9971 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 5.0.0 > Environment: Windows, Tools for Apache Cordova in Visual Studio > Cordova 5.4.0 >Reporter: Michael Braude >Assignee: Vladimir Kotikov >Priority: Critical > Labels: easyfix, windows, > Original Estimate: 2h > Remaining Estimate: 2h > > Starting with version 5.4.0, Cordova now outputs "Picked up _JAVA_OPTIONS: > -Xmx512M" to stderr. This breaks clients such as Visual Studio because we > interpret messages in stderr to be errors, and this is not an error. So the > result is that we show deploy failures to the dev when there are no errors. > See this for customer impact: > http://stackoverflow.com/questions/33603167/vs2015-build-with-cordova-cli5-4-0-shows-deployment-errors > We can work around this in Visual Studio by using special casing, but Cordova > needs to output this in stdout like it did in previous versions -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10054) Random webview crash on Nexus6P
[ https://issues.apache.org/jira/browse/CB-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-10054. - Resolution: Won't Fix This is a WebView crash, and not an issue we can fix. Try upgrading the WebView to avoid this issue. This is why we allowed for third-party WebViews in the first place, because we can't fix these sorts of crashes. > Random webview crash on Nexus6P > --- > > Key: CB-10054 > URL: https://issues.apache.org/jira/browse/CB-10054 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0, 4.0.0, 5.0.0 > Environment: Only happens on Android 6.0 on Nexus 6P only (Adreno > GPU). This happens on all Cordova lib versions I have tried, even 5.0.0. >Reporter: Edouard Lafargue >Priority: Critical > > On Nexus 6P, the same code that works great on all other platforms (including > Android 6.0 on Nexus 5) crashes the application randomly during various UI > draw operations. Looking at the crash dump below, this seems to be related to > OpenGL/GPU. > When using the Crosswalk Webview, the application does not crash, this only > happens with the system webview. > This is a blocker for this particular device. Any hints on how to debug > further will be appreciated! > This crash always happens at the same location: > 1-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ ### ### ### ### ### ### > ### ### ### ### ### ### ### > 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ Chrome build fingerprint: > 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ a0.1.7 > 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ 1070 > 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ > 61966e6e-3fdc-4984-9d79-401e23ee5095 > 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ ### ### ### ### ### ### > ### ### ### ### ### ### ### > 11-17 17:00:18.590 25264-25321/? A/libc﹕ Fatal signal 11 (SIGSEGV), code 1, > fault addr 0x440 in tid 25321 (GpuThread) > 11-17 17:00:18.6933829-3829/? A/DEBUG﹕ *** *** *** *** *** *** *** *** > *** *** *** *** *** *** *** *** > 11-17 17:00:18.6933829-3829/? A/DEBUG﹕ Build fingerprint: > 'google/angler/angler:6.0/MDB08L/2343525:user/release-keys' > 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ Revision: '0' > 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ ABI: 'arm64' > 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ pid: 25264, tid: 25321, name: > GpuThread >>> io.wizkers.safecast.drive <<< > 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ signal 11 (SIGSEGV), code 1 > (SEGV_MAPERR), fault addr 0x440 > 11-17 17:00:18.7233829-3829/? A/DEBUG﹕ x0 06d8 x1 > x2 x3 0001 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x4 0010 x5 > x6 0010 x7 0007 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x8 x9 > 0010 x10 x11 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x12 x13 > 0028 x14 0078 x15 007f71520780 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x16 007f71520030 x17 > 0003 x18 0001 x19 0780 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x20 007f716ba000 x21 > 0003 x22 007f71564000 x23 007f71567000 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x24 007f71567cb8 x25 > 0001 x26 x27 007f9a7bc140 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x28 007f7167edfc x29 > 007f7167eb50 x30 007fa0666024 > 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ sp 007f7167eb50 pc > 007fa07195c4 pstate 6000 > 11-17 17:00:18.7383829-3829/? A/DEBUG﹕ backtrace: > 11-17 17:00:18.7393829-3829/? A/DEBUG﹕ #00 pc 0024d5c4 > /vendor/lib64/egl/libGLESv2_adreno.so > (EsxGfxMem::UpdateTimestampBucketId(EsxContext const*, unsigned int, > EsxAccessType)+64) > 11-17 17:00:18.7393829-3829/? A/DEBUG﹕ #01 pc 0019a020 > /vendor/lib64/egl/libGLESv2_adreno.so (EsxContext::BucketRenderingCmds()+596) > 11-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10054) Random webview crash on Nexus6P
Edouard Lafargue created CB-10054: - Summary: Random webview crash on Nexus6P Key: CB-10054 URL: https://issues.apache.org/jira/browse/CB-10054 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.5.0, 4.0.0, 5.0.0 Environment: Only happens on Android 6.0 on Nexus 6P only (Adreno GPU). This happens on all Cordova lib versions I have tried, even 5.0.0. Reporter: Edouard Lafargue Priority: Critical On Nexus 6P, the same code that works great on all other platforms (including Android 6.0 on Nexus 5) crashes the application randomly during various UI draw operations. Looking at the crash dump below, this seems to be related to OpenGL/GPU. When using the Crosswalk Webview, the application does not crash, this only happens with the system webview. This is a blocker for this particular device. Any hints on how to debug further will be appreciated! This crash always happens at the same location: 1-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ ### ### ### ### ### ### ### ### ### ### ### ### ### 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ Chrome build fingerprint: 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ a0.1.7 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ 1070 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ 61966e6e-3fdc-4984-9d79-401e23ee5095 11-17 17:00:18.590 25264-25321/? W/google-breakpad﹕ ### ### ### ### ### ### ### ### ### ### ### ### ### 11-17 17:00:18.590 25264-25321/? A/libc﹕ Fatal signal 11 (SIGSEGV), code 1, fault addr 0x440 in tid 25321 (GpuThread) 11-17 17:00:18.6933829-3829/? A/DEBUG﹕ *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 11-17 17:00:18.6933829-3829/? A/DEBUG﹕ Build fingerprint: 'google/angler/angler:6.0/MDB08L/2343525:user/release-keys' 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ Revision: '0' 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ ABI: 'arm64' 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ pid: 25264, tid: 25321, name: GpuThread >>> io.wizkers.safecast.drive <<< 11-17 17:00:18.6943829-3829/? A/DEBUG﹕ signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x440 11-17 17:00:18.7233829-3829/? A/DEBUG﹕ x0 06d8 x1 x2 x3 0001 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x4 0010 x5 x6 0010 x7 0007 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x8 x9 0010 x10 x11 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x12 x13 0028 x14 0078 x15 007f71520780 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x16 007f71520030 x17 0003 x18 0001 x19 0780 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x20 007f716ba000 x21 0003 x22 007f71564000 x23 007f71567000 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x24 007f71567cb8 x25 0001 x26 x27 007f9a7bc140 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ x28 007f7167edfc x29 007f7167eb50 x30 007fa0666024 11-17 17:00:18.7243829-3829/? A/DEBUG﹕ sp 007f7167eb50 pc 007fa07195c4 pstate 6000 11-17 17:00:18.7383829-3829/? A/DEBUG﹕ backtrace: 11-17 17:00:18.7393829-3829/? A/DEBUG﹕ #00 pc 0024d5c4 /vendor/lib64/egl/libGLESv2_adreno.so (EsxGfxMem::UpdateTimestampBucketId(EsxContext const*, unsigned int, EsxAccessType)+64) 11-17 17:00:18.7393829-3829/? A/DEBUG﹕ #01 pc 0019a020 /vendor/lib64/egl/libGLESv2_adreno.so (EsxContext::BucketRenderingCmds()+596) 11-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10047) [StatusBar] Fix iOS8 Deprecation Warnings
[ https://issues.apache.org/jira/browse/CB-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018630#comment-15018630 ] jcesarmobile commented on CB-10047: --- closed pull 39 because github app added some things I didn't want, pull 40 should be ok > [StatusBar] Fix iOS8 Deprecation Warnings > - > > Key: CB-10047 > URL: https://issues.apache.org/jira/browse/CB-10047 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Statusbar >Reporter: jordan cardwell >Assignee: jcesarmobile >Priority: Minor > Labels: deprecated, deprecation > > Issue has been around for a while > [https://github.com/apache/cordova-plugin-statusbar/pull/26] > After use Cordova build ios > there are some warning about UIDeviceOrientation and UIInterfaceOrientation: > Implicit conversion from enumeration type "UIDeviceOrientation"(aka "enum > UIDeviceOrientation") to different enumeration type "UIInterfaceOrientation" > (aka "enum UIInterfaceOrientation") > Based on current ios api, UIViewControl.interfaceOrientation has been > deprecated. > Fixed those warning using function: [[UIDevice currentDevice] orientation] > instead of self.viewController.interfaceOrientation -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10047) [StatusBar] Fix iOS8 Deprecation Warnings
[ https://issues.apache.org/jira/browse/CB-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018623#comment-15018623 ] ASF GitHub Bot commented on CB-10047: - Github user jcesarmobile closed the pull request at: https://github.com/apache/cordova-plugin-statusbar/pull/39 > [StatusBar] Fix iOS8 Deprecation Warnings > - > > Key: CB-10047 > URL: https://issues.apache.org/jira/browse/CB-10047 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Statusbar >Reporter: jordan cardwell >Assignee: jcesarmobile >Priority: Minor > Labels: deprecated, deprecation > > Issue has been around for a while > [https://github.com/apache/cordova-plugin-statusbar/pull/26] > After use Cordova build ios > there are some warning about UIDeviceOrientation and UIInterfaceOrientation: > Implicit conversion from enumeration type "UIDeviceOrientation"(aka "enum > UIDeviceOrientation") to different enumeration type "UIInterfaceOrientation" > (aka "enum UIInterfaceOrientation") > Based on current ios api, UIViewControl.interfaceOrientation has been > deprecated. > Fixed those warning using function: [[UIDevice currentDevice] orientation] > instead of self.viewController.interfaceOrientation -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10047) [StatusBar] Fix iOS8 Deprecation Warnings
[ https://issues.apache.org/jira/browse/CB-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018621#comment-15018621 ] ASF GitHub Bot commented on CB-10047: - GitHub user jcesarmobile opened a pull request: https://github.com/apache/cordova-plugin-statusbar/pull/40 CB-10047 fix iOS 8 deprecated warnings Removed all references to self.viewController.interfaceOrientation, they weren’t really used on invertFrameIfNeeded and are deprecated on iOS 8 Removed orientation param on invertFrameIfNeeded as it wasn’t being used. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jcesarmobile/cordova-plugin-statusbar CB-10047-statusbar Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-statusbar/pull/40.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #40 commit da75b5e2c29c2e1f04e124f5fa5ffd767d7eb8b9 Author: Julio César Date: 2015-11-20T19:33:00Z CB-10047 fix iOS 8 deprecated warnings Removed all references to self.viewController.interfaceOrientation, they weren’t really used on invertFrameIfNeeded and are deprecated on iOS 8 Removed orientation param on invertFrameIfNeeded as it wasn’t being used. > [StatusBar] Fix iOS8 Deprecation Warnings > - > > Key: CB-10047 > URL: https://issues.apache.org/jira/browse/CB-10047 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Statusbar >Reporter: jordan cardwell >Assignee: jcesarmobile >Priority: Minor > Labels: deprecated, deprecation > > Issue has been around for a while > [https://github.com/apache/cordova-plugin-statusbar/pull/26] > After use Cordova build ios > there are some warning about UIDeviceOrientation and UIInterfaceOrientation: > Implicit conversion from enumeration type "UIDeviceOrientation"(aka "enum > UIDeviceOrientation") to different enumeration type "UIInterfaceOrientation" > (aka "enum UIInterfaceOrientation") > Based on current ios api, UIViewControl.interfaceOrientation has been > deprecated. > Fixed those warning using function: [[UIDevice currentDevice] orientation] > instead of self.viewController.interfaceOrientation -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8917) Add api/way to get plugins results even when Cordova activity restarts
[ https://issues.apache.org/jira/browse/CB-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018594#comment-15018594 ] ASF GitHub Bot commented on CB-8917: Github user riknoll commented on the pull request: https://github.com/apache/cordova-docs/pull/428#issuecomment-158500525 Added docs for the new plugin API > Add api/way to get plugins results even when Cordova activity restarts > > > Key: CB-8917 > URL: https://issues.apache.org/jira/browse/CB-8917 > Project: Apache Cordova > Issue Type: Improvement > Components: Android >Reporter: Bnaya > > In android when you have a plugin that opens new activity the CordovaActivity > will be killed and you won't get the result from the plugin. > The new activity will get the results but because the plugin objects are dead > and the webview reloaded you can get the data to the js callback. > The most noticeable example is the camera plugin. (And maybe its the same > with even more platforms) > possible solution for this is to add metadata to the device ready event with > incoming data from plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8863) Fix potential problems with blocks usage in core plugins
[ https://issues.apache.org/jira/browse/CB-8863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018540#comment-15018540 ] ASF subversion and git services commented on CB-8863: - Commit d19ce1a3fe5302a92a66c9d7d4e4c68f5c759534 in cordova-plugin-media-capture's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;h=d19ce1a ] CB-8863 Fix block usage of self > Fix potential problems with blocks usage in core plugins > > > Key: CB-8863 > URL: https://issues.apache.org/jira/browse/CB-8863 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > Labels: cordova-ios-5.0.x > > Audit the core plugins to check for proper blocks usage. > Problems that I see can be summed up in this (fixed) code: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292-L313 > 1. You need a weak reference to "self" in blocks to prevent retain cycle > problems. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292 > 2. Anything that calls UIKit methods, which includes plugins that write > JavaScript back to the UIWebView (commandDelegate functions), must be called > in the main thread. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L308-L310 > (UPDATE: we actually already handle this in evalJS) > 3. Avoid creating private variables like this in the first place -- I would > create a class extension which will effectively have "private" properties > (nothing is truly private in objc). This is to avoid this situation in the > block where you have to cast the weak self into a strong self (and check it's > still around), just to access a private variable: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L298-L304 > Of course since we are modifying UIKit items here, rule 2 above also applies. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8863) Fix potential problems with blocks usage in core plugins
[ https://issues.apache.org/jira/browse/CB-8863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018541#comment-15018541 ] ASF GitHub Bot commented on CB-8863: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-media-capture/pull/49 > Fix potential problems with blocks usage in core plugins > > > Key: CB-8863 > URL: https://issues.apache.org/jira/browse/CB-8863 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > Labels: cordova-ios-5.0.x > > Audit the core plugins to check for proper blocks usage. > Problems that I see can be summed up in this (fixed) code: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292-L313 > 1. You need a weak reference to "self" in blocks to prevent retain cycle > problems. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292 > 2. Anything that calls UIKit methods, which includes plugins that write > JavaScript back to the UIWebView (commandDelegate functions), must be called > in the main thread. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L308-L310 > (UPDATE: we actually already handle this in evalJS) > 3. Avoid creating private variables like this in the first place -- I would > create a class extension which will effectively have "private" properties > (nothing is truly private in objc). This is to avoid this situation in the > block where you have to cast the weak self into a strong self (and check it's > still around), just to access a private variable: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L298-L304 > Of course since we are modifying UIKit items here, rule 2 above also applies. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8863) Fix potential problems with blocks usage in core plugins
[ https://issues.apache.org/jira/browse/CB-8863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018524#comment-15018524 ] ASF GitHub Bot commented on CB-8863: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-media/pull/76 > Fix potential problems with blocks usage in core plugins > > > Key: CB-8863 > URL: https://issues.apache.org/jira/browse/CB-8863 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > Labels: cordova-ios-5.0.x > > Audit the core plugins to check for proper blocks usage. > Problems that I see can be summed up in this (fixed) code: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292-L313 > 1. You need a weak reference to "self" in blocks to prevent retain cycle > problems. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292 > 2. Anything that calls UIKit methods, which includes plugins that write > JavaScript back to the UIWebView (commandDelegate functions), must be called > in the main thread. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L308-L310 > (UPDATE: we actually already handle this in evalJS) > 3. Avoid creating private variables like this in the first place -- I would > create a class extension which will effectively have "private" properties > (nothing is truly private in objc). This is to avoid this situation in the > block where you have to cast the weak self into a strong self (and check it's > still around), just to access a private variable: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L298-L304 > Of course since we are modifying UIKit items here, rule 2 above also applies. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10047) [StatusBar] Fix iOS8 Deprecation Warnings
[ https://issues.apache.org/jira/browse/CB-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018522#comment-15018522 ] ASF GitHub Bot commented on CB-10047: - GitHub user jcesarmobile opened a pull request: https://github.com/apache/cordova-plugin-statusbar/pull/39 CB-10047 fix iOS 8 deprecated warnings Removed all references to self.viewController.interfaceOrientation, they weren’t really used on invertFrameIfNeeded and are deprecated on iOS 8 Removed orientation param on invertFrameIfNeeded as it wasn’t being used. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jcesarmobile/cordova-plugin-statusbar CB-10047 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-statusbar/pull/39.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #39 commit 97bd65a83429c5b6b7501ba8178fc370e92f22d8 Author: Julio César Date: 2015-11-20T16:42:01Z Merge remote-tracking branch 'apache/master' commit e291f3feec82a81cd0925757183a2369c6398861 Author: Julio César Date: 2015-11-20T18:49:53Z CB-10047 fix iOS 8 deprecated warnings Removed all references to self.viewController.interfaceOrientation, they weren’t really used on invertFrameIfNeeded and are deprecated on iOS 8 Removed orientation param on invertFrameIfNeeded as it wasn’t being used. > [StatusBar] Fix iOS8 Deprecation Warnings > - > > Key: CB-10047 > URL: https://issues.apache.org/jira/browse/CB-10047 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Statusbar >Reporter: jordan cardwell >Assignee: jcesarmobile >Priority: Minor > Labels: deprecated, deprecation > > Issue has been around for a while > [https://github.com/apache/cordova-plugin-statusbar/pull/26] > After use Cordova build ios > there are some warning about UIDeviceOrientation and UIInterfaceOrientation: > Implicit conversion from enumeration type "UIDeviceOrientation"(aka "enum > UIDeviceOrientation") to different enumeration type "UIInterfaceOrientation" > (aka "enum UIInterfaceOrientation") > Based on current ios api, UIViewControl.interfaceOrientation has been > deprecated. > Fixed those warning using function: [[UIDevice currentDevice] orientation] > instead of self.viewController.interfaceOrientation -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10040) Compile Error in InAppBrowser Plugin for iOS - No known instance method for selector 'URLIsWhitelisted:'
[ https://issues.apache.org/jira/browse/CB-10040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-10040. --- Resolution: Fixed > Compile Error in InAppBrowser Plugin for iOS - No known instance method for > selector 'URLIsWhitelisted:' > > > Key: CB-10040 > URL: https://issues.apache.org/jira/browse/CB-10040 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 4.0.0 > Environment: OS X 10.11.1, Xcode 7.1.1, iOS 9.1 >Reporter: Inderpreet >Assignee: Shazron Abdullah > Labels: Triaged, cordova-ios-4.0.x, cordova-plugin-inappbrowser, > ios > Attachments: CB-10040V1.patch, CB-10040V2.patch > > > While working with cordova-ios branch > (https://github.com/apache/cordova-ios.git#master) we are facing a compile > error in InAppBrowser > Plugin(https://github.com/apache/cordova-plugin-inappbrowser.git#master), it > can be due to the recent update to cordova-ios i.e. iOS whitelist removal > CB-9972 > Error details : CDVInAppBrowser.m:231:31: No known instance method for > selector 'URLIsWhitelisted:' -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10040) Compile Error in InAppBrowser Plugin for iOS - No known instance method for selector 'URLIsWhitelisted:'
[ https://issues.apache.org/jira/browse/CB-10040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018514#comment-15018514 ] ASF subversion and git services commented on CB-10040: -- Commit 542536f7908a776ec49becb0bf40969ee4a48a82 in cordova-plugin-inappbrowser's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-inappbrowser.git;h=542536f ] CB-10040 - re-fix: backwards compatible with cordova-ios < 4.0 > Compile Error in InAppBrowser Plugin for iOS - No known instance method for > selector 'URLIsWhitelisted:' > > > Key: CB-10040 > URL: https://issues.apache.org/jira/browse/CB-10040 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 4.0.0 > Environment: OS X 10.11.1, Xcode 7.1.1, iOS 9.1 >Reporter: Inderpreet >Assignee: Shazron Abdullah > Labels: Triaged, cordova-ios-4.0.x, cordova-plugin-inappbrowser, > ios > Attachments: CB-10040V1.patch, CB-10040V2.patch > > > While working with cordova-ios branch > (https://github.com/apache/cordova-ios.git#master) we are facing a compile > error in InAppBrowser > Plugin(https://github.com/apache/cordova-plugin-inappbrowser.git#master), it > can be due to the recent update to cordova-ios i.e. iOS whitelist removal > CB-9972 > Error details : CDVInAppBrowser.m:231:31: No known instance method for > selector 'URLIsWhitelisted:' -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8863) Fix potential problems with blocks usage in core plugins
[ https://issues.apache.org/jira/browse/CB-8863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018501#comment-15018501 ] ASF subversion and git services commented on CB-8863: - Commit 9e93bad83c9e980cb593dc057fe8af40f35652f1 in cordova-plugin-file-transfer's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file-transfer.git;h=9e93bad ] CB-8863 fix block usage of self > Fix potential problems with blocks usage in core plugins > > > Key: CB-8863 > URL: https://issues.apache.org/jira/browse/CB-8863 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > Labels: cordova-ios-5.0.x > > Audit the core plugins to check for proper blocks usage. > Problems that I see can be summed up in this (fixed) code: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292-L313 > 1. You need a weak reference to "self" in blocks to prevent retain cycle > problems. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L292 > 2. Anything that calls UIKit methods, which includes plugins that write > JavaScript back to the UIWebView (commandDelegate functions), must be called > in the main thread. > Fix: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L308-L310 > (UPDATE: we actually already handle this in evalJS) > 3. Avoid creating private variables like this in the first place -- I would > create a class extension which will effectively have "private" properties > (nothing is truly private in objc). This is to avoid this situation in the > block where you have to cast the weak self into a strong self (and check it's > still around), just to access a private variable: > https://github.com/apache/cordova-plugin-splashscreen/blob/fa60f01adcba2d21583de7972a0facc4da1eb75e/src/ios/CDVSplashScreen.m#L298-L304 > Of course since we are modifying UIKit items here, rule 2 above also applies. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Reopened] (CB-10040) Compile Error in InAppBrowser Plugin for iOS - No known instance method for selector 'URLIsWhitelisted:'
[ https://issues.apache.org/jira/browse/CB-10040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah reopened CB-10040: --- Re-opening because it is not backwards compatible based on the docs. For cordova-ios < 4, it will still need to open it in the inappbrowser if it doesn't pass the internal whitelist. > Compile Error in InAppBrowser Plugin for iOS - No known instance method for > selector 'URLIsWhitelisted:' > > > Key: CB-10040 > URL: https://issues.apache.org/jira/browse/CB-10040 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 4.0.0 > Environment: OS X 10.11.1, Xcode 7.1.1, iOS 9.1 >Reporter: Inderpreet >Assignee: Shazron Abdullah > Labels: Triaged, cordova-ios-4.0.x, cordova-plugin-inappbrowser, > ios > Attachments: CB-10040V1.patch, CB-10040V2.patch > > > While working with cordova-ios branch > (https://github.com/apache/cordova-ios.git#master) we are facing a compile > error in InAppBrowser > Plugin(https://github.com/apache/cordova-plugin-inappbrowser.git#master), it > can be due to the recent update to cordova-ios i.e. iOS whitelist removal > CB-9972 > Error details : CDVInAppBrowser.m:231:31: No known instance method for > selector 'URLIsWhitelisted:' -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10040) Compile Error in InAppBrowser Plugin for iOS - No known instance method for selector 'URLIsWhitelisted:'
[ https://issues.apache.org/jira/browse/CB-10040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018468#comment-15018468 ] Shazron Abdullah commented on CB-10040: --- Hmm I didn't think of the cordova-ios < 4.0 case - having cordova-ios-4 tunnel vision :/ For cordova-ios-4.x, there is no need to check for the whitelist here because the main webview will have a filter that checks whether it is has an tag exception, which CDVInAppBrowser::openInCordovaWebView won't know the result from, so we can't switch on it. I'll have to re-open this and use the #ifdef macro to switch between the old and new code paths for backwards compat. purposes. > Compile Error in InAppBrowser Plugin for iOS - No known instance method for > selector 'URLIsWhitelisted:' > > > Key: CB-10040 > URL: https://issues.apache.org/jira/browse/CB-10040 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 4.0.0 > Environment: OS X 10.11.1, Xcode 7.1.1, iOS 9.1 >Reporter: Inderpreet >Assignee: Shazron Abdullah > Labels: Triaged, cordova-ios-4.0.x, cordova-plugin-inappbrowser, > ios > Attachments: CB-10040V1.patch, CB-10040V2.patch > > > While working with cordova-ios branch > (https://github.com/apache/cordova-ios.git#master) we are facing a compile > error in InAppBrowser > Plugin(https://github.com/apache/cordova-plugin-inappbrowser.git#master), it > can be due to the recent update to cordova-ios i.e. iOS whitelist removal > CB-9972 > Error details : CDVInAppBrowser.m:231:31: No known instance method for > selector 'URLIsWhitelisted:' -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9472) Camera Plugin crashes on iOS if CameraUsesGeolocation is set to true.
[ https://issues.apache.org/jira/browse/CB-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018444#comment-15018444 ] andy stevko commented on CB-9472: - cordova cli 5.1.1 cordova-ios 3.8.0 iOS v9.0.2 camera-plugin - latest The only way I was able to track the problem to this ticket is the fleeting iOS interstitial dialog asking user for permission to use gps position with the camera photo. The device had Location Services disabled and Location setting to Never for every app. The permission dialog was only visible for a second before disappearing. Other devices that have Location available just crash without any tracking. > Camera Plugin crashes on iOS if CameraUsesGeolocation is set to true. > - > > Key: CB-9472 > URL: https://issues.apache.org/jira/browse/CB-9472 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera >Reporter: Cesidio DiBenedetto >Priority: Critical > Labels: Triaged, ios > > cordova - 5.1.1 > camera-plugin - 1.2.0 > cordova-ios - 3.8.0 > if you add: > > to the config.xml, the app crashes after taking a picture. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8917) Add api/way to get plugins results even when Cordova activity restarts
[ https://issues.apache.org/jira/browse/CB-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018411#comment-15018411 ] ASF GitHub Bot commented on CB-8917: Github user riknoll commented on the pull request: https://github.com/apache/cordova-android/pull/239#issuecomment-158471787 I will submit a PR that updates the camera plugin to use the save-restore API as well, which should fix CB-9189. I'll also take a look at the contacts plugin, because I believe it uses external activities. > Add api/way to get plugins results even when Cordova activity restarts > > > Key: CB-8917 > URL: https://issues.apache.org/jira/browse/CB-8917 > Project: Apache Cordova > Issue Type: Improvement > Components: Android >Reporter: Bnaya > > In android when you have a plugin that opens new activity the CordovaActivity > will be killed and you won't get the result from the plugin. > The new activity will get the results but because the plugin objects are dead > and the webview reloaded you can get the data to the js callback. > The most noticeable example is the camera plugin. (And maybe its the same > with even more platforms) > possible solution for this is to add metadata to the device ready event with > incoming data from plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8917) Add api/way to get plugins results even when Cordova activity restarts
[ https://issues.apache.org/jira/browse/CB-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018393#comment-15018393 ] ASF GitHub Bot commented on CB-8917: Github user riknoll commented on the pull request: https://github.com/apache/cordova-android/pull/239#issuecomment-158469875 Alright, I plan on merging this in soon. I want to do some more testing and write some plugin-side docs before I do, but since this PR's been open a while and I don't think this will really be much of a breaking change, I am going to push forward. I plan to merge it in early next week. Let me know if there are any objections and I will try to address them! > Add api/way to get plugins results even when Cordova activity restarts > > > Key: CB-8917 > URL: https://issues.apache.org/jira/browse/CB-8917 > Project: Apache Cordova > Issue Type: Improvement > Components: Android >Reporter: Bnaya > > In android when you have a plugin that opens new activity the CordovaActivity > will be killed and you won't get the result from the plugin. > The new activity will get the results but because the plugin objects are dead > and the webview reloaded you can get the data to the js callback. > The most noticeable example is the camera plugin. (And maybe its the same > with even more platforms) > possible solution for this is to add metadata to the device ready event with > incoming data from plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10030) Cordova-Ubuntu Platform Release
[ https://issues.apache.org/jira/browse/CB-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018383#comment-15018383 ] David Barth commented on CB-10030: -- Let me know if you want me to send the call for vote and tick the rest of the release process checks. ie whatever a non-committer can help you with. > Cordova-Ubuntu Platform Release > --- > > Key: CB-10030 > URL: https://issues.apache.org/jira/browse/CB-10030 > Project: Apache Cordova > Issue Type: Task > Components: Ubuntu >Reporter: David Barth >Assignee: Maxim Ermilov > > Following steps at > https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-10029) Rename edge docs to dev
[ https://issues.apache.org/jira/browse/CB-10029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard B Knoll closed CB-10029. Resolution: Fixed > Rename edge docs to dev > --- > > Key: CB-10029 > URL: https://issues.apache.org/jira/browse/CB-10029 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Richard B Knoll >Assignee: Richard B Knoll > > Renaming edge to dev to prevent confusion among website visitors. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8534) Add support for auth dialogs in inappbrowser plugin
[ https://issues.apache.org/jira/browse/CB-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018332#comment-15018332 ] ASF GitHub Bot commented on CB-8534: Github user sgrebnov commented on the pull request: https://github.com/apache/cordova-plugin-inappbrowser/pull/82#issuecomment-158460236 Verified and merged > Add support for auth dialogs in inappbrowser plugin > --- > > Key: CB-8534 > URL: https://issues.apache.org/jira/browse/CB-8534 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin InAppBrowser >Reporter: Connor Pearson > Labels: Android > > The AndroidWebView delegates onReceivedHttpAuthRequest to any plugin that > responds to it. (CB-8201) This would add the same behavior to the > inappbrowser for android. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8534) Add support for auth dialogs in inappbrowser plugin
[ https://issues.apache.org/jira/browse/CB-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018330#comment-15018330 ] ASF GitHub Bot commented on CB-8534: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-inappbrowser/pull/82 > Add support for auth dialogs in inappbrowser plugin > --- > > Key: CB-8534 > URL: https://issues.apache.org/jira/browse/CB-8534 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin InAppBrowser >Reporter: Connor Pearson > Labels: Android > > The AndroidWebView delegates onReceivedHttpAuthRequest to any plugin that > responds to it. (CB-8201) This would add the same behavior to the > inappbrowser for android. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8534) Add support for auth dialogs in inappbrowser plugin
[ https://issues.apache.org/jira/browse/CB-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018328#comment-15018328 ] ASF subversion and git services commented on CB-8534: - Commit 9b576f303b87f30b5054c47240c1e815415da374 in cordova-plugin-inappbrowser's branch refs/heads/master from [~cjpearson] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-inappbrowser.git;h=9b576f3 ] CB-8534: Allow plugins to respond to onReceivedHttpAuthRequest. This closes #82 > Add support for auth dialogs in inappbrowser plugin > --- > > Key: CB-8534 > URL: https://issues.apache.org/jira/browse/CB-8534 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin InAppBrowser >Reporter: Connor Pearson > Labels: Android > > The AndroidWebView delegates onReceivedHttpAuthRequest to any plugin that > responds to it. (CB-8201) This would add the same behavior to the > inappbrowser for android. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9971) Cordova outputs "Picked up _JAVA_OPTIONS" in stderr
[ https://issues.apache.org/jira/browse/CB-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018268#comment-15018268 ] ASF GitHub Bot commented on CB-9971: Github user vladimir-kotikov commented on the pull request: https://github.com/apache/cordova-android/pull/240#issuecomment-158453018 .It does, right, but there is two problems: 1. Superspawn returns output only _after_ the underlying process exits - if the build lasts long enough, this might be confusing for the user, 2. Superspawn either resolves with stdout or rejects with some error message that contains stderr output - there is no way to get both stdout and stderr after the promise completed > Cordova outputs "Picked up _JAVA_OPTIONS" in stderr > --- > > Key: CB-9971 > URL: https://issues.apache.org/jira/browse/CB-9971 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 5.0.0 > Environment: Windows, Tools for Apache Cordova in Visual Studio > Cordova 5.4.0 >Reporter: Michael Braude >Assignee: Vladimir Kotikov >Priority: Critical > Labels: easyfix, windows, > Original Estimate: 2h > Remaining Estimate: 2h > > Starting with version 5.4.0, Cordova now outputs "Picked up _JAVA_OPTIONS: > -Xmx512M" to stderr. This breaks clients such as Visual Studio because we > interpret messages in stderr to be errors, and this is not an error. So the > result is that we show deploy failures to the dev when there are no errors. > See this for customer impact: > http://stackoverflow.com/questions/33603167/vs2015-build-with-cordova-cli5-4-0-shows-deployment-errors > We can work around this in Visual Studio by using special casing, but Cordova > needs to output this in stdout like it did in previous versions -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9445) executeScript callbacks not working for iOS
[
https://issues.apache.org/jira/browse/CB-9445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018227#comment-15018227
]
ASF GitHub Bot commented on CB-9445:
GitHub user sgrebnov opened a pull request:
https://github.com/apache/cordova-plugin-inappbrowser/pull/125
CB-9445 Improves executeScript callbacks on iOS
https://issues.apache.org/jira/browse/CB-9445
The following code could be used for tests
```
var ref = window.open('http://apache.org', '_blank', 'location=yes');
ref.addEventListener('loadstart', function() {
ref.executeScript({code: "window.some_var = 'some
value';"},function(){
ref.executeScript({code: "window.some_var2 = 'some
value2';"},function(){
alert('loadstart2 callback');
});
alert('loadstart1 callback');
});
});
ref.addEventListener('loadstop', function() {
ref.executeScript({code: "alert('loadstop code:' +
window.some_var + ' '+ window.some_var2);"},function(){alert('loadstop
callback');});
});
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MSOpenTech/cordova-plugin-inappbrowser CB-9445
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-inappbrowser/pull/125.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #125
commit 8456a7692663e4e87d0775b5aa428b86f971f3d0
Author: sgrebnov
Date: 2015-11-20T16:15:55Z
CB-9445 Improves executeScript callbacks on iOS
> executeScript callbacks not working for iOS
> ---
>
> Key: CB-9445
> URL: https://issues.apache.org/jira/browse/CB-9445
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin InAppBrowser
>Affects Versions: 5.1.1
> Environment: Cordova 5.1.1 (CLI), ios 3.8.0, android 4.0.2,
> cordova-plugin-inappbrowser 1.0.1 (NPM)
>Reporter: Scott Seitz
>Assignee: jcesarmobile
> Labels: Triaged, iOS
>
> Can someone please check to see if they are encountering the same problem I
> am in the environment I've listed? (latest released builds of everything I
> think)
> I open an inappbrowser window and then run an executeScript command using
> "code:" (not "file:"). Everything works fine on Android, but on iOS, it
> simply will NOT fire the callback function after executing the injected code.
> Make the "code:" as simple as you like to test it and see if you can get a
> callback to fire. I've dumbed it down as much as possible and can't get one
> to fire. I know that all instances of code I've injected have run fine in
> the iab by using the console (against the iab) to check for the variables I
> was creating in the code. I can't even get a callback to fire that doesn't
> expect a parameter to be passed back...
> Many thanks,
> Scott
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-7696) External links are mistakenly opening via system browser instead of InAppBrowser
[ https://issues.apache.org/jira/browse/CB-7696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Grebnov resolved CB-7696. Resolution: Fixed > External links are mistakenly opening via system browser instead of > InAppBrowser > > > Key: CB-7696 > URL: https://issues.apache.org/jira/browse/CB-7696 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser > Environment: 'windows' platform, Windows 8.0, 8.1, Windows Phone 8.1 >Reporter: Sergey Shakhnazarov >Assignee: Sergey Grebnov > Labels: Triaged, Windows > > 1. Run Mobilespec app > 2. Go to Plugin Tests (Automatic and manual) > 3. Go to “manual tests” > 4. Go to “cordova.inappbrowser.tests.tests” > 5. Click on of these buttons > White Listed URL > "target=Random" button > Expected result: open successfully in InAppBrowser to www.google.com > Actual: opens link in a system browser > "* target=Random, no location bar" button > Expected result: open successfully in InAppBrowser to www.google.com with no > location bar. > Actual: opens link in a system browser > Non White Listed URL > target=Default > Expected result: open successfully in InAppBrowser to apple.com (_self > enforces whitelist). > Actual: opens link in a system browser > target=_self > Expected result: open successfully in InAppBrowser to apple.com (_self > enforces whitelist). > Actual: opens link in a system browser > target=Random > Expected result: open successfully in InAppBrowser to apple.com. > Actual: opens link in a system browser > * target=Random, no location bar > Expected result: open successfully in InAppBrowser to apple.com without > locationBar. > Actual: opens link in a system browser -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-3750) InAppBrowser: Can We Haz Loading Spinner?
[ https://issues.apache.org/jira/browse/CB-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018169#comment-15018169 ] ASF GitHub Bot commented on CB-3750: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-inappbrowser/pull/89 > InAppBrowser: Can We Haz Loading Spinner? > - > > Key: CB-3750 > URL: https://issues.apache.org/jira/browse/CB-3750 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 2.5.0, 2.6.0, 2.7.0, 2.8.0 > Environment: Android (at least) >Reporter: Lindsey Simon >Priority: Trivial > Labels: Triaged > > I'm using the InAppBrowser to open a Google/Facebook OAuth login screen. In > order for that to work it first opens an URL on my server and then redirects > to the proper provider endpoint. > When the internet is slow this results in a pretty lousy user experience as > the InAppBrowser doesn't seem to have any loading indicator - which made me > think it wasn't working, and then I clicked Done prematurely. I suspect my > users will do the same and not try a second time and my app is DOA. > Am I missing anything here by chance? > Any advice on how to get a loading indicator in the least-intrusive way? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-3750) InAppBrowser: Can We Haz Loading Spinner?
[ https://issues.apache.org/jira/browse/CB-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018170#comment-15018170 ] ASF GitHub Bot commented on CB-3750: Github user sgrebnov commented on the pull request: https://github.com/apache/cordova-plugin-inappbrowser/pull/89#issuecomment-158436013 Tested and merged > InAppBrowser: Can We Haz Loading Spinner? > - > > Key: CB-3750 > URL: https://issues.apache.org/jira/browse/CB-3750 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 2.5.0, 2.6.0, 2.7.0, 2.8.0 > Environment: Android (at least) >Reporter: Lindsey Simon >Priority: Trivial > Labels: Triaged > > I'm using the InAppBrowser to open a Google/Facebook OAuth login screen. In > order for that to work it first opens an URL on my server and then redirects > to the proper provider endpoint. > When the internet is slow this results in a pretty lousy user experience as > the InAppBrowser doesn't seem to have any loading indicator - which made me > think it wasn't working, and then I clicked Done prematurely. I suspect my > users will do the same and not try a second time and my app is DOA. > Am I missing anything here by chance? > Any advice on how to get a loading indicator in the least-intrusive way? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-3750) InAppBrowser: Can We Haz Loading Spinner?
[ https://issues.apache.org/jira/browse/CB-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018168#comment-15018168 ] ASF subversion and git services commented on CB-3750: - Commit 52cfd3216a05edff9f5f00f66050cf9312b6a548 in cordova-plugin-inappbrowser's branch refs/heads/master from [~cjpearson] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-inappbrowser.git;h=52cfd32 ] CB-3750: Fixes spinner on iOS. This closes #89 > InAppBrowser: Can We Haz Loading Spinner? > - > > Key: CB-3750 > URL: https://issues.apache.org/jira/browse/CB-3750 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 2.5.0, 2.6.0, 2.7.0, 2.8.0 > Environment: Android (at least) >Reporter: Lindsey Simon >Priority: Trivial > Labels: Triaged > > I'm using the InAppBrowser to open a Google/Facebook OAuth login screen. In > order for that to work it first opens an URL on my server and then redirects > to the proper provider endpoint. > When the internet is slow this results in a pretty lousy user experience as > the InAppBrowser doesn't seem to have any loading indicator - which made me > think it wasn't working, and then I clicked Done prematurely. I suspect my > users will do the same and not try a second time and my app is DOA. > Am I missing anything here by chance? > Any advice on how to get a loading indicator in the least-intrusive way? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9827) Implement and expose PlatformApi for iOS
[ https://issues.apache.org/jira/browse/CB-9827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018126#comment-15018126 ] ASF GitHub Bot commented on CB-9827: Github user sgrebnov commented on the pull request: https://github.com/apache/cordova-ios/pull/176#issuecomment-158425264 TODO: @sgrebnov to rebase on top of master, fetch latest changes from cordova-lib (preferences handling change, may be more), address Mefire notes > Implement and expose PlatformApi for iOS > > > Key: CB-9827 > URL: https://issues.apache.org/jira/browse/CB-9827 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Vladimir Kotikov >Assignee: Sergey Grebnov > Labels: PlatformApi > Fix For: 5.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10010) Cordova plugin contacts - PhoneNumbers error
[ https://issues.apache.org/jira/browse/CB-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-10010: -- Priority: Minor (was: Major) > Cordova plugin contacts - PhoneNumbers error > > > Key: CB-10010 > URL: https://issues.apache.org/jira/browse/CB-10010 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Affects Versions: 1.1.0 >Reporter: Rony Cohen >Assignee: Vladimir Kotikov >Priority: Minor > Labels: Android, contacts, cordova-plugin-contacts, triaged > > with cordova-plugin-contacts 1.1.0 "Contacts" > When I get the whole list of contacts It's working but when I choose : > navigator.contacts.fieldType.phoneNumbers in the options.desiredFields > I get properly some first contacts, then (maybe because one of my contact > phoneNumber value) , I get this error : > Error in Success callbackId: Contacts598408154 : > SyntaxError: Unexpected token ucordova.js:312 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-10010) Cordova plugin contacts - PhoneNumbers error
[ https://issues.apache.org/jira/browse/CB-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-10010: - Assignee: Vladimir Kotikov > Cordova plugin contacts - PhoneNumbers error > > > Key: CB-10010 > URL: https://issues.apache.org/jira/browse/CB-10010 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Affects Versions: 1.1.0 >Reporter: Rony Cohen >Assignee: Vladimir Kotikov > Labels: Android, contacts, cordova-plugin-contacts, triaged > > with cordova-plugin-contacts 1.1.0 "Contacts" > When I get the whole list of contacts It's working but when I choose : > navigator.contacts.fieldType.phoneNumbers in the options.desiredFields > I get properly some first contacts, then (maybe because one of my contact > phoneNumber value) , I get this error : > Error in Success callbackId: Contacts598408154 : > SyntaxError: Unexpected token ucordova.js:312 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10010) Cordova plugin contacts - PhoneNumbers error
[
https://issues.apache.org/jira/browse/CB-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018090#comment-15018090
]
Vladimir Kotikov commented on CB-10010:
---
[~ronyrun], this looks like an error in either success or error callback for
{{contacts.find()}}. Could you please post a code to repro this issue?
> Cordova plugin contacts - PhoneNumbers error
>
>
> Key: CB-10010
> URL: https://issues.apache.org/jira/browse/CB-10010
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
>Affects Versions: 1.1.0
>Reporter: Rony Cohen
> Labels: Android, contacts, cordova-plugin-contacts, triaged
>
> with cordova-plugin-contacts 1.1.0 "Contacts"
> When I get the whole list of contacts It's working but when I choose :
> navigator.contacts.fieldType.phoneNumbers in the options.desiredFields
> I get properly some first contacts, then (maybe because one of my contact
> phoneNumber value) , I get this error :
> Error in Success callbackId: Contacts598408154 :
> SyntaxError: Unexpected token ucordova.js:312
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-4611) ContactField pref property returns true in Android
[
https://issues.apache.org/jira/browse/CB-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-4611.
Resolution: Not A Problem
> ContactField pref property returns true in Android
> --
>
> Key: CB-4611
> URL: https://issues.apache.org/jira/browse/CB-4611
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs, Plugin Contacts
>Affects Versions: 2.9.0
> Environment: Android 4.2 emulator
>Reporter: Shingo Toda
>Assignee: Michael Brooks
>Priority: Trivial
> Labels: documentation, triaged
>
> I am looking into mobile-spec. [This
> document|http://cordova.apache.org/docs/en/2.9.0/cordova_contacts_contacts.md.html#ContactField]
> says
> {quote}
> *Android Quirks*
> pref: Not supported, returning false.
> {quote}
> But spec "contacts.spec.11 should be able to define a ContactField object" in
> contacts.tests.js(239) is passed, which pref is set to true. See the
> following.
> {code:title=www/autotest/tests/contacts.tests.js|borderStyle=solid}
> it("contacts.spec.11 should be able to define a ContactField object",
> function() {
> var contactField = new ContactField("home", "8005551212", true);
> expect(contactField).toBeDefined();
> expect(contactField.type).toBe("home");
> expect(contactField.value).toBe("8005551212");
> expect(contactField.pref).toBe(true);
> });
> {code}
> Is pref property not really supported?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-4611) ContactField pref property returns true in Android
[
https://issues.apache.org/jira/browse/CB-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-4611:
-
Labels: documentation triaged (was: documentation)
> ContactField pref property returns true in Android
> --
>
> Key: CB-4611
> URL: https://issues.apache.org/jira/browse/CB-4611
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs, Plugin Contacts
>Affects Versions: 2.9.0
> Environment: Android 4.2 emulator
>Reporter: Shingo Toda
>Assignee: Michael Brooks
>Priority: Minor
> Labels: documentation, triaged
>
> I am looking into mobile-spec. [This
> document|http://cordova.apache.org/docs/en/2.9.0/cordova_contacts_contacts.md.html#ContactField]
> says
> {quote}
> *Android Quirks*
> pref: Not supported, returning false.
> {quote}
> But spec "contacts.spec.11 should be able to define a ContactField object" in
> contacts.tests.js(239) is passed, which pref is set to true. See the
> following.
> {code:title=www/autotest/tests/contacts.tests.js|borderStyle=solid}
> it("contacts.spec.11 should be able to define a ContactField object",
> function() {
> var contactField = new ContactField("home", "8005551212", true);
> expect(contactField).toBeDefined();
> expect(contactField.type).toBe("home");
> expect(contactField.value).toBe("8005551212");
> expect(contactField.pref).toBe(true);
> });
> {code}
> Is pref property not really supported?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-4611) ContactField pref property returns true in Android
[
https://issues.apache.org/jira/browse/CB-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-4611:
-
Priority: Trivial (was: Minor)
> ContactField pref property returns true in Android
> --
>
> Key: CB-4611
> URL: https://issues.apache.org/jira/browse/CB-4611
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs, Plugin Contacts
>Affects Versions: 2.9.0
> Environment: Android 4.2 emulator
>Reporter: Shingo Toda
>Assignee: Michael Brooks
>Priority: Trivial
> Labels: documentation, triaged
>
> I am looking into mobile-spec. [This
> document|http://cordova.apache.org/docs/en/2.9.0/cordova_contacts_contacts.md.html#ContactField]
> says
> {quote}
> *Android Quirks*
> pref: Not supported, returning false.
> {quote}
> But spec "contacts.spec.11 should be able to define a ContactField object" in
> contacts.tests.js(239) is passed, which pref is set to true. See the
> following.
> {code:title=www/autotest/tests/contacts.tests.js|borderStyle=solid}
> it("contacts.spec.11 should be able to define a ContactField object",
> function() {
> var contactField = new ContactField("home", "8005551212", true);
> expect(contactField).toBeDefined();
> expect(contactField.type).toBe("home");
> expect(contactField.value).toBe("8005551212");
> expect(contactField.pref).toBe(true);
> });
> {code}
> Is pref property not really supported?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-4611) ContactField pref property returns true in Android
[
https://issues.apache.org/jira/browse/CB-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018082#comment-15018082
]
Vladimir Kotikov commented on CB-4611:
--
This test just tests if ContactField constructor acts properly and sets
{{pref}} field according to constructor's param.
{{pref}} is not supported by native Android implementation, and thus, {{pref}}
property is ingored, when saving contact and always false, when querying
contact from device.
> ContactField pref property returns true in Android
> --
>
> Key: CB-4611
> URL: https://issues.apache.org/jira/browse/CB-4611
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs, Plugin Contacts
>Affects Versions: 2.9.0
> Environment: Android 4.2 emulator
>Reporter: Shingo Toda
>Assignee: Michael Brooks
>Priority: Minor
> Labels: documentation
>
> I am looking into mobile-spec. [This
> document|http://cordova.apache.org/docs/en/2.9.0/cordova_contacts_contacts.md.html#ContactField]
> says
> {quote}
> *Android Quirks*
> pref: Not supported, returning false.
> {quote}
> But spec "contacts.spec.11 should be able to define a ContactField object" in
> contacts.tests.js(239) is passed, which pref is set to true. See the
> following.
> {code:title=www/autotest/tests/contacts.tests.js|borderStyle=solid}
> it("contacts.spec.11 should be able to define a ContactField object",
> function() {
> var contactField = new ContactField("home", "8005551212", true);
> expect(contactField).toBeDefined();
> expect(contactField.type).toBe("home");
> expect(contactField.value).toBe("8005551212");
> expect(contactField.pref).toBe(true);
> });
> {code}
> Is pref property not really supported?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-4611) ContactField pref property returns true in Android
[
https://issues.apache.org/jira/browse/CB-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018082#comment-15018082
]
Vladimir Kotikov edited comment on CB-4611 at 11/20/15 2:24 PM:
This test just tests if ContactField constructor acts properly and sets
{{pref}} field according to constructor's param.
{{pref}} is not supported by native Android implementation, and thus is
ignored, when saving contact, and always false, when querying contact from
device.
was (Author: vladimir.kotikov):
This test just tests if ContactField constructor acts properly and sets
{{pref}} field according to constructor's param.
{{pref}} is not supported by native Android implementation, and thus, {{pref}}
property is ingored, when saving contact and always false, when querying
contact from device.
> ContactField pref property returns true in Android
> --
>
> Key: CB-4611
> URL: https://issues.apache.org/jira/browse/CB-4611
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs, Plugin Contacts
>Affects Versions: 2.9.0
> Environment: Android 4.2 emulator
>Reporter: Shingo Toda
>Assignee: Michael Brooks
>Priority: Minor
> Labels: documentation
>
> I am looking into mobile-spec. [This
> document|http://cordova.apache.org/docs/en/2.9.0/cordova_contacts_contacts.md.html#ContactField]
> says
> {quote}
> *Android Quirks*
> pref: Not supported, returning false.
> {quote}
> But spec "contacts.spec.11 should be able to define a ContactField object" in
> contacts.tests.js(239) is passed, which pref is set to true. See the
> following.
> {code:title=www/autotest/tests/contacts.tests.js|borderStyle=solid}
> it("contacts.spec.11 should be able to define a ContactField object",
> function() {
> var contactField = new ContactField("home", "8005551212", true);
> expect(contactField).toBeDefined();
> expect(contactField.type).toBe("home");
> expect(contactField.value).toBe("8005551212");
> expect(contactField.pref).toBe(true);
> });
> {code}
> Is pref property not really supported?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-4921) ContactField Full Example only returns 1 contact
[
https://issues.apache.org/jira/browse/CB-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-4921:
-
Priority: Trivial (was: Minor)
> ContactField Full Example only returns 1 contact
>
>
> Key: CB-4921
> URL: https://issues.apache.org/jira/browse/CB-4921
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Mike Billau
>Priority: Trivial
> Labels: reproduced, triaged
>
> There is something unusual about the documented Full Example for ContactField
> [1]
> The code example saves a bunch of phone number contacts and then does a
> *contacts.find* presumably to demonstrate that the phone numbers just saved
> can be retrieved OK.
> The problem with the example is that the *options* does not specify
> _multiple=true_ and since the default is _options.multiple=false_ [2] there
> will never be multiple contacts returned. So the example won't display all
> what just got saved, and it is also contrary to the way the onSuccess method
> is expecting to iterate over multiple contacts.
> I think the code should say
> {quote}
> options.multiple=true;
> {quote}
> [1]
> http://cordova.apache.org/docs/en/3.0.0/cordova_contacts_contacts.md.html#ContactField
> [2]
> http://cordova.apache.org/docs/en/3.0.0/cordova_contacts_contacts.md.html#contactFindOptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-4921) ContactField Full Example only returns 1 contact
[
https://issues.apache.org/jira/browse/CB-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-4921:
-
Labels: reproduced triaged (was: )
> ContactField Full Example only returns 1 contact
>
>
> Key: CB-4921
> URL: https://issues.apache.org/jira/browse/CB-4921
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Mike Billau
>Priority: Minor
> Labels: reproduced, triaged
>
> There is something unusual about the documented Full Example for ContactField
> [1]
> The code example saves a bunch of phone number contacts and then does a
> *contacts.find* presumably to demonstrate that the phone numbers just saved
> can be retrieved OK.
> The problem with the example is that the *options* does not specify
> _multiple=true_ and since the default is _options.multiple=false_ [2] there
> will never be multiple contacts returned. So the example won't display all
> what just got saved, and it is also contrary to the way the onSuccess method
> is expecting to iterate over multiple contacts.
> I think the code should say
> {quote}
> options.multiple=true;
> {quote}
> [1]
> http://cordova.apache.org/docs/en/3.0.0/cordova_contacts_contacts.md.html#ContactField
> [2]
> http://cordova.apache.org/docs/en/3.0.0/cordova_contacts_contacts.md.html#contactFindOptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-4921) ContactField Full Example only returns 1 contact
[
https://issues.apache.org/jira/browse/CB-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-4921:
-
Component/s: (was: Docs)
> ContactField Full Example only returns 1 contact
>
>
> Key: CB-4921
> URL: https://issues.apache.org/jira/browse/CB-4921
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Mike Billau
>Priority: Minor
>
> There is something unusual about the documented Full Example for ContactField
> [1]
> The code example saves a bunch of phone number contacts and then does a
> *contacts.find* presumably to demonstrate that the phone numbers just saved
> can be retrieved OK.
> The problem with the example is that the *options* does not specify
> _multiple=true_ and since the default is _options.multiple=false_ [2] there
> will never be multiple contacts returned. So the example won't display all
> what just got saved, and it is also contrary to the way the onSuccess method
> is expecting to iterate over multiple contacts.
> I think the code should say
> {quote}
> options.multiple=true;
> {quote}
> [1]
> http://cordova.apache.org/docs/en/3.0.0/cordova_contacts_contacts.md.html#ContactField
> [2]
> http://cordova.apache.org/docs/en/3.0.0/cordova_contacts_contacts.md.html#contactFindOptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-5308) Contact.save() calls failure callback even though contact data is successfully saved on device
[
https://issues.apache.org/jira/browse/CB-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-5308:
-
Priority: Major (was: Minor)
> Contact.save() calls failure callback even though contact data is
> successfully saved on device
> --
>
> Key: CB-5308
> URL: https://issues.apache.org/jira/browse/CB-5308
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
> Environment: Android 4.1.2, 4.4.3 physical device. 4.4.3 device is
> Nexus 7.
> Cordova 3.1.0, 3.6.3
>Reporter: Shingo Toda
> Labels: Android, reproduced, triaged
>
> When I run contact mobile-spec, following specs sometimes fail.
> - contacts.spec.6
> - contacts.spec.20
> - contacts.spec.21
> - contacts.spec.24
> In Java side, it looks that {{ContactAccessorSdk5.save()}} returns contact id
> but {{ContactAccessorSdk5.getContactById()}} returns {{null}} instead of
> contact data associated with the id. Actually some of contact data such as
> "Test Delete" are found on my device so the save operation is actually done.
> This save() returns "newId" in the following code.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> //Add contact
> try {
> ContentProviderResult[] cpResults =
> mApp.getActivity().getContentResolver().applyBatch(ContactsContract.AUTHORITY,
> ops);
> if (cpResults.length >= 0) {
> newId = cpResults[0].uri.getLastPathSegment();
> }
> } catch (RemoteException e) {
> Log.e(LOG_TAG, e.getMessage(), e);
> } catch (OperationApplicationException e) {
> Log.e(LOG_TAG, e.getMessage(), e);
> }
> return newId;
> {code}
> When I debug it, {{cpResults\[0\].uri}} is
> {{content://com.android.contacts/raw_contacts/}} so, this is just my
> assumption, I think {{save()}} returns raw contact id.
> But at {{getContactById()}}, query filter uses {{CONTACT_ID}} column as a
> projection.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> Cursor c =
> mApp.getActivity().getContentResolver().query(ContactsContract.Data.CONTENT_URI,
> null,
> ContactsContract.Data.CONTACT_ID + " = ? ",
> new String[] { id },
> ContactsContract.Data.CONTACT_ID + " ASC");
> {code}
> So if contact id and raw contact id is different then fetching contact data
> might fail. Actually in my case, if I fail the specs, they are always
> different.
> I try modifying {{getContactById()}} to process following code if contact
> JSONObject doesn't have id property, then I didn't get failure for those
> specs even if I run them some times.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> Cursor c =
> mApp.getActivity().getContentResolver().query(ContactsContract.Data.CONTENT_URI,
> null,
> ContactsContract.Data.RAW_CONTACT_ID + " = ? ",
> new String[] { rawid },
> ContactsContract.Data.RAW_CONTACT_ID + " ASC");
> {code}
> I am just learning how contact data is managed on Android so I might be wrong
> for some use cases, but it works fine for mobile-spec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-5308) Contact.save() calls failure callback even though contact data is successfully saved on device
[
https://issues.apache.org/jira/browse/CB-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-5308:
-
Environment:
Android 4.1.2, 4.4.3 physical device. 4.4.3 device is Nexus 7.
Cordova 3.1.0, 3.6.3
was:Android 4.1.2, 4.4.3 physical device. 4.4.3 device is Nexus 7.
> Contact.save() calls failure callback even though contact data is
> successfully saved on device
> --
>
> Key: CB-5308
> URL: https://issues.apache.org/jira/browse/CB-5308
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
> Environment: Android 4.1.2, 4.4.3 physical device. 4.4.3 device is
> Nexus 7.
> Cordova 3.1.0, 3.6.3
>Reporter: Shingo Toda
>Priority: Minor
> Labels: Android, reproduced, triaged
>
> When I run contact mobile-spec, following specs sometimes fail.
> - contacts.spec.6
> - contacts.spec.20
> - contacts.spec.21
> - contacts.spec.24
> In Java side, it looks that {{ContactAccessorSdk5.save()}} returns contact id
> but {{ContactAccessorSdk5.getContactById()}} returns {{null}} instead of
> contact data associated with the id. Actually some of contact data such as
> "Test Delete" are found on my device so the save operation is actually done.
> This save() returns "newId" in the following code.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> //Add contact
> try {
> ContentProviderResult[] cpResults =
> mApp.getActivity().getContentResolver().applyBatch(ContactsContract.AUTHORITY,
> ops);
> if (cpResults.length >= 0) {
> newId = cpResults[0].uri.getLastPathSegment();
> }
> } catch (RemoteException e) {
> Log.e(LOG_TAG, e.getMessage(), e);
> } catch (OperationApplicationException e) {
> Log.e(LOG_TAG, e.getMessage(), e);
> }
> return newId;
> {code}
> When I debug it, {{cpResults\[0\].uri}} is
> {{content://com.android.contacts/raw_contacts/}} so, this is just my
> assumption, I think {{save()}} returns raw contact id.
> But at {{getContactById()}}, query filter uses {{CONTACT_ID}} column as a
> projection.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> Cursor c =
> mApp.getActivity().getContentResolver().query(ContactsContract.Data.CONTENT_URI,
> null,
> ContactsContract.Data.CONTACT_ID + " = ? ",
> new String[] { id },
> ContactsContract.Data.CONTACT_ID + " ASC");
> {code}
> So if contact id and raw contact id is different then fetching contact data
> might fail. Actually in my case, if I fail the specs, they are always
> different.
> I try modifying {{getContactById()}} to process following code if contact
> JSONObject doesn't have id property, then I didn't get failure for those
> specs even if I run them some times.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> Cursor c =
> mApp.getActivity().getContentResolver().query(ContactsContract.Data.CONTENT_URI,
> null,
> ContactsContract.Data.RAW_CONTACT_ID + " = ? ",
> new String[] { rawid },
> ContactsContract.Data.RAW_CONTACT_ID + " ASC");
> {code}
> I am just learning how contact data is managed on Android so I might be wrong
> for some use cases, but it works fine for mobile-spec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-5308) Contact.save() calls failure callback even though contact data is successfully saved on device
[
https://issues.apache.org/jira/browse/CB-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-5308:
-
Labels: Android reproduced triaged (was: Android)
> Contact.save() calls failure callback even though contact data is
> successfully saved on device
> --
>
> Key: CB-5308
> URL: https://issues.apache.org/jira/browse/CB-5308
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
> Environment: Android 4.1.2, 4.4.3 physical device. 4.4.3 device is
> Nexus 7.
> Cordova 3.1.0, 3.6.3
>Reporter: Shingo Toda
> Labels: Android, reproduced, triaged
>
> When I run contact mobile-spec, following specs sometimes fail.
> - contacts.spec.6
> - contacts.spec.20
> - contacts.spec.21
> - contacts.spec.24
> In Java side, it looks that {{ContactAccessorSdk5.save()}} returns contact id
> but {{ContactAccessorSdk5.getContactById()}} returns {{null}} instead of
> contact data associated with the id. Actually some of contact data such as
> "Test Delete" are found on my device so the save operation is actually done.
> This save() returns "newId" in the following code.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> //Add contact
> try {
> ContentProviderResult[] cpResults =
> mApp.getActivity().getContentResolver().applyBatch(ContactsContract.AUTHORITY,
> ops);
> if (cpResults.length >= 0) {
> newId = cpResults[0].uri.getLastPathSegment();
> }
> } catch (RemoteException e) {
> Log.e(LOG_TAG, e.getMessage(), e);
> } catch (OperationApplicationException e) {
> Log.e(LOG_TAG, e.getMessage(), e);
> }
> return newId;
> {code}
> When I debug it, {{cpResults\[0\].uri}} is
> {{content://com.android.contacts/raw_contacts/}} so, this is just my
> assumption, I think {{save()}} returns raw contact id.
> But at {{getContactById()}}, query filter uses {{CONTACT_ID}} column as a
> projection.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> Cursor c =
> mApp.getActivity().getContentResolver().query(ContactsContract.Data.CONTENT_URI,
> null,
> ContactsContract.Data.CONTACT_ID + " = ? ",
> new String[] { id },
> ContactsContract.Data.CONTACT_ID + " ASC");
> {code}
> So if contact id and raw contact id is different then fetching contact data
> might fail. Actually in my case, if I fail the specs, they are always
> different.
> I try modifying {{getContactById()}} to process following code if contact
> JSONObject doesn't have id property, then I didn't get failure for those
> specs even if I run them some times.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> Cursor c =
> mApp.getActivity().getContentResolver().query(ContactsContract.Data.CONTENT_URI,
> null,
> ContactsContract.Data.RAW_CONTACT_ID + " = ? ",
> new String[] { rawid },
> ContactsContract.Data.RAW_CONTACT_ID + " ASC");
> {code}
> I am just learning how contact data is managed on Android so I might be wrong
> for some use cases, but it works fine for mobile-spec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-5308) Contact.save() calls failure callback even though contact data is successfully saved on device
[
https://issues.apache.org/jira/browse/CB-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-5308:
-
Component/s: (was: mobile-spec)
> Contact.save() calls failure callback even though contact data is
> successfully saved on device
> --
>
> Key: CB-5308
> URL: https://issues.apache.org/jira/browse/CB-5308
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
> Environment: Android 4.1.2, 4.4.3 physical device. 4.4.3 device is
> Nexus 7.
>Reporter: Shingo Toda
>Priority: Minor
> Labels: Android
>
> When I run contact mobile-spec, following specs sometimes fail.
> - contacts.spec.6
> - contacts.spec.20
> - contacts.spec.21
> - contacts.spec.24
> In Java side, it looks that {{ContactAccessorSdk5.save()}} returns contact id
> but {{ContactAccessorSdk5.getContactById()}} returns {{null}} instead of
> contact data associated with the id. Actually some of contact data such as
> "Test Delete" are found on my device so the save operation is actually done.
> This save() returns "newId" in the following code.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> //Add contact
> try {
> ContentProviderResult[] cpResults =
> mApp.getActivity().getContentResolver().applyBatch(ContactsContract.AUTHORITY,
> ops);
> if (cpResults.length >= 0) {
> newId = cpResults[0].uri.getLastPathSegment();
> }
> } catch (RemoteException e) {
> Log.e(LOG_TAG, e.getMessage(), e);
> } catch (OperationApplicationException e) {
> Log.e(LOG_TAG, e.getMessage(), e);
> }
> return newId;
> {code}
> When I debug it, {{cpResults\[0\].uri}} is
> {{content://com.android.contacts/raw_contacts/}} so, this is just my
> assumption, I think {{save()}} returns raw contact id.
> But at {{getContactById()}}, query filter uses {{CONTACT_ID}} column as a
> projection.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> Cursor c =
> mApp.getActivity().getContentResolver().query(ContactsContract.Data.CONTENT_URI,
> null,
> ContactsContract.Data.CONTACT_ID + " = ? ",
> new String[] { id },
> ContactsContract.Data.CONTACT_ID + " ASC");
> {code}
> So if contact id and raw contact id is different then fetching contact data
> might fail. Actually in my case, if I fail the specs, they are always
> different.
> I try modifying {{getContactById()}} to process following code if contact
> JSONObject doesn't have id property, then I didn't get failure for those
> specs even if I run them some times.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> Cursor c =
> mApp.getActivity().getContentResolver().query(ContactsContract.Data.CONTENT_URI,
> null,
> ContactsContract.Data.RAW_CONTACT_ID + " = ? ",
> new String[] { rawid },
> ContactsContract.Data.RAW_CONTACT_ID + " ASC");
> {code}
> I am just learning how contact data is managed on Android so I might be wrong
> for some use cases, but it works fine for mobile-spec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-5308) Contact.save() calls failure callback even though contact data is successfully saved on device
[
https://issues.apache.org/jira/browse/CB-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-5308:
-
Affects Version/s: (was: 3.6.3)
(was: 3.1.0)
> Contact.save() calls failure callback even though contact data is
> successfully saved on device
> --
>
> Key: CB-5308
> URL: https://issues.apache.org/jira/browse/CB-5308
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
> Environment: Android 4.1.2, 4.4.3 physical device. 4.4.3 device is
> Nexus 7.
>Reporter: Shingo Toda
>Priority: Minor
> Labels: Android
>
> When I run contact mobile-spec, following specs sometimes fail.
> - contacts.spec.6
> - contacts.spec.20
> - contacts.spec.21
> - contacts.spec.24
> In Java side, it looks that {{ContactAccessorSdk5.save()}} returns contact id
> but {{ContactAccessorSdk5.getContactById()}} returns {{null}} instead of
> contact data associated with the id. Actually some of contact data such as
> "Test Delete" are found on my device so the save operation is actually done.
> This save() returns "newId" in the following code.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> //Add contact
> try {
> ContentProviderResult[] cpResults =
> mApp.getActivity().getContentResolver().applyBatch(ContactsContract.AUTHORITY,
> ops);
> if (cpResults.length >= 0) {
> newId = cpResults[0].uri.getLastPathSegment();
> }
> } catch (RemoteException e) {
> Log.e(LOG_TAG, e.getMessage(), e);
> } catch (OperationApplicationException e) {
> Log.e(LOG_TAG, e.getMessage(), e);
> }
> return newId;
> {code}
> When I debug it, {{cpResults\[0\].uri}} is
> {{content://com.android.contacts/raw_contacts/}} so, this is just my
> assumption, I think {{save()}} returns raw contact id.
> But at {{getContactById()}}, query filter uses {{CONTACT_ID}} column as a
> projection.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> Cursor c =
> mApp.getActivity().getContentResolver().query(ContactsContract.Data.CONTENT_URI,
> null,
> ContactsContract.Data.CONTACT_ID + " = ? ",
> new String[] { id },
> ContactsContract.Data.CONTACT_ID + " ASC");
> {code}
> So if contact id and raw contact id is different then fetching contact data
> might fail. Actually in my case, if I fail the specs, they are always
> different.
> I try modifying {{getContactById()}} to process following code if contact
> JSONObject doesn't have id property, then I didn't get failure for those
> specs even if I run them some times.
> {code:title=ContactAccessorSdk5.java|borderStyle=solid}
> Cursor c =
> mApp.getActivity().getContentResolver().query(ContactsContract.Data.CONTENT_URI,
> null,
> ContactsContract.Data.RAW_CONTACT_ID + " = ? ",
> new String[] { rawid },
> ContactsContract.Data.RAW_CONTACT_ID + " ASC");
> {code}
> I am just learning how contact data is managed on Android so I might be wrong
> for some use cases, but it works fine for mobile-spec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-5645) IOS7 null returned for Contacts API displayName
[ https://issues.apache.org/jira/browse/CB-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-5645. Resolution: Not A Problem Assignee: Vladimir Kotikov > IOS7 null returned for Contacts API displayName > --- > > Key: CB-5645 > URL: https://issues.apache.org/jira/browse/CB-5645 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Affects Versions: 3.1.0 > Environment: IOS 7.0 >Reporter: Vishal >Assignee: Vladimir Kotikov > Labels: ios, triaged > > In IOS7 when using the Contacts API to retrieve a list of contacts the > displayName field is null even if the contact has a first/last name. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-5645) IOS7 null returned for Contacts API displayName
[ https://issues.apache.org/jira/browse/CB-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-5645: - Labels: ios triaged (was: ios) > IOS7 null returned for Contacts API displayName > --- > > Key: CB-5645 > URL: https://issues.apache.org/jira/browse/CB-5645 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Affects Versions: 3.1.0 > Environment: IOS 7.0 >Reporter: Vishal > Labels: ios, triaged > > In IOS7 when using the Contacts API to retrieve a list of contacts the > displayName field is null even if the contact has a first/last name. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-5645) IOS7 null returned for Contacts API displayName
[
https://issues.apache.org/jira/browse/CB-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018042#comment-15018042
]
Vladimir Kotikov commented on CB-5645:
--
According to docs, {{displayName}} is null on iOS and will be returned only if
{{options.desiredFields}} contains {{'displayName'}}. See
https://github.com/apache/cordova-plugin-contacts#ios-quirks for more info.
> IOS7 null returned for Contacts API displayName
> ---
>
> Key: CB-5645
> URL: https://issues.apache.org/jira/browse/CB-5645
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Contacts
>Affects Versions: 3.1.0
> Environment: IOS 7.0
>Reporter: Vishal
> Labels: ios
>
> In IOS7 when using the Contacts API to retrieve a list of contacts the
> displayName field is null even if the contact has a first/last name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-6861) Automated mobile-spec tests wont run with latest Contacts plugin
[ https://issues.apache.org/jira/browse/CB-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-6861. Resolution: Fixed Closing this as outdated. No plugin tests failures reported by https://ci.apache.org/builders/cordova-wp8 > Automated mobile-spec tests wont run with latest Contacts plugin > > > Key: CB-6861 > URL: https://issues.apache.org/jira/browse/CB-6861 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Reporter: Staci Cooper >Assignee: Jesse MacFadyen >Priority: Minor > Labels: WP8, mobilespec, outdated > > With all repos checked out at master, run: > ./cordova-mobile-spec/createmobilespec/createmobilespec.js --wp8 > Then when you try to run the automated tests, you get a blank screen and the > warning that deviceready has not fired. If you checkout > cordova-plugin-contacts at the r0.2.10 tag (everything else still on master) > and then create mobilespec, all tests run as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-6861) Automated mobile-spec tests wont run with latest Contacts plugin
[ https://issues.apache.org/jira/browse/CB-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-6861: - Labels: WP8 mobilespec outdated (was: ) > Automated mobile-spec tests wont run with latest Contacts plugin > > > Key: CB-6861 > URL: https://issues.apache.org/jira/browse/CB-6861 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Reporter: Staci Cooper >Assignee: Jesse MacFadyen >Priority: Minor > Labels: WP8, mobilespec, outdated > > With all repos checked out at master, run: > ./cordova-mobile-spec/createmobilespec/createmobilespec.js --wp8 > Then when you try to run the automated tests, you get a blank screen and the > warning that deviceready has not fired. If you checkout > cordova-plugin-contacts at the r0.2.10 tag (everything else still on master) > and then create mobilespec, all tests run as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-6861) Automated mobile-spec tests wont run with latest Contacts plugin
[ https://issues.apache.org/jira/browse/CB-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-6861: - Affects Version/s: (was: 3.5.0) > Automated mobile-spec tests wont run with latest Contacts plugin > > > Key: CB-6861 > URL: https://issues.apache.org/jira/browse/CB-6861 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Reporter: Staci Cooper >Assignee: Jesse MacFadyen >Priority: Minor > Labels: WP8, mobilespec, outdated > > With all repos checked out at master, run: > ./cordova-mobile-spec/createmobilespec/createmobilespec.js --wp8 > Then when you try to run the automated tests, you get a blank screen and the > warning that deviceready has not fired. If you checkout > cordova-plugin-contacts at the r0.2.10 tag (everything else still on master) > and then create mobilespec, all tests run as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-6861) Automated mobile-spec tests wont run with latest Contacts plugin
[ https://issues.apache.org/jira/browse/CB-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-6861: - Component/s: (was: WP8) (was: mobile-spec) > Automated mobile-spec tests wont run with latest Contacts plugin > > > Key: CB-6861 > URL: https://issues.apache.org/jira/browse/CB-6861 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Reporter: Staci Cooper >Assignee: Jesse MacFadyen >Priority: Minor > Labels: WP8, mobilespec, outdated > > With all repos checked out at master, run: > ./cordova-mobile-spec/createmobilespec/createmobilespec.js --wp8 > Then when you try to run the automated tests, you get a blank screen and the > warning that deviceready has not fired. If you checkout > cordova-plugin-contacts at the r0.2.10 tag (everything else still on master) > and then create mobilespec, all tests run as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-7247) Incorrect info in contact docs for the options parameter for contacts.find
[ https://issues.apache.org/jira/browse/CB-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-7247. Resolution: Fixed Assignee: Vladimir Kotikov The bug was fixed in master. Regarding the documentation, i believe we maintain only the one version of documentation, so there is no actions needed. > Incorrect info in contact docs for the options parameter for contacts.find > -- > > Key: CB-7247 > URL: https://issues.apache.org/jira/browse/CB-7247 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Affects Versions: Master > Environment: all >Reporter: Sebastian Miller-Hack >Assignee: Vladimir Kotikov >Priority: Minor > Labels: documentation > Original Estimate: 10m > Remaining Estimate: 10m > > The parameter contactFindOptions of navigator.contacts.find is labeled > optional but actually is required. > \ > @sgrebnov fixed the issue in the production branch > (https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;a=commit;h=413cea9d5a5def821014eaadbb85cec5213ed4c3) > but the docs are still incorrect for older releases. > This issue will now address fixing the docs for previous versions of the > plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-7543) Contact picker search box does not appear if contact permissions were requested
[ https://issues.apache.org/jira/browse/CB-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-7543. Resolution: Cannot Reproduce Assignee: Vladimir Kotikov [~mcypark], I wasn't able to reproduce this using latest versions of cordova and contacts plugin. Closing this, feel free to reopen in case if this occur again. > Contact picker search box does not appear if contact permissions were > requested > --- > > Key: CB-7543 > URL: https://issues.apache.org/jira/browse/CB-7543 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts > Environment: iOS, Cordova 3.5.0 >Reporter: Micahel Park >Assignee: Vladimir Kotikov >Priority: Minor > Labels: iOS > > I've implemented the cordova contact picker plugin in an ionic ios sample > app. The issue that I'm running into is that on first run, after the contact > picker asks for permission to contacts, I don't see the search box at the top > of the contact picker. On subsequent calls to the contact picker, everything > shows up correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-7543) Contact picker search box does not appear if contact permissions were requested
[ https://issues.apache.org/jira/browse/CB-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-7543: - Labels: iOS (was: ) > Contact picker search box does not appear if contact permissions were > requested > --- > > Key: CB-7543 > URL: https://issues.apache.org/jira/browse/CB-7543 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts > Environment: iOS, Cordova 3.5.0 >Reporter: Micahel Park >Priority: Minor > Labels: iOS > > I've implemented the cordova contact picker plugin in an ionic ios sample > app. The issue that I'm running into is that on first run, after the contact > picker asks for permission to contacts, I don't see the search box at the top > of the contact picker. On subsequent calls to the contact picker, everything > shows up correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
