[jira] [Updated] (CB-9845) inappbrowser close function not working as intended, leaving instance of inappbrowser running

[Sebastian Betzinger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebastian Betzinger updated CB-9845:

Description: 
recent cordova tools 5.3.3, recent inappbrowser 1.0.1

Code to reproduce:

var ref;

function xy() {
ref = cordova.InAppBrowser.open(...);
}

function ab() {
ref.close();
xy();
}

xy();

ab();


First InAppBrowser instance stays opened with url "about:blank" in foreground 
and a second instance of InAppBrowser is launched in background with actual 
content. Using show() function on second instance does not bring second 
inappbrowser to foreground, so every newly launched instance is stuck in 
background.

Should be: instance of InAppBrowser should be purged and closed instead of 
being held with "about:blank"

Also using the Toolbar/Locationbar to close the inappbrowser leaves the 
instance on device. This is a matter in lack of performance regarding long time 
running of the apps.

  was:
Code to reproduce:

var ref;

function xy() {
ref = cordova.InAppBrowser.open(...);
}

function ab() {
ref.close();
xy();
}

xy();

ab();


First InAppBrowser instance stays opened with url "about:blank" in foreground 
and a second instance of InAppBrowser is launched in background with actual 
content. Using show() function on second instance does not bring second 
inappbrowser to foreground, so every newly launched instance is stuck in 
background.

Should be: instance of InAppBrowser should be purged and closed instead of 
being held with "about:blank"

Also using the Toolbar/Locationbar to close the inappbrowser leaves the 
instance on device. This is a matter in lack of performance regarding long time 
running of the apps.


> inappbrowser close function not working as intended, leaving instance of 
> inappbrowser running
> -
>
> Key: CB-9845
> URL: https://issues.apache.org/jira/browse/CB-9845
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, iOS, Plugin InAppBrowser
>Affects Versions: Master
> Environment: Mac OSX/Win10/Ubuntu14.04
>Reporter: Sebastian Betzinger
>Priority: Critical
>  Labels: 1.0.1, inappbrowser
>
> recent cordova tools 5.3.3, recent inappbrowser 1.0.1
> Code to reproduce:
> var ref;
> function xy() {
> ref = cordova.InAppBrowser.open(...);
> }
> function ab() {
> ref.close();
> xy();
> }
> xy();
> ab();
> First InAppBrowser instance stays opened with url "about:blank" in foreground 
> and a second instance of InAppBrowser is launched in background with actual 
> content. Using show() function on second instance does not bring second 
> inappbrowser to foreground, so every newly launched instance is stuck in 
> background.
> Should be: instance of InAppBrowser should be purged and closed instead of 
> being held with "about:blank"
> Also using the Toolbar/Locationbar to close the inappbrowser leaves the 
> instance on device. This is a matter in lack of performance regarding long 
> time running of the apps.



--
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-9845) inappbrowser close function not working as intended, leaving instance of inappbrowser running

[Sebastian Betzinger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebastian Betzinger updated CB-9845:

Labels: 1.0.1 inappbrowser  (was: )

> inappbrowser close function not working as intended, leaving instance of 
> inappbrowser running
> -
>
> Key: CB-9845
> URL: https://issues.apache.org/jira/browse/CB-9845
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, iOS, Plugin InAppBrowser
>Affects Versions: Master
> Environment: Mac OSX/Win10/Ubuntu14.04
>Reporter: Sebastian Betzinger
>Priority: Critical
>  Labels: 1.0.1, inappbrowser
>
> Code to reproduce:
> var ref;
> function xy() {
> ref = cordova.InAppBrowser.open(...);
> }
> function ab() {
> ref.close();
> xy();
> }
> xy();
> ab();
> First InAppBrowser instance stays opened with url "about:blank" in foreground 
> and a second instance of InAppBrowser is launched in background with actual 
> content. Using show() function on second instance does not bring second 
> inappbrowser to foreground, so every newly launched instance is stuck in 
> background.
> Should be: instance of InAppBrowser should be purged and closed instead of 
> being held with "about:blank"
> Also using the Toolbar/Locationbar to close the inappbrowser leaves the 
> instance on device. This is a matter in lack of performance regarding long 
> time running of the apps.



--
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-9845) inappbrowser close function not working as intended, leaving instance of inappbrowser running

[Sebastian Betzinger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebastian Betzinger updated CB-9845:

Description: 
Code to reproduce:

var ref;

function xy() {
ref = cordova.InAppBrowser.open(...);
}

function ab() {
ref.close();
xy();
}

xy();

ab();


First InAppBrowser instance stays opened with url "about:blank" in foreground 
and a second instance of InAppBrowser is launched in background with actual 
content. Using show() function on second instance does not bring second 
inappbrowser to foreground, so every newly launched instance is stuck in 
background.

Should be: instance of InAppBrowser should be purged and closed instead of 
being held with "about:blank"

Also using the Toolbar/Locationbar to close the inappbrowser leaves the 
instance on device. This is a matter in lack of performance regarding long time 
running of the apps.

  was:
Code of index.js:

var ref;

function xy() {
ref = cordova.InAppBrowser.open(...);
}

function ab() {
ref.close();
xy();
}

xy();

ab();


InAppBrowser instance stays opened with url "about:blank" in foreground and a 
second instance of InAppBrowser is launched in background.

Should be: instance of InAppBrowser should be purged and closed instead of 
being held with "about:blank"

Also using the Toolbar/Locationbar to close the inappbrowser leaves the 
instance on device. This is a matter in lack of performance regarding long time 
running of the app.


> inappbrowser close function not working as intended, leaving instance of 
> inappbrowser running
> -
>
> Key: CB-9845
> URL: https://issues.apache.org/jira/browse/CB-9845
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, iOS, Plugin InAppBrowser
>Affects Versions: Master
> Environment: Mac OSX/Win10/Ubuntu14.04
>Reporter: Sebastian Betzinger
>Priority: Critical
>  Labels: 1.0.1, inappbrowser
>
> Code to reproduce:
> var ref;
> function xy() {
> ref = cordova.InAppBrowser.open(...);
> }
> function ab() {
> ref.close();
> xy();
> }
> xy();
> ab();
> First InAppBrowser instance stays opened with url "about:blank" in foreground 
> and a second instance of InAppBrowser is launched in background with actual 
> content. Using show() function on second instance does not bring second 
> inappbrowser to foreground, so every newly launched instance is stuck in 
> background.
> Should be: instance of InAppBrowser should be purged and closed instead of 
> being held with "about:blank"
> Also using the Toolbar/Locationbar to close the inappbrowser leaves the 
> instance on device. This is a matter in lack of performance regarding long 
> time running of the apps.



--
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-9845) inappbrowser close function not working as intended, leaving instance of inappbrowser running

[Sebastian Betzinger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebastian Betzinger updated CB-9845:

Description: 
Code of index.js:

var ref;

function xy() {
ref = cordova.InAppBrowser.open(...);
}

function ab() {
ref.close();
xy();
}

xy();

ab();


InAppBrowser instance stays opened with url "about:blank" in foreground and a 
second instance of InAppBrowser is launched in background.

Should be: instance of InAppBrowser should be purged and closed instead of 
being held with "about:blank"

Also using the Toolbar/Locationbar to close the inappbrowser leaves the 
instance on device. This is a matter in lack of performance regarding long time 
running of the app.

  was:
Code of index.js:

var ref;

function xy() {
ref = cordova.InAppBrowser.open(...);
}

function ab() {
ref.close();
xy();
}

xy();

ab();


InAppBrowser instance stays opened with url "about:blank" in foreground and a 
second instance of InAppBrowser is launched in background.

Should be: instance of InAppBrowser should be purged and closed instead of 
being held with "about:blank"


> inappbrowser close function not working as intended, leaving instance of 
> inappbrowser running
> -
>
> Key: CB-9845
> URL: https://issues.apache.org/jira/browse/CB-9845
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, iOS, Plugin InAppBrowser
>Affects Versions: Master
> Environment: Mac OSX/Win10/Ubuntu14.04
>Reporter: Sebastian Betzinger
>Priority: Critical
>
> Code of index.js:
> var ref;
> function xy() {
> ref = cordova.InAppBrowser.open(...);
> }
> function ab() {
> ref.close();
> xy();
> }
> xy();
> ab();
> InAppBrowser instance stays opened with url "about:blank" in foreground and a 
> second instance of InAppBrowser is launched in background.
> Should be: instance of InAppBrowser should be purged and closed instead of 
> being held with "about:blank"
> Also using the Toolbar/Locationbar to close the inappbrowser leaves the 
> instance on device. This is a matter in lack of performance regarding long 
> time running of the app.



--
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-9702) Fix plugin initialization based on XCode 7.0 compiler warnings

[Jesse MacFadyen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jesse MacFadyen resolved CB-9702.
-
Resolution: Fixed

Thanks Perry!

> Fix plugin initialization based on XCode 7.0 compiler warnings
> --
>
> Key: CB-9702
> URL: https://issues.apache.org/jira/browse/CB-9702
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Network Information
>Affects Versions: Master
> Environment: XCode Version 7.0 (7A220)
>Reporter: Perry Stoll
>
> xcode complains "These will always evaluate to true", which, looking at these 
> lines, makes sense. These things are objects, taking their address will 
> always yield a non-null value. 
> {code}
> cordova-plugin-network-information pstoll$ git diff
> diff --git a/src/ios/CDVConnection.m b/src/ios/CDVConnection.m
> index 3749767..223dd7c 100644
> --- a/src/ios/CDVConnection.m
> +++ b/src/ios/CDVConnection.m
> @@ -118,7 +118,7 @@
>  [self.internetReach startNotifier];
>  [[NSNotificationCenter defaultCenter] addObserver:self 
> selector:@selector(updateConnectionType:)
>   
> name:kReachabilityChangedNotification object:nil];
> -if (&UIApplicationDidEnterBackgroundNotification && 
> &UIApplicationWillEnterForegroundNotification) {
> +if (UIApplicationDidEnterBackgroundNotification && 
> UIApplicationWillEnterForegroundNotification) {
>  [[NSNotificationCenter defaultCenter] addObserver:self 
> selector:@selector(onPause) name:UIApplicationDidEnterBackgroundNotification 
> object:nil];
>  [[NSNotificationCenter defaultCenter] addObserver:self 
> selector:@selector(onResume) 
> name:UIApplicationWillEnterForegroundNotification object:nil];
>  }
> {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] [Commented] (CB-9702) Fix plugin initialization based on XCode 7.0 compiler warnings

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970449#comment-14970449
 ] 

ASF subversion and git services commented on CB-9702:
-

Commit 1132a185666fb60acdcddfa801d59525a8535d38 in 
cordova-plugin-network-information's branch refs/heads/master from 
[~purplecabbage]
[ 
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-network-information.git;h=1132a18
 ]

Merge branch 'CB-9702' of 
https://github.com/pstoll/cordova-plugin-network-information


> Fix plugin initialization based on XCode 7.0 compiler warnings
> --
>
> Key: CB-9702
> URL: https://issues.apache.org/jira/browse/CB-9702
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Network Information
>Affects Versions: Master
> Environment: XCode Version 7.0 (7A220)
>Reporter: Perry Stoll
>
> xcode complains "These will always evaluate to true", which, looking at these 
> lines, makes sense. These things are objects, taking their address will 
> always yield a non-null value. 
> {code}
> cordova-plugin-network-information pstoll$ git diff
> diff --git a/src/ios/CDVConnection.m b/src/ios/CDVConnection.m
> index 3749767..223dd7c 100644
> --- a/src/ios/CDVConnection.m
> +++ b/src/ios/CDVConnection.m
> @@ -118,7 +118,7 @@
>  [self.internetReach startNotifier];
>  [[NSNotificationCenter defaultCenter] addObserver:self 
> selector:@selector(updateConnectionType:)
>   
> name:kReachabilityChangedNotification object:nil];
> -if (&UIApplicationDidEnterBackgroundNotification && 
> &UIApplicationWillEnterForegroundNotification) {
> +if (UIApplicationDidEnterBackgroundNotification && 
> UIApplicationWillEnterForegroundNotification) {
>  [[NSNotificationCenter defaultCenter] addObserver:self 
> selector:@selector(onPause) name:UIApplicationDidEnterBackgroundNotification 
> object:nil];
>  [[NSNotificationCenter defaultCenter] addObserver:self 
> selector:@selector(onResume) 
> name:UIApplicationWillEnterForegroundNotification object:nil];
>  }
> {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] [Commented] (CB-9519) Inappropriate destruction time of engine in CordovaWebViewImpl

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970431#comment-14970431
 ] 

ASF GitHub Bot commented on CB-9519:


Github user DILEEP-YADAV commented on the pull request:

https://github.com/apache/cordova-android/pull/208#issuecomment-150468569
  
ok



> Inappropriate destruction time of engine in CordovaWebViewImpl
> --
>
> Key: CB-9519
> URL: https://issues.apache.org/jira/browse/CB-9519
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Reporter: Dong Hanlin
>Assignee: Vladimir Kotikov
>
> In {{CordovaWebViewImpl.java}}, one of the TODO comments in {{public void 
> handleDestroy()}} method points out that the engine should not destroy 
> webview until after about:blank is done loading. Actually, the engine has 
> indeed been destroyed before about:blank is completely loaded, which causes 
> some problems.
> I think moving a line of code may work:
> {quote}
> engine.destroy();
> {quote}
> This code can be moved into the last {{if}} block in {{public void 
> onPageFinishedLoading(String url)}}, like this:
> {code}
> // Shutdown if blank loaded
> if (url.equals("about:blank")) {
> engine.destroy();
> pluginManager.postMessage("exit", null);
> }
> {code}
> Since before destroying the engine, we have set the URL to be about:blank, so 
> destroying it when about:blank is completed loaded can work.



--
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-9845) inappbrowser close function not working as intended, leaving instance of inappbrowser running

[Sebastian Betzinger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebastian Betzinger updated CB-9845:

Description: 
Code of index.js:

var ref;

function xy() {
ref = cordova.InAppBrowser.open(...);
}

function ab() {
ref.close();
xy();
}

xy();

ab();


InAppBrowser instance stays opened with url "about:blank" in foreground and a 
second instance of InAppBrowser is launched in background.

Should be: instance of InAppBrowser should be purged and closed instead of 
being held with "about:blank"

  was:
Code of index.js:

var ref;

function xy() {
ref = cordova.InAppBrowser.open(...);
}

function ab() {
ref.close();
xy();
}

ab();


InAppBrowser instance stays opened with url "about:blank" in foreground and a 
second instance of InAppBrowser is launched in background.

Should be: instance of InAppBrowser should be purged and closed instead of 
being held with "about:blank"


> inappbrowser close function not working as intended, leaving instance of 
> inappbrowser running
> -
>
> Key: CB-9845
> URL: https://issues.apache.org/jira/browse/CB-9845
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, iOS, Plugin InAppBrowser
>Affects Versions: Master
> Environment: Mac OSX/Win10/Ubuntu14.04
>Reporter: Sebastian Betzinger
>Priority: Critical
>
> Code of index.js:
> var ref;
> function xy() {
> ref = cordova.InAppBrowser.open(...);
> }
> function ab() {
> ref.close();
> xy();
> }
> xy();
> ab();
> InAppBrowser instance stays opened with url "about:blank" in foreground and a 
> second instance of InAppBrowser is launched in background.
> Should be: instance of InAppBrowser should be purged and closed instead of 
> being held with "about:blank"



--
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-9845) inappbrowser close function not working as intended, leaving instance of inappbrowser running

[Sebastian Betzinger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebastian Betzinger updated CB-9845:

Affects Version/s: (was: 3.5.0)

> inappbrowser close function not working as intended, leaving instance of 
> inappbrowser running
> -
>
> Key: CB-9845
> URL: https://issues.apache.org/jira/browse/CB-9845
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, iOS, Plugin InAppBrowser
>Affects Versions: Master
> Environment: Mac OSX/Win10/Ubuntu14.04
>Reporter: Sebastian Betzinger
>Priority: Critical
>
> Code of index.js:
> var ref;
> function xy() {
> ref = cordova.InAppBrowser.open(...);
> }
> function ab() {
> ref.close();
> xy();
> }
> ab();
> InAppBrowser instance stays opened with url "about:blank" in foreground and a 
> second instance of InAppBrowser is launched in background.
> Should be: instance of InAppBrowser should be purged and closed instead of 
> being held with "about:blank"



--
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-9736) 2 main activities are generated when a package name is specified

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970397#comment-14970397
 ] 

ASF GitHub Bot commented on CB-9736:


Github user stevengill commented on the pull request:

https://github.com/apache/cordova-lib/pull/328#issuecomment-150461925
  
Definitely. Thanks!

On Thu, Oct 22, 2015 at 5:27 PM, Gorkem Ercan 
wrote:

> @stevengill  Yes, created CB-9844 to
> follow up. This one is still valid for fixing older android engines 
though.
>
> —
> Reply to this email directly or view it on GitHub
> .
>



> 2 main activities are generated when a package name is specified
> 
>
> Key: CB-9736
> URL: https://issues.apache.org/jira/browse/CB-9736
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 3.5.0
>Reporter: Gorkem ERCAN
>Assignee: Gorkem ERCAN
>Priority: Minor
>
> If android-packageName is specified on the config.xml two main activity 
> classes are generated. One with with the package name as specified on id 
> attribute and one with the value of android-packageName. This does not seem 
> to cause any problems as AndroidManifest.xml references the 
> android-packageName value.



--
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-9848) UILaunchImages array is invalid, causing iOS 9 devices to display at 320x480px scaled sizes

[Woon Tien Jing (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Woon Tien Jing closed CB-9848.
--
Resolution: Invalid

> UILaunchImages array is invalid, causing iOS 9 devices to display at 
> 320x480px scaled sizes
> ---
>
> Key: CB-9848
> URL: https://issues.apache.org/jira/browse/CB-9848
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: iOS
>Affects Versions: 3.7.0
> Environment: Mac OS X El Capitan, Xcode 7, iOS 9 simulator (and 
> devices)
>Reporter: Woon Tien Jing
>  Labels: easyfix, fix-provided
>
> UILaunchImages is checked more thoroughly on iOS9 so Cordova-iOS 3.7.0's 
> invalid format is rejected and the app falls back to 320x480 scaled mode. 
> Required fix is given below.
> In Info.plist, each item in the UILaunchImages array has the form:
> 
> UILaunchImageOrientation
> Portrait
> UILaunchImageName
> Default-Portrait~ipad
> UILaunchImageSize
> {768, 1024}
>   
> According to Apple's documentation, each item must have a 
> `UILaunchImageMinimumOSVersion` 
> (https://developer.apple.com/library/prerelease/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW28)::
> 
> UILaunchImageMinimumOSVersion
> 7.0
> UILaunchImageOrientation
> Portrait
> UILaunchImageName
> Default-Portrait~ipad
> UILaunchImageSize
> {768, 1024}
>   



--
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-9848) UILaunchImages array is invalid, causing iOS 9 devices to display at 320x480px scaled sizes

[Woon Tien Jing (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970296#comment-14970296
 ] 

Woon Tien Jing commented on CB-9848:


Sorry, looks like one of my build scripts is inserting this incorrect 
UILaunchImages array. Most likely nothing wrong in Cordova-iOS.

Please ignore.

> UILaunchImages array is invalid, causing iOS 9 devices to display at 
> 320x480px scaled sizes
> ---
>
> Key: CB-9848
> URL: https://issues.apache.org/jira/browse/CB-9848
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: iOS
>Affects Versions: 3.7.0
> Environment: Mac OS X El Capitan, Xcode 7, iOS 9 simulator (and 
> devices)
>Reporter: Woon Tien Jing
>  Labels: easyfix, fix-provided
>
> UILaunchImages is checked more thoroughly on iOS9 so Cordova-iOS 3.7.0's 
> invalid format is rejected and the app falls back to 320x480 scaled mode. 
> Required fix is given below.
> In Info.plist, each item in the UILaunchImages array has the form:
> 
> UILaunchImageOrientation
> Portrait
> UILaunchImageName
> Default-Portrait~ipad
> UILaunchImageSize
> {768, 1024}
>   
> According to Apple's documentation, each item must have a 
> `UILaunchImageMinimumOSVersion` 
> (https://developer.apple.com/library/prerelease/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW28)::
> 
> UILaunchImageMinimumOSVersion
> 7.0
> UILaunchImageOrientation
> Portrait
> UILaunchImageName
> Default-Portrait~ipad
> UILaunchImageSize
> {768, 1024}
>   



--
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-9848) UILaunchImages array is invalid, causing iOS 9 devices to display at 320x480px scaled sizes

[Woon Tien Jing (JIRA)]

Woon Tien Jing created CB-9848:
--

 Summary: UILaunchImages array is invalid, causing iOS 9 devices to 
display at 320x480px scaled sizes
 Key: CB-9848
 URL: https://issues.apache.org/jira/browse/CB-9848
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS
Affects Versions: 3.7.0
 Environment: Mac OS X El Capitan, Xcode 7, iOS 9 simulator (and 
devices)
Reporter: Woon Tien Jing


UILaunchImages is checked more thoroughly on iOS9 so Cordova-iOS 3.7.0's 
invalid format is rejected and the app falls back to 320x480 scaled mode. 
Required fix is given below.

In Info.plist, each item in the UILaunchImages array has the form:


UILaunchImageOrientation
Portrait
UILaunchImageName
Default-Portrait~ipad
UILaunchImageSize
{768, 1024}
  

According to Apple's documentation, each item must have a 
`UILaunchImageMinimumOSVersion` 
(https://developer.apple.com/library/prerelease/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW28)::


UILaunchImageMinimumOSVersion
7.0
UILaunchImageOrientation
Portrait
UILaunchImageName
Default-Portrait~ipad
UILaunchImageSize
{768, 1024}
  




--
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-9773) Old versions of docs pages should link directly to same page in current version

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970223#comment-14970223
 ] 

ASF GitHub Bot commented on CB-9773:


Github user asfgit closed the pull request at:

https://github.com/apache/cordova-docs/pull/399


> Old versions of docs pages should link directly to same page in current 
> version
> ---
>
> Key: CB-9773
> URL: https://issues.apache.org/jira/browse/CB-9773
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Website
>Reporter: Jan Piotrowski
>
> Old: https://cordova.apache.org/docs/en/4.0.0/guide/hybrid/plugins/index.html
> Current: 
> https://cordova.apache.org/docs/en/5.1.1/guide/hybrid/plugins/index.html
> The old version includes a text and link:
> > This version of the documentation is outdated! Click here for the latest 
> > released version: 5.1.1
> But the "5.1.1" is linked to the start page of the 5.1.1-docs instead of 
> directly to the same page in the 5.1.1 documentation. This should be changed, 
> so users can look at the same page of the documentation in the current 
> version.



--
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-9773) Old versions of docs pages should link directly to same page in current version

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970201#comment-14970201
 ] 

ASF GitHub Bot commented on CB-9773:


GitHub user dblotsky opened a pull request:

https://github.com/apache/cordova-docs/pull/399

[CB-9773] Switching versions goes to the same page, not to root



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-docs CB-9773

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-docs/pull/399.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 #399


commit c49c6fea714717f6aa2853948860763f593e8579
Author: Dmitry Blotsky 
Date:   2015-10-23T00:38:34Z

Making version-switching go to the same page.




> Old versions of docs pages should link directly to same page in current 
> version
> ---
>
> Key: CB-9773
> URL: https://issues.apache.org/jira/browse/CB-9773
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Website
>Reporter: Jan Piotrowski
>
> Old: https://cordova.apache.org/docs/en/4.0.0/guide/hybrid/plugins/index.html
> Current: 
> https://cordova.apache.org/docs/en/5.1.1/guide/hybrid/plugins/index.html
> The old version includes a text and link:
> > This version of the documentation is outdated! Click here for the latest 
> > released version: 5.1.1
> But the "5.1.1" is linked to the start page of the 5.1.1-docs instead of 
> directly to the same page in the 5.1.1 documentation. This should be changed, 
> so users can look at the same page of the documentation in the current 
> version.



--
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-9736) 2 main activities are generated when a package name is specified

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970181#comment-14970181
 ] 

ASF GitHub Bot commented on CB-9736:


Github user gorkem commented on the pull request:

https://github.com/apache/cordova-lib/pull/328#issuecomment-150394486
  
@stevengill Yes, created CB-9844 to follow up. This one is still valid for 
fixing older android engines though.


> 2 main activities are generated when a package name is specified
> 
>
> Key: CB-9736
> URL: https://issues.apache.org/jira/browse/CB-9736
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 3.5.0
>Reporter: Gorkem ERCAN
>Assignee: Gorkem ERCAN
>Priority: Minor
>
> If android-packageName is specified on the config.xml two main activity 
> classes are generated. One with with the package name as specified on id 
> attribute and one with the value of android-packageName. This does not seem 
> to cause any problems as AndroidManifest.xml references the 
> android-packageName value.



--
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-9583) Switch Camera to use Internal Storage for Temporary File

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970091#comment-14970091
 ] 

ASF subversion and git services commented on CB-9583:
-

Commit 8024c5de49888442992f8841740697ae151e1125 in cordova-plugin-camera's 
branch refs/heads/master from [~bowserj]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=8024c5d 
]

CB-9583: Permissions for Marshmallow


> Switch Camera to use Internal Storage for Temporary File
> 
>
> Key: CB-9583
> URL: https://issues.apache.org/jira/browse/CB-9583
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, Plugin Camera
>Reporter: Joe Bowser
>Assignee: Joe Bowser
>
> The camera requires too many permissions currently to do basic tasks like 
> capture a temporary image.  The temporary image should exist on Internal, not 
> external storage.  This is so that the users don't need to request 
> EXTERNAL_STORAGE permissions just to get an image and send it to a server.



--
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-9847) Cannot tell when running on Simulator ( Windows )

[Jesse MacFadyen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jesse MacFadyen updated CB-9847:

Summary: Cannot tell when running on Simulator ( Windows )  (was: Cannot 
tell when running on Simulator)

> Cannot tell when running on Simulator ( Windows )
> -
>
> Key: CB-9847
> URL: https://issues.apache.org/jira/browse/CB-9847
> Project: Apache Cordova
>  Issue Type: Improvement
>Reporter: Jesse MacFadyen
>Assignee: Jesse MacFadyen
>
> There are times where things simply won't work when we are running on the 
> simulator.  For example, if you are using the device-motion api you will 
> simply never receive a result when calling `getCurrentAcceleration`
> It would be nice if we could tell before the call if this is the case, and 
> avoid waiting for a result.
> Prior art in https://github.com/apache/cordova-plugin-device/pull/35



--
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-9847) Cannot tell when running on Simulator ( Windows )

[Jesse MacFadyen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970024#comment-14970024
 ] 

Jesse MacFadyen commented on CB-9847:
-

Support has been added for iOS, Android and WP8.
Need windows universal support

> Cannot tell when running on Simulator ( Windows )
> -
>
> Key: CB-9847
> URL: https://issues.apache.org/jira/browse/CB-9847
> Project: Apache Cordova
>  Issue Type: Improvement
>Reporter: Jesse MacFadyen
>Assignee: Jesse MacFadyen
>
> There are times where things simply won't work when we are running on the 
> simulator.  For example, if you are using the device-motion api you will 
> simply never receive a result when calling `getCurrentAcceleration`
> It would be nice if we could tell before the call if this is the case, and 
> avoid waiting for a result.
> Prior art in https://github.com/apache/cordova-plugin-device/pull/35



--
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-9736) 2 main activities are generated when a package name is specified

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970004#comment-14970004
 ] 

ASF GitHub Bot commented on CB-9736:


Github user stevengill commented on the pull request:

https://github.com/apache/cordova-lib/pull/328#issuecomment-150371632
  
This functionality is moving to the platforms themselves. For this fix to 
work in android@5.0+, you should look to add it to 
https://github.com/apache/cordova-android/blob/master/bin/templates/cordova/lib/prepare.js#L156


> 2 main activities are generated when a package name is specified
> 
>
> Key: CB-9736
> URL: https://issues.apache.org/jira/browse/CB-9736
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 3.5.0
>Reporter: Gorkem ERCAN
>Assignee: Gorkem ERCAN
>Priority: Minor
>
> If android-packageName is specified on the config.xml two main activity 
> classes are generated. One with with the package name as specified on id 
> attribute and one with the value of android-packageName. This does not seem 
> to cause any problems as AndroidManifest.xml references the 
> android-packageName value.



--
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-9842) cordova-common missing when adding Android on OS X

[Vladimir Kotikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Kotikov resolved CB-9842.
--
Resolution: Cannot Reproduce

> cordova-common missing when adding Android on OS X
> --
>
> Key: CB-9842
> URL: https://issues.apache.org/jira/browse/CB-9842
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Affects Versions: Master
> Environment: OS X
>Reporter: Dmitry Blotsky
>Assignee: Vladimir Kotikov
>Priority: Critical
>  Labels: android, cordova-common, found-by-ci
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This build failed: 
> https://ci.apache.org/builders/cordova-android-osx/builds/713/. Steps to 
> reproduce the bug (assuming local install of everything from master after 
> running {{npm link}}):
> {noformat}
> ./bin/cordova create foobar
> cd foobar
> ../bin/cordova platform add ../cordova-android
> {noformat}
> Error:
> {noformat}
> Error: Cannot find module 'cordova-common'
> at Function.Module._resolveFilename (module.js:336:15)
> at Function.Module._load (module.js:278:25)
> at Module.require (module.js:365:17)
> at require (module.js:384:17)
> at Object. 
> (/Users/buildbot/slaves/apache/cordova-android-osx/mobilespec/platforms/android/cordova/lib/Adb.js:4:14)
> at Module._compile (module.js:460:26)
> at Object.Module._extensions..js (module.js:478:10)
> at Module.load (module.js:355:32)
> at Function.Module._load (module.js:310:12)
> at Module.require (module.js:365:17)
> {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] [Commented] (CB-9842) cordova-common missing when adding Android on OS X

[Vladimir Kotikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969806#comment-14969806
 ] 

Vladimir Kotikov commented on CB-9842:
--

I can’t reproduce this neither using ‘createmobilespec’ script nor using the 
steps from JIRA. Tried this on two Mac machines.

>From what I see from stdio output, the following chain fails:
  Create.js:129  require(path.join(projectPath, 'cordova/lib/build'))
  Build.js:27  require('./Adb');
  Adb.js:4  require('cordova-common').events

I suspect that something is going wrong when `node_modules` is copied into 
platform’s ‘cordova’ directory, and in particular linked cordova-common doesn’t 
copied properly, but I can’t confirm this without access to osx slave.


> cordova-common missing when adding Android on OS X
> --
>
> Key: CB-9842
> URL: https://issues.apache.org/jira/browse/CB-9842
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Affects Versions: Master
> Environment: OS X
>Reporter: Dmitry Blotsky
>Assignee: Vladimir Kotikov
>Priority: Critical
>  Labels: android, cordova-common, found-by-ci
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This build failed: 
> https://ci.apache.org/builders/cordova-android-osx/builds/713/. Steps to 
> reproduce the bug (assuming local install of everything from master after 
> running {{npm link}}):
> {noformat}
> ./bin/cordova create foobar
> cd foobar
> ../bin/cordova platform add ../cordova-android
> {noformat}
> Error:
> {noformat}
> Error: Cannot find module 'cordova-common'
> at Function.Module._resolveFilename (module.js:336:15)
> at Function.Module._load (module.js:278:25)
> at Module.require (module.js:365:17)
> at require (module.js:384:17)
> at Object. 
> (/Users/buildbot/slaves/apache/cordova-android-osx/mobilespec/platforms/android/cordova/lib/Adb.js:4:14)
> at Module._compile (module.js:460:26)
> at Object.Module._extensions..js (module.js:478:10)
> at Module.load (module.js:355:32)
> at Function.Module._load (module.js:310:12)
> at Module.require (module.js:365:17)
> {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] [Commented] (CB-9782) Implement and expose PlatformApi for Android

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969795#comment-14969795
 ] 

ASF subversion and git services commented on CB-9782:
-

Commit 8c7130608c5194e2dd446f27361894ac27145e3a in cordova-coho's branch 
refs/heads/master from [~vladimir.kotikov]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=8c71306 ]

CB-9782 Partially reverts a214d55 npm-link support for cordova-android

Removes npm link validation for cordova-common -> cordova-android


> Implement and expose PlatformApi for Android
> 
>
> Key: CB-9782
> URL: https://issues.apache.org/jira/browse/CB-9782
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Android
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> 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] [Commented] (CB-9846) Plugins declared in the config.xml aren't listed on cordova plugin ls command

[Steve Gill (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969625#comment-14969625
 ] 

Steve Gill commented on CB-9846:


We don't use npm install to install plugins. Our dependency structure doesn't 
allow this.

If you look at package.json of that repo, you won't see any plugins listed. 

Plugins need to be installed. Couple ways to do this

1) Manually install them `cordova plugin add PackageName`
2) restore them from config.xml. `cordova prepare` does this. Adding a platform 
a platform also runs cordova prepare. cordova build also runs cordova prepare. 
If you have platforms listed in config.xml, cordova prepare would add those 
platforms as well. 




> Plugins declared in the config.xml aren't listed on cordova plugin ls command
> -
>
> Key: CB-9846
> URL: https://issues.apache.org/jira/browse/CB-9846
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CLI
>Affects Versions: 5.3.2
> Environment: Windows 10 Entreprise
>Reporter: Diego Geffner
>
> The plugins that appear on the config.xml file, but are not yet installed, 
> aren't listed on plugin ls command output.
> For example, if you get: this app https://github.com/thinkmill/reacteu-app , 
> and do:
> npm install
> npm run build
> and you do cordova plugin ls you get no plugins
> then if you add, cordova platform add android it says that it discovers the 
> plugins, and after that if you do again cordova plugin ls  you'll see the 
> list of plugins.  
> I think this behavior is confusing.



--
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-9846) Plugins declared in the config.xml aren't listed on cordova plugin ls command

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill reassigned CB-9846:
--

Assignee: Steve Gill

> Plugins declared in the config.xml aren't listed on cordova plugin ls command
> -
>
> Key: CB-9846
> URL: https://issues.apache.org/jira/browse/CB-9846
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CLI
>Affects Versions: 5.3.2
> Environment: Windows 10 Entreprise
>Reporter: Diego Geffner
>Assignee: Steve Gill
>
> The plugins that appear on the config.xml file, but are not yet installed, 
> aren't listed on plugin ls command output.
> For example, if you get: this app https://github.com/thinkmill/reacteu-app , 
> and do:
> npm install
> npm run build
> and you do cordova plugin ls you get no plugins
> then if you add, cordova platform add android it says that it discovers the 
> plugins, and after that if you do again cordova plugin ls  you'll see the 
> list of plugins.  
> I think this behavior is confusing.



--
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-9846) Plugins declared in the config.xml aren't listed on cordova plugin ls command

[Steve Gill (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Gill resolved CB-9846.

Resolution: Not A Problem

> Plugins declared in the config.xml aren't listed on cordova plugin ls command
> -
>
> Key: CB-9846
> URL: https://issues.apache.org/jira/browse/CB-9846
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CLI
>Affects Versions: 5.3.2
> Environment: Windows 10 Entreprise
>Reporter: Diego Geffner
>
> The plugins that appear on the config.xml file, but are not yet installed, 
> aren't listed on plugin ls command output.
> For example, if you get: this app https://github.com/thinkmill/reacteu-app , 
> and do:
> npm install
> npm run build
> and you do cordova plugin ls you get no plugins
> then if you add, cordova platform add android it says that it discovers the 
> plugins, and after that if you do again cordova plugin ls  you'll see the 
> list of plugins.  
> I think this behavior is confusing.



--
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-9847) Cannot tell when running on Simulator

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969559#comment-14969559
 ] 

ASF GitHub Bot commented on CB-9847:


Github user purplecabbage commented on the pull request:


https://github.com/apache/cordova-plugin-device/pull/35#issuecomment-150307876
  
Created an issue for this here: CB-9847
Moving forward with `isVirtual`


> Cannot tell when running on Simulator
> -
>
> Key: CB-9847
> URL: https://issues.apache.org/jira/browse/CB-9847
> Project: Apache Cordova
>  Issue Type: Improvement
>Reporter: Jesse MacFadyen
>Assignee: Jesse MacFadyen
>
> There are times where things simply won't work when we are running on the 
> simulator.  For example, if you are using the device-motion api you will 
> simply never receive a result when calling `getCurrentAcceleration`
> It would be nice if we could tell before the call if this is the case, and 
> avoid waiting for a result.
> Prior art in https://github.com/apache/cordova-plugin-device/pull/35



--
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-9847) Cannot tell when running on Simulator

[Jesse MacFadyen (JIRA)]

Jesse MacFadyen created CB-9847:
---

 Summary: Cannot tell when running on Simulator
 Key: CB-9847
 URL: https://issues.apache.org/jira/browse/CB-9847
 Project: Apache Cordova
  Issue Type: Improvement
Reporter: Jesse MacFadyen
Assignee: Jesse MacFadyen


There are times where things simply won't work when we are running on the 
simulator.  For example, if you are using the device-motion api you will simply 
never receive a result when calling `getCurrentAcceleration`

It would be nice if we could tell before the call if this is the case, and 
avoid waiting for a result.

Prior art in https://github.com/apache/cordova-plugin-device/pull/35



--
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-9846) Plugins declared in the config.xml aren't listed on cordova plugin ls command

[Diego Geffner (JIRA)]

Diego Geffner created CB-9846:
-

 Summary: Plugins declared in the config.xml aren't listed on 
cordova plugin ls command
 Key: CB-9846
 URL: https://issues.apache.org/jira/browse/CB-9846
 Project: Apache Cordova
  Issue Type: Bug
  Components: CLI
Affects Versions: 5.3.2
 Environment: Windows 10 Entreprise
Reporter: Diego Geffner


The plugins that appear on the config.xml file, but are not yet installed, 
aren't listed on plugin ls command output.

For example, if you get: this app https://github.com/thinkmill/reacteu-app , 
and do:
npm install
npm run build

and you do cordova plugin ls you get no plugins
then if you add, cordova platform add android it says that it discovers the 
plugins, and after that if you do again cordova plugin ls  you'll see the list 
of plugins.  

I think this behavior is confusing.



--
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-9845) inappbrowser close function not working as intended, leaving instance of inappbrowser running

[Sebastian Betzinger (JIRA)]

Sebastian Betzinger created CB-9845:
---

 Summary: inappbrowser close function not working as intended, 
leaving instance of inappbrowser running
 Key: CB-9845
 URL: https://issues.apache.org/jira/browse/CB-9845
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.5.0, Master
 Environment: Mac OSX/Win10/Ubuntu14.04
Reporter: Sebastian Betzinger
Priority: Critical


Code of index.js:

var ref;

function xy() {
ref = cordova.InAppBrowser.open(...);
}

function ab() {
ref.close();
xy();
}

ab();


InAppBrowser instance stays opened with url "about:blank" in foreground and a 
second instance of InAppBrowser is launched in background.

Should be: instance of InAppBrowser should be purged and closed instead of 
being held with "about:blank"



--
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-7838) Contact Picker returns -1 as the id for all contacts

[Matus P (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969314#comment-14969314
 ] 

Matus P commented on CB-7838:
-

Hi. I've found this problem on both (device and simulator). The problem is, 
that native contacts picker is not asking user to grant permissions to access 
address book. And it's seems, that because of it contact ID is set to -1 value. 
So I changed iOS code to this in file CDVContacts.m for method 
(void)chooseContact: ((CDVInvokedUrlCommand*)command:
{code}
NSString* callbackId = command.callbackId;
CDVAddressBookHelper* abHelper = [[CDVAddressBookHelper alloc] init];
CDVContacts* __weak weakSelf = self; // play it safe to avoid retain 
cycles
// it gets uglier, block within block.
[abHelper createAddressBook: ^(ABAddressBookRef addrBook, 
CDVAddressBookAccessError* errCode) {
if (addrBook == NULL) {
// permission was denied or other error - return error
CDVPluginResult* result = [CDVPluginResult 
resultWithStatus:CDVCommandStatus_ERROR messageToErrorObject:errCode ? 
(int)errCode.errorCode:UNKNOWN_ERROR];
[weakSelf.commandDelegate sendPluginResult:result 
callbackId:callbackId];
return;
}

/// HERE IS THE CURRENT CODE OF METHOD ///

}];
{code}

After applying, it asks for permissions first time I want to pick a Contact.

> Contact Picker returns -1 as the id for all contacts
> 
>
> Key: CB-7838
> URL: https://issues.apache.org/jira/browse/CB-7838
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Contacts
>Affects Versions: 3.5.0
> Environment: iOS
>Reporter: Ralph S Theart
>
> Can anyone confirm that the contacts plug-in returns -1 for any contact id 
> return from a device but it on the simulator returns a valid unique ID? 
> Its strange..I have ios8 devices that return -1 for any contact picked...but 
> the same action on the simulators returns a positive integer.
> {code:title=From iOS 8 Device|borderStyle=solid}
> {
>   "id": -1,
>   "rawId": null,
>   "displayName": null,
>   "name": {
> "givenName": "Aunte",
> "formatted": "Aunte Aline",
> "middleName": null,
> "familyName": "Aline",
> "honorificPrefix": null,
> "honorificSuffix": null
>   },
>   "nickname": null,
>   "phoneNumbers": [
> {
>   "type": "other",
>   "value": "01141223***",
>   "id": 0,
>   "pref": false
> }
>   ],
>   "emails": [
> {
>   "type": "home",
>   "value": "vito.**@bluewin.ch",
>   "id": 0,
>   "pref": false
> }
>   ],.
> {code}
> {code:title=From ios-sim}
> {
>   "id": 7,
>   "rawId": null,
>   "displayName": null,
>   "name": {
> "givenName": "Test",
> "formatted": "Test",
> "middleName": null,
> "familyName": null,
> "honorificPrefix": null,
> "honorificSuffix": null
>   },
>   "nickname": null,
>   "phoneNumbers": [
> {
>   "type": "home",
>   "value": "(954)\u00a0646-7923",
>   "id": 0,
>   "pref": false
> }
>   ],
>   "emails": null,
>   "addresses": null,
>   "ims": null,
>   "organizations": null,
>   "birthday": null,
>   "note": null,
>   "photos": null,
>   "categories": null,
>   "urls": null
> }
> {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] [Updated] (CB-9844) 2 main activities are generated when android package name is specified

[Gorkem ERCAN (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gorkem ERCAN updated CB-9844:
-
Priority: Minor  (was: Major)

> 2 main activities are generated when android package name is specified
> --
>
> Key: CB-9844
> URL: https://issues.apache.org/jira/browse/CB-9844
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Affects Versions: 5.0.0
>Reporter: Gorkem ERCAN
>Assignee: Gorkem ERCAN
>Priority: Minor
>
> If android-packageName is specified on the config.xml two main activity 
> classes are generated. One with with the package name as specified on id 
> attribute and one with the value of android-packageName. This is because the 
> old package name is not removed when the new one is generated [1]. 
> This has been fixed for Cordova CLI but needs to be fixed on Android because 
> the logic has moved.
> [1] 
> https://github.com/apache/cordova-android/blob/master/bin/templates/cordova/lib/prepare.js#L156



--
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-9736) 2 main activities are generated when a package name is specified

[Gorkem ERCAN (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gorkem ERCAN resolved CB-9736.
--
Resolution: Fixed

> 2 main activities are generated when a package name is specified
> 
>
> Key: CB-9736
> URL: https://issues.apache.org/jira/browse/CB-9736
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 3.5.0
>Reporter: Gorkem ERCAN
>Assignee: Gorkem ERCAN
>Priority: Minor
>
> If android-packageName is specified on the config.xml two main activity 
> classes are generated. One with with the package name as specified on id 
> attribute and one with the value of android-packageName. This does not seem 
> to cause any problems as AndroidManifest.xml references the 
> android-packageName value.



--
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-9844) 2 main activities are generated when android package name is specified

[Gorkem ERCAN (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gorkem ERCAN reassigned CB-9844:


Assignee: Gorkem ERCAN

> 2 main activities are generated when android package name is specified
> --
>
> Key: CB-9844
> URL: https://issues.apache.org/jira/browse/CB-9844
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Affects Versions: 5.0.0
>Reporter: Gorkem ERCAN
>Assignee: Gorkem ERCAN
>
> If android-packageName is specified on the config.xml two main activity 
> classes are generated. One with with the package name as specified on id 
> attribute and one with the value of android-packageName. This is because the 
> old package name is not removed when the new one is generated [1]. 
> This has been fixed for Cordova CLI but needs to be fixed on Android because 
> the logic has moved.
> [1] 
> https://github.com/apache/cordova-android/blob/master/bin/templates/cordova/lib/prepare.js#L156



--
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-9844) 2 main activities are generated when android package name is specified

[Gorkem ERCAN (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gorkem ERCAN updated CB-9844:
-
Description: 
If android-packageName is specified on the config.xml two main activity classes 
are generated. One with with the package name as specified on id attribute and 
one with the value of android-packageName. This is because the old package name 
is not removed when the new one is generated [1]. 

This has been fixed for Cordova CLI but needs to be fixed on Android because 
the logic has moved.

[1] 
https://github.com/apache/cordova-android/blob/master/bin/templates/cordova/lib/prepare.js#L156

> 2 main activities are generated when android package name is specified
> --
>
> Key: CB-9844
> URL: https://issues.apache.org/jira/browse/CB-9844
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Affects Versions: 5.0.0
>Reporter: Gorkem ERCAN
>
> If android-packageName is specified on the config.xml two main activity 
> classes are generated. One with with the package name as specified on id 
> attribute and one with the value of android-packageName. This is because the 
> old package name is not removed when the new one is generated [1]. 
> This has been fixed for Cordova CLI but needs to be fixed on Android because 
> the logic has moved.
> [1] 
> https://github.com/apache/cordova-android/blob/master/bin/templates/cordova/lib/prepare.js#L156



--
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-9844) 2 main activities are generated when android package name is specified

[Gorkem ERCAN (JIRA)]

Gorkem ERCAN created CB-9844:


 Summary: 2 main activities are generated when android package name 
is specified
 Key: CB-9844
 URL: https://issues.apache.org/jira/browse/CB-9844
 Project: Apache Cordova
  Issue Type: Bug
  Components: Android
Affects Versions: 5.0.0
Reporter: Gorkem ERCAN






--
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-9736) 2 main activities are generated when a package name is specified

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969222#comment-14969222
 ] 

ASF subversion and git services commented on CB-9736:
-

Commit 071eccd7eb33b61fe9dd706dfb520de10bfcfc83 in cordova-lib's branch 
refs/heads/master from [~gercan]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=071eccd ]

CB-9736 - Extra main activity generated when an android package name is 
specified

Removes the old package name after the new one is created. If the package
name is different


> 2 main activities are generated when a package name is specified
> 
>
> Key: CB-9736
> URL: https://issues.apache.org/jira/browse/CB-9736
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 3.5.0
>Reporter: Gorkem ERCAN
>Assignee: Gorkem ERCAN
>Priority: Minor
>
> If android-packageName is specified on the config.xml two main activity 
> classes are generated. One with with the package name as specified on id 
> attribute and one with the value of android-packageName. This does not seem 
> to cause any problems as AndroidManifest.xml references the 
> android-packageName value.



--
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-9736) 2 main activities are generated when a package name is specified

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969224#comment-14969224
 ] 

ASF GitHub Bot commented on CB-9736:


Github user asfgit closed the pull request at:

https://github.com/apache/cordova-lib/pull/328


> 2 main activities are generated when a package name is specified
> 
>
> Key: CB-9736
> URL: https://issues.apache.org/jira/browse/CB-9736
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 3.5.0
>Reporter: Gorkem ERCAN
>Assignee: Gorkem ERCAN
>Priority: Minor
>
> If android-packageName is specified on the config.xml two main activity 
> classes are generated. One with with the package name as specified on id 
> attribute and one with the value of android-packageName. This does not seem 
> to cause any problems as AndroidManifest.xml references the 
> android-packageName value.



--
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-9835) Cordova-android fails to install some plugins due to errors in properties-parser

[Vladimir Kotikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Kotikov updated CB-9835:
-
Environment: NodeJS@<4.x  (was: NodeJS@>=4.x)

> Cordova-android fails to install some plugins due to errors in 
> properties-parser
> 
>
> Key: CB-9835
> URL: https://issues.apache.org/jira/browse/CB-9835
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Affects Versions: Master
> Environment: NodeJS@<4.x
>Reporter: Vladimir Kotikov
>Assignee: Alexander Sorokin
>Priority: Blocker
>  Labels: android, properties-parser
> Fix For: Master
>
>
> As per [~TimBarham]'s comment here: 
> https://github.com/apache/cordova-android/commit/400282282f21c07bda5527e4c2266810fe01da3f#commitcomment-13890057
>  the issue is caused by {{properties-parser}} module.
> As a solution, we need to downgrade {{properties-parser}} to 0.2.3 which 
> works fine in all node versions starting from 0.10



--
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-9769) Application modifying the autolayout engine from a background thread causes crash on keyboard focus

[jcesarmobile (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969195#comment-14969195
 ] 

jcesarmobile commented on CB-9769:
--

are you using any 3rd party keyboard when you receive this error?

Can you explain or provide code for "textbox within a form"? it's a regular 
input type text? textarea?

> Application modifying the autolayout engine from a background thread causes 
> crash on keyboard focus
> ---
>
> Key: CB-9769
> URL: https://issues.apache.org/jira/browse/CB-9769
> Project: Apache Cordova
>  Issue Type: Bug
>Reporter: Ryan England
>
> Hi there,
> We're getting issues when keyboard focus is given to a textbox within a form. 
> Upon clicking the form field, the entire app immediately crashes and the 
> following information is displayed in Xcode:
> 2015-10-08 18:47:49.092 BudiPay[527:113011] This application is modifying the 
> autolayout engine from a background thread, which can lead to engine 
> corruption and weird crashes.  This will cause an exception in a future 
> release.
>  Stack:(
>   0   CoreFoundation  0x000184608f74  + 
> 148
>   1   libobjc.A.dylib 0x000199af7f80 
> objc_exception_throw + 56
>   2   CoreFoundation  0x000184608ea4  + > 0
>   3   Foundation  0x0001856225d8  + 
> 88
>   4   Foundation  0x0001854a4a1c  + 
> 36
>   5   UIKit   0x000189c6393c  + 
> 64
>   6   UIKit   0x000189c64454  + 
> 244
>   7   UIKit   0x000189c80f28  + 
> 108
>   8   UIKit   0x00018a38a77c  + 
> 268
>   9   UIKit   0x000189e61fb0  + 
> 176
>   10  UIKit   0x000189e51098  + 
> 52
>   11  UIKit   0x000189b5aff0  + 
> 644
>   12  QuartzCore  0x000189361f14  + 
> 148
>   13  QuartzCore  0x00018935cb20  + 
> 292
>   14  QuartzCore  0x00018935c9e0  + 
> 32
>   15  QuartzCore  0x00018935c07c  + 
> 252
>   16  QuartzCore  0x00018935bdd0  + 
> 516
>   17  QuartzCore  0x0001893aeb00  + 
> 592
>   18  IOKit   0x000185896018 
> IODispatchCalloutFromCFMessage + 372
>   19  CoreFoundation  0x0001845aa8e0  + 
> 180
>   20  CoreFoundation  0x0001845c0cdc  + 
> 56
>   21  CoreFoundation  0x0001845c0414  + 
> 436
>   22  CoreFoundation  0x0001845be16c  + 
> 1800
>   23  CoreFoundation  0x0001844ecdc0 
> CFRunLoopRunSpecific + 384
>   24  WebCore 0x000196a25aa0  + 
> 456
>   25  libsystem_pthread.dylib 0x00019a4fbb3c  + 
> 156
>   26  libsystem_pthread.dylib 0x00019a4fbaa0  + > 0
>   27  libsystem_pthread.dylib 0x00019a4f9030 thread_start 
> + 4
> )
> 2015-10-08 18:47:49.096 BudiPay[527:113011] This application is modifying the 
> autolayout engine from a background thread, which can lead to engine 
> corruption and weird crashes.  This will cause an exception in a future 
> release.
>  Stack:(
>   0   CoreFoundation  0x000184608f74  + 
> 148
>   1   libobjc.A.dylib 0x000199af7f80 
> objc_exception_throw + 56
>   2   CoreFoundation  0x000184608ea4  + > 0
>   3   Foundation  0x0001856225d8  + 
> 88
>   4   Foundation  0x0001854a8f3c  + 
> 56
>   5   Foundation  0x0001854a4afc  + 
> 260
>   6   UIKit   0x000189c6393c  + 
> 64
>   7   UIKit   0x000189c64454  + 
> 244
>   8   UIKit   0x000189c80f28  + 
> 108
>   9   UIKit   0x00018a38a77c  + 
> 268
>   10  UIKit   0x000189e61fb0  + 
> 176
>   11  UIKit   0x000189e51098  + 
> 52
>   12  UIKit   0x000189b5aff0  + 
> 644
>   13  QuartzCore  0x000189361f14  + 
> 148
>   14  QuartzCore  0x00018935cb20  + 
> 292
>   15  QuartzCore  0x0001893

[jira] [Commented] (CB-9685) A fix for the magnifying glass popping up on iOS9 when longpressing the webview

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968992#comment-14968992
 ] 

ASF GitHub Bot commented on CB-9685:


Github user EddyVerbruggen commented on the pull request:

https://github.com/apache/cordova-ios/pull/164#issuecomment-150191011
  
BTW I am seeing it on 9.1. iPhone 6S, longpress and 3D Touch.


> A fix for the magnifying glass popping up on iOS9 when longpressing the 
> webview
> ---
>
> Key: CB-9685
> URL: https://issues.apache.org/jira/browse/CB-9685
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaLib, iOS
>Reporter: Eddy Verbruggen
>Assignee: Shazron Abdullah
>  Labels: cordova-ios-4.0.x
>
> When pressing the webview for 500ms on iOS9 a magnification glass pops up. On 
> UIWebView the popup is always at the top of the page (see the screenshot in 
> the readme here: 
> https://github.com/EddyVerbruggen/cordova-plugin-ios-longpress-fix), on 
> WKWebView the popup is where your finger is.
> On UIWebView we have yet to find a non-native way (read: CSS) to fix the 
> problem, but on WKWebView a few lines of CSS seem to fix the issue.
> This improvement is aimed at resolving the problem for UIWebView. There is no 
> reason not to include a fix for WKWebView as well, other than I didn't invest 
> time in it because of the CSS workaround.



--
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-9685) A fix for the magnifying glass popping up on iOS9 when longpressing the webview

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968988#comment-14968988
 ] 

ASF GitHub Bot commented on CB-9685:


Github user jcesarmobile commented on the pull request:

https://github.com/apache/cordova-ios/pull/164#issuecomment-150188723
  
+1 for preference

BTW, I'm not able to reproduce the magnifier glass issue on iOS 9.1, maybe 
apple fixed it?


> A fix for the magnifying glass popping up on iOS9 when longpressing the 
> webview
> ---
>
> Key: CB-9685
> URL: https://issues.apache.org/jira/browse/CB-9685
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaLib, iOS
>Reporter: Eddy Verbruggen
>Assignee: Shazron Abdullah
>  Labels: cordova-ios-4.0.x
>
> When pressing the webview for 500ms on iOS9 a magnification glass pops up. On 
> UIWebView the popup is always at the top of the page (see the screenshot in 
> the readme here: 
> https://github.com/EddyVerbruggen/cordova-plugin-ios-longpress-fix), on 
> WKWebView the popup is where your finger is.
> On UIWebView we have yet to find a non-native way (read: CSS) to fix the 
> problem, but on WKWebView a few lines of CSS seem to fix the issue.
> This improvement is aimed at resolving the problem for UIWebView. There is no 
> reason not to include a fix for WKWebView as well, other than I didn't invest 
> time in it because of the CSS workaround.



--
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-9685) A fix for the magnifying glass popping up on iOS9 when longpressing the webview

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968982#comment-14968982
 ] 

ASF GitHub Bot commented on CB-9685:


Github user zhangjianying commented on the pull request:

https://github.com/apache/cordova-ios/pull/164#issuecomment-150184839
  
good idea. thinks


> A fix for the magnifying glass popping up on iOS9 when longpressing the 
> webview
> ---
>
> Key: CB-9685
> URL: https://issues.apache.org/jira/browse/CB-9685
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaLib, iOS
>Reporter: Eddy Verbruggen
>Assignee: Shazron Abdullah
>  Labels: cordova-ios-4.0.x
>
> When pressing the webview for 500ms on iOS9 a magnification glass pops up. On 
> UIWebView the popup is always at the top of the page (see the screenshot in 
> the readme here: 
> https://github.com/EddyVerbruggen/cordova-plugin-ios-longpress-fix), on 
> WKWebView the popup is where your finger is.
> On UIWebView we have yet to find a non-native way (read: CSS) to fix the 
> problem, but on WKWebView a few lines of CSS seem to fix the issue.
> This improvement is aimed at resolving the problem for UIWebView. There is no 
> reason not to include a fix for WKWebView as well, other than I didn't invest 
> time in it because of the CSS workaround.



--
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-9843) filetransfer.spec.12 failure on wp8

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968959#comment-14968959
 ] 

ASF GitHub Bot commented on CB-9843:


Github user daserge commented on a diff in the pull request:


https://github.com/apache/cordova-plugin-file-transfer/pull/106#discussion_r42734873
  
--- Diff: src/wp/FileTransfer.cs ---
@@ -775,11 +775,8 @@ private void downloadCallback(IAsyncResult 
asynchronousResult)
 }
 catch (WebException webex)
 {
-// TODO: probably need better work here to properly 
respond with all http status codes back to JS
-// Right now am jumping through hoops just to detect 404.
 HttpWebResponse response = (HttpWebResponse)webex.Response;
-if ((webex.Status == WebExceptionStatus.ProtocolError && 
response.StatusCode == HttpStatusCode.NotFound)
-|| webex.Status == WebExceptionStatus.UnknownError)
+if ((webex.Status == WebExceptionStatus.ProtocolError) || 
(webex.Status == WebExceptionStatus.UnknownError))
--- End diff --

Please remove excess brackets.


> filetransfer.spec.12 failure on wp8
> ---
>
> Key: CB-9843
> URL: https://issues.apache.org/jira/browse/CB-9843
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin File Transfer
>Affects Versions: Master
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> There is a file transfer plugin failure on wp8 platform:
> {noformat}
> cordova-plugin-file-transfer-tests.tests >> FileTransfer methods download 
> filetransfer.spec.12 should get http status on failure
> Expected 3 to be 1.
> Error: Expected 3 to be 1.
>at stack 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11)
>at buildExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5)
>at expectationResultFactory 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:572:11)
>at addExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:321:5)
>at addExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:516:9)
>at Anonymous function 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7)
>at downloadFail 
> (x-wmapp0:www/cdvtests/../plugins/cordova-plugin-file-transfer-tests/tests.js:507:25)
>at errorCallback 
> (x-wmapp0:www/cdvtests/../plugins/cordova-plugin-file-transfer/www/FileTransfer.js:221:9)
>at callbackFromNative 
> (x-wmapp0:www/cdvtests/../cordova.js:295:38)
>at callbackError (x-wmapp0:www/cdvtests/../cordova.js:282:9)
> {noformat}
> wp8 platform does not make a difference between 404 and unknown host so the 
> plugin returns CONNECTION_ERR and not FILE_NOT_FOUND_ERR



--
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-9843) filetransfer.spec.12 failure on wp8

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968951#comment-14968951
 ] 

ASF GitHub Bot commented on CB-9843:


GitHub user alsorokin opened a pull request:

https://github.com/apache/cordova-plugin-file-transfer/pull/106

CB-9843 Added wp8 quirk to test spec 15

https://issues.apache.org/jira/browse/CB-9843

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-plugin-file-transfer 
CB-9843

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-file-transfer/pull/106.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 #106


commit b1f034f01b6ab02b6514084ae4c90c7f66b7fd00
Author: Alexander Sorokin 
Date:   2015-10-22T10:49:55Z

CB-9843 Added wp8 quirk to test spec 15




> filetransfer.spec.12 failure on wp8
> ---
>
> Key: CB-9843
> URL: https://issues.apache.org/jira/browse/CB-9843
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin File Transfer
>Affects Versions: Master
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> There is a file transfer plugin failure on wp8 platform:
> {noformat}
> cordova-plugin-file-transfer-tests.tests >> FileTransfer methods download 
> filetransfer.spec.12 should get http status on failure
> Expected 3 to be 1.
> Error: Expected 3 to be 1.
>at stack 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11)
>at buildExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5)
>at expectationResultFactory 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:572:11)
>at addExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:321:5)
>at addExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:516:9)
>at Anonymous function 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7)
>at downloadFail 
> (x-wmapp0:www/cdvtests/../plugins/cordova-plugin-file-transfer-tests/tests.js:507:25)
>at errorCallback 
> (x-wmapp0:www/cdvtests/../plugins/cordova-plugin-file-transfer/www/FileTransfer.js:221:9)
>at callbackFromNative 
> (x-wmapp0:www/cdvtests/../cordova.js:295:38)
>at callbackError (x-wmapp0:www/cdvtests/../cordova.js:282:9)
> {noformat}
> wp8 platform does not make a difference between 404 and unknown host so the 
> plugin returns CONNECTION_ERR and not FILE_NOT_FOUND_ERR



--
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-9843) filetransfer.spec.12 failure on wp8

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968949#comment-14968949
 ] 

ASF GitHub Bot commented on CB-9843:


Github user alsorokin closed the pull request at:

https://github.com/apache/cordova-plugin-file-transfer/pull/105


> filetransfer.spec.12 failure on wp8
> ---
>
> Key: CB-9843
> URL: https://issues.apache.org/jira/browse/CB-9843
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin File Transfer
>Affects Versions: Master
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> There is a file transfer plugin failure on wp8 platform:
> {noformat}
> cordova-plugin-file-transfer-tests.tests >> FileTransfer methods download 
> filetransfer.spec.12 should get http status on failure
> Expected 3 to be 1.
> Error: Expected 3 to be 1.
>at stack 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11)
>at buildExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5)
>at expectationResultFactory 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:572:11)
>at addExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:321:5)
>at addExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:516:9)
>at Anonymous function 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7)
>at downloadFail 
> (x-wmapp0:www/cdvtests/../plugins/cordova-plugin-file-transfer-tests/tests.js:507:25)
>at errorCallback 
> (x-wmapp0:www/cdvtests/../plugins/cordova-plugin-file-transfer/www/FileTransfer.js:221:9)
>at callbackFromNative 
> (x-wmapp0:www/cdvtests/../cordova.js:295:38)
>at callbackError (x-wmapp0:www/cdvtests/../cordova.js:282:9)
> {noformat}
> wp8 platform does not make a difference between 404 and unknown host so the 
> plugin returns CONNECTION_ERR and not FILE_NOT_FOUND_ERR



--
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-9843) filetransfer.spec.12 failure on wp8

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968945#comment-14968945
 ] 

ASF GitHub Bot commented on CB-9843:


GitHub user alsorokin opened a pull request:

https://github.com/apache/cordova-plugin-file-transfer/pull/105

CB-9843 Added wp8 quirk to test spec 12

https://issues.apache.org/jira/browse/CB-9843

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-plugin-file-transfer 
CB-9843

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-file-transfer/pull/105.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 #105


commit d6b480c95e2665e1aaa5fa5b01c4cb31958b3f68
Author: Alexander Sorokin 
Date:   2015-10-22T10:14:03Z

CB-9843 Added wp8 quirk to test spec 12




> filetransfer.spec.12 failure on wp8
> ---
>
> Key: CB-9843
> URL: https://issues.apache.org/jira/browse/CB-9843
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin File Transfer
>Affects Versions: Master
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> There is a file transfer plugin failure on wp8 platform:
> {noformat}
> cordova-plugin-file-transfer-tests.tests >> FileTransfer methods download 
> filetransfer.spec.12 should get http status on failure
> Expected 3 to be 1.
> Error: Expected 3 to be 1.
>at stack 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11)
>at buildExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5)
>at expectationResultFactory 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:572:11)
>at addExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:321:5)
>at addExpectationResult 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:516:9)
>at Anonymous function 
> (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7)
>at downloadFail 
> (x-wmapp0:www/cdvtests/../plugins/cordova-plugin-file-transfer-tests/tests.js:507:25)
>at errorCallback 
> (x-wmapp0:www/cdvtests/../plugins/cordova-plugin-file-transfer/www/FileTransfer.js:221:9)
>at callbackFromNative 
> (x-wmapp0:www/cdvtests/../cordova.js:295:38)
>at callbackError (x-wmapp0:www/cdvtests/../cordova.js:282:9)
> {noformat}
> wp8 platform does not make a difference between 404 and unknown host so the 
> plugin returns CONNECTION_ERR and not FILE_NOT_FOUND_ERR



--
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-9685) A fix for the magnifying glass popping up on iOS9 when longpressing the webview

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-9685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968909#comment-14968909
 ] 

ASF GitHub Bot commented on CB-9685:


Github user EddyVerbruggen commented on the pull request:

https://github.com/apache/cordova-ios/pull/164#issuecomment-150170110
  
I think I'll be adding a configuration for this to config.xml as not all 
folks may like this feature (new PR).

The plugin that inspired this PR has been around for a few weeks now: 
https://github.com/EddyVerbruggen/cordova-plugin-ios-longpress-fix and while 
most like it, it may break text selection. If your app needs that this feature 
will cause trouble.

I propose enabling this private plugin only when a certain config.xml 
property has been enabled.

And I'd also like to add a feature to suppress the magnifying glass for 
devices with 3D Touch support. In the plugin mentioned above I've already done 
so, by specifying a preference: ``.

Any thoughts others want to share perhaps?


> A fix for the magnifying glass popping up on iOS9 when longpressing the 
> webview
> ---
>
> Key: CB-9685
> URL: https://issues.apache.org/jira/browse/CB-9685
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaLib, iOS
>Reporter: Eddy Verbruggen
>Assignee: Shazron Abdullah
>  Labels: cordova-ios-4.0.x
>
> When pressing the webview for 500ms on iOS9 a magnification glass pops up. On 
> UIWebView the popup is always at the top of the page (see the screenshot in 
> the readme here: 
> https://github.com/EddyVerbruggen/cordova-plugin-ios-longpress-fix), on 
> WKWebView the popup is where your finger is.
> On UIWebView we have yet to find a non-native way (read: CSS) to fix the 
> problem, but on WKWebView a few lines of CSS seem to fix the issue.
> This improvement is aimed at resolving the problem for UIWebView. There is no 
> reason not to include a fix for WKWebView as well, other than I didn't invest 
> time in it because of the CSS workaround.



--
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-9843) filetransfer.spec.12 failure on wp8

[Alexander Sorokin (JIRA)]

Alexander Sorokin created CB-9843:
-

 Summary: filetransfer.spec.12 failure on wp8
 Key: CB-9843
 URL: https://issues.apache.org/jira/browse/CB-9843
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File Transfer
Affects Versions: Master
Reporter: Alexander Sorokin
Assignee: Alexander Sorokin


There is a file transfer plugin failure on wp8 platform:
{noformat}
cordova-plugin-file-transfer-tests.tests >> FileTransfer methods download 
filetransfer.spec.12 should get http status on failure
Expected 3 to be 1.
Error: Expected 3 to be 1.
   at stack (x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11)
   at buildExpectationResult 
(x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5)
   at expectationResultFactory 
(x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:572:11)
   at addExpectationResult 
(x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:321:5)
   at addExpectationResult 
(x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:516:9)
   at Anonymous function 
(x-wmapp0:www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7)
   at downloadFail 
(x-wmapp0:www/cdvtests/../plugins/cordova-plugin-file-transfer-tests/tests.js:507:25)
   at errorCallback 
(x-wmapp0:www/cdvtests/../plugins/cordova-plugin-file-transfer/www/FileTransfer.js:221:9)
   at callbackFromNative 
(x-wmapp0:www/cdvtests/../cordova.js:295:38)
   at callbackError (x-wmapp0:www/cdvtests/../cordova.js:282:9)
{noformat}
wp8 platform does not make a difference between 404 and unknown host so the 
plugin returns CONNECTION_ERR and not FILE_NOT_FOUND_ERR



--
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-8973) Mobile-spec: Can't see tests behind the console when running auto or manual tests

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-8973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968835#comment-14968835
 ] 

ASF GitHub Bot commented on CB-8973:


GitHub user daserge opened a pull request:

https://github.com/apache/cordova-plugin-test-framework/pull/15

CB-8973: Changed the functionality of making the log appear and disap…

…pear

Applies the UI fix for wp8 platform

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-plugin-test-framework 
CB-8973-fix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-test-framework/pull/15.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 #15


commit c95392c8bca7af2abe032762a4a7fa0c88654dbe
Author: daserge 
Date:   2015-10-22T08:58:50Z

CB-8973: Changed the functionality of making the log appear and disappear

Applies the UI fix for wp8 platform




> Mobile-spec: Can't see tests behind the console when running auto or manual 
> tests
> -
>
> Key: CB-8973
> URL: https://issues.apache.org/jira/browse/CB-8973
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin TestFramework
>Reporter: Rob Paveza
>Assignee: Rob Paveza
>Priority: Minor
>




--
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