Bug Tracker

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#10513 closed bug (cantfix)

parse error on IOS

Reported by: anonymous Owned by: anonymous
Priority: low Milestone: None
Component: misc Version: 1.6.4
Keywords: Cc:
Blocked by: Blocking:


Im getting a parse error from jquery 1.6.4 on mobile safari since upgrading to IOS5

Change History (14)

comment:1 Changed 11 years ago by addyosmani

Component: unfiledmisc
Owner: set to anonymous
Priority: undecidedlow
Status: newpending

Thanks for submitting a ticket. Could you provide us with more information about the issue? eg. a test case.

Also, are you absolutely sure this isn't related to the network you're using adding further compression to the file? By letting us know what provider you're using we may be able to ascertain this as it's been an issue in the past.

comment:2 Changed 11 years ago by anonymous

Status: pendingnew

I'm having the same problem here.

comment:3 Changed 11 years ago by anonymous

Same problem here, parse error on line 3 in the compressed version of the 1.6.4 release download from the homepage. Also states that the variable $ is undefined.

However there are no problems in the uncompressed version or even when using the compressed version of off one of the CNDs. Though the CND versions only work if the are linked externally, copy pasting code from them also does not work.

comment:4 Changed 11 years ago by voku1987

Same problem here, parse error on line 3 (mobile safari) in the compressed version of the 1.6.4 and also in 1.6.2 ...

comment:5 Changed 11 years ago by dmethvin

Status: newpending

You guys know that you're not providing any information we could use to help solve this problem? The 1.6.4 file has been there unchanged since September 12.

Is there some particular web page that is giving this error when you view it on iOS5?

comment:6 Changed 11 years ago by Hugo Valk <[email protected]…>


You can try running this site: http://www.concordia-waddinxveen.nl/ It uses jquery 1.6.4 on ios5 mobile safari. It gives the parse error on my iPhone 4. After that it cannot resolve the var $ (logical when the jquery file is not processed).

comment:7 Changed 11 years ago by dmethvin

@Hugo, who is your mobile provider? They may be "pre-compressing" the file and causing it to break. I know that T-Mobile does this; see #9969. Note also that if this is the cause it is out of our control.

comment:8 Changed 11 years ago by dmethvin


To turn off this feature on your mobile phone or broadband, visit accelerator.t-mobile.co.uk or accelerator.orange.co.uk on your connection and pick the relevant option – if anyone knows of similar on other networks, do leave updates in the comments.

comment:9 Changed 11 years ago by dmethvin

Resolution: cantfix
Status: pendingclosed

You'll need to contact T-Mobile or Orange at the links above, or however you reach their customer service. This is not fixable by us, since the file is just chopped off.

comment:10 Changed 11 years ago by [email protected]


Just wanted to say that it can be fixed by using the online hosted version: http://code.jquery.com/jquery-1.7.1.min.js


comment:11 Changed 11 years ago by [email protected]

Although this bug has been closed, i'm facing the same issue with 1.7.1 minified and uncompressed versions. I get a parse error using safari on IOS 5. I'm currently developing a new webbased ios application and got this issue. I'll try to get some more details, although it is difficult to debug. Any ideas how toget some more info on this?

comment:12 Changed 11 years ago by dmethvin

If this is a mobile device, your provider is most likely corrupting the file. T-Mobile in particular does this. Google around. Please don't post additional "me toos" on this ticket that have absolutely no debugging information.

comment:13 Changed 11 years ago by anonymous

I'm not using t-mobile, but a wifi connection in my own house. Sorry i can't give any details. The ios browser itself does not give much options. I just tried a jsfiddle, which somehow works. Don't know what the reason for that might be. I load my script in the header from a local resource. This is the fiddle: http://jsfiddle.net/ewR6m/.

comment:14 Changed 11 years ago by dmethvin

The files delivered from the CDN have been there and loaded by millions of browsers without problem, so whatever it is is not a jQuery core bug that should be reported here.

Note: See TracTickets for help on using tickets.