[
https://issues.apache.org/jira/browse/CB-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111014#comment-15111014
]
Jon Akhtar edited comment on CB-10250 at 1/21/16 6:08 PM:
----------------------------------------------------------
There is definitely an issue where an error loading the error page will try to
load the error page in an infinite loop. That is what I have observed. It is
probably a combination of a bug in iOS and a bug in Cordova. I'm of the opinion
that an error loading the error page should not try to load the error page
again, but what the behavior should be I am not sure. Perhaps load the start
page instead - I'm not sure of the best strategy.
The way I caused it was to set up Charles Proxy to proxy the requests in the
simulator, but I "forgot" to install the SSL certificate. This caused an error
accessing the remote site which then tried to load the error page which failed
with a -999 error, and then tried to load the error page again with the same
-999 error, and so on in an infinite loop.
We have the <content/> url directed to a local page which will then load the
remote site. Also we have a local error page, so there is no chance that it
doesn't exist or something like that. In fact it works most of the time.
was (Author: jakhtar):
Does the loop infinitely try to load the remote page or the error page. There
is definitely an issue where an error loading the error page will try to load
the error page in an infinite loop. That is what I have observed.
The way I caused it was to set up Charles Proxy to proxy the requests in the
simulator, but I "forgot" to install the SSL certificate. This caused an error
accessing the remote site which then tried to load the error page which failed
with a -999 error, and then tried to load the error page again with the same
-999 error, and so on in an infinite loop.
We have the <content/> url directed to a local page which will then load the
remote site. Also we have a local error page, so there is no chance that it
doesn't exist or something like that. In fact it works most of the time.
> "NSURLErrorDomain error -999" Infinite Loop Breaks Remote Sites
> ---------------------------------------------------------------
>
> Key: CB-10250
> URL: https://issues.apache.org/jira/browse/CB-10250
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: iOS 9.2
> iPad 2 Emulator
> cordova-ios 4.0.1
> Reporter: vB Results, LLC.
> Priority: Blocker
> Labels: triaged
>
> Whenever I tap a link on a remote site I get the following errors looping
> infinitely in the XCode console when running the emulator.
> The page itself then becomes unresponsive to anything but scrolling, tapping
> a link will underline the link but nothing happens.
> "2015-12-22 21:28:51.931 My Project[50066:507275] Failed to load webpage with
> error: The operation couldn’t be completed. (NSURLErrorDomain error -999.)
> 2015-12-22 21:28:51.932 My Project[50066:507275]
> file:///Users/user900330/Library/Developer/CoreSimulator/Devices/DBFAD775-E311-4A18-BA8A-D5F376404977/data/Containers/Bundle/Application/82A8E42A-397E-4B8B-B609-6FCD6A2D4AAF/My%20Project.app/www/index.html?error=Failed%20to%20load%20webpage%20with%20error:%20The%20operation%20couldn%E2%80%99t%20be%20completed.%20(NSURLErrorDomain%20error%20-999.)
> 2015-12-22 21:28:51.932 My Project[50066:507275] Resetting plugins due to
> page load.
> 2015-12-22 21:28:51.934 My Project[50066:507275] Failed to load webpage with
> error: The operation couldn’t be completed. (NSURLErrorDomain error -999.)"
> Relevant entries in config.xml:
> <content src="http://www.example.com/page.php"; />
> <allow-navigation href="*" />
> <access origin="*" />
> <allow-navigation href="content://*" />
> <allow-navigation href="cdvfile://*" />
> I was experiencing this error on cordova-ios 3.9.2 and it seemed to be fixed
> with 4.0.0. With 4.0.1 it's back!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
