error on line 2 at column 59: SystemLiteral " or ' expected - ios

Question

I am getting such error in my iOS application when I am going to open some web pages using buil-in web view engine (based on Safari but Safari works fine):
This page contains the following errors: error on line 2 at column 59:
SystemLiteral " or ' expected. Below is a rendering of the page up to
the first error.
(nothing is rendered).
The funny thing is that these websites can be opened on iPhone's version of my app but not on iPad.
Looking into the Internet I found hundreds of thousands websites which cannot be handled by google robots - when I search in google:
"59: SystemLiteral " or ' expected"
it lists search results but all found websites' descriptions shows my error. However when I open any of them they are rendering fine on desktop browser and iOS Safari.
Anybody knows what may be the reason of that? Non of websites opened from this google search can be rendered in my app on iPad - all shows the same error.
I also tried debug it using Mac's Safari Developer mode but it does not give any hint.
Update: I prepared a minimal project, added UIWebView controller and it shows the same error.
ViewController.h:
#import <UIKit/UIKit.h>
#interface ViewController : UIViewController
#property (weak, nonatomic) IBOutlet UIWebView *webView;
#end
ViewController.m:
#import "ViewController.h"
#interface ViewController ()
#end
#implementation ViewController
- (void)viewDidLoad
{
[super viewDidLoad];
NSString *fullURL = #"http://catalog.llc.lib.ms.us/polaris/";
NSURL *url = [NSURL URLWithString:fullURL];
NSURLRequest *requestObj = [NSURLRequest requestWithURL:url];
[_webView loadRequest:requestObj];
}
- (void)didReceiveMemoryWarning
{
[super didReceiveMemoryWarning];
}
#end
I also tried few web pages with this code (all from google search I mentioned above), they show also different erros, like "error on line 1077 at column 9: Opening and editing tag mismatch: META line 0 and head." - this comes from http://www.lucindalayton.com/home/?ID=15449 but still they cannot be rendered.

Answer 1

Looking at the response from that web site, it has a blank line at the start of the response, which seemed a little curious. In my first attempt, I trimmed that whitespace:
- (void)viewDidLoad
{
[super viewDidLoad];
NSString *fullURL = #"http://catalog.llc.lib.ms.us/polaris/";
NSURL *url = [NSURL URLWithString:fullURL];
NSURLRequest *request = [NSURLRequest requestWithURL:url];
[NSURLConnection sendAsynchronousRequest:request queue:[NSOperationQueue mainQueue] completionHandler:^(NSURLResponse *response, NSData *data, NSError *connectionError) {
if (!data) {
NSLog(#"%s: sendAsynchronousRequest error: %#", __PRETTY_FUNCTION__, connectionError);
return;
}
NSString *html = [[NSString alloc] initWithData:data encoding:NSUTF8StringEncoding];
html = [html stringByTrimmingCharactersInSet:[NSCharacterSet whitespaceAndNewlineCharacterSet]];
[_webView loadHTMLString:html baseURL:url];
}];
}
But I later noticed that you don't have to trim the whitespace, but rather merely using loadHTMLString seemed to be enough.
I'm unclear as to why Safari handles this properly, as does the iPhone web view, but not the iPad web view. But this seems to get around it.

Answer 2

Rob, thanks from hint but in my case it was something else. I found breakthrough analysing communication between browser and server using some test web page. I will explain it in details:
The problem is related to user agent and mime type.
My application was containing in user agent string, among other things, "Mobile/[somenumber] Safari Version/[someversionnumber]"Some servers are very strict what comes in user agent and for mobile Safari-based browsers are expecting some Safari webkit version so the proper notation should be "Mobile/[somenumber] Safari/[someverionnumber] Version/[someversionnumber]"
Notation affects behavior of the server - it sends different mime type (Content-Type). For websites I mentioned in the qestion when user agent is improper "Content-Type" is set by server to "application/xhtml+xml", but when is proper it is "text/html" which is rendered without any problems. Html code sent in both cases is exactly the same.
Anyway, for me it is still hard to say if it is server site fault, which lets sending "application/xhtml+xml" content type to mobile device, or webkit which should handle such code anyway or very strict user agent notation.