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

Patrick Mueller commented on CB-803:
------------------------------------

I'm wondering if there was some crud between different sessions here; I 
recently changed the way I generate session keys to a mechanism where there's 
likely to be re-use between the keys, if you start/stop the server.  Maybe some 
gunk from the old session got picked up from a new session, or something.

Not much you can do about it, if it is a problem, besides reloading your debug 
clients and targets AFTER you restart the server (if you restarted the server).
                
> Server Bug
> ----------
>
>                 Key: CB-803
>                 URL: https://issues.apache.org/jira/browse/CB-803
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: weinre
>    Affects Versions: 2.0.0
>         Environment: Node Server running on OSX 10.7
> Device - iOS 5.1
>            Reporter: Adam Butler
>            Assignee: Patrick Mueller
>              Labels: ios, json, syntaxerror, weinre
>
> When loading a page I am receiving this error in the node server console only 
> when the client is an iOS device.
> ---------------------------------------------------------
> error: SyntaxError: Unexpected token m
> ---------------------------------------------------------
> stack: 
>           native json.js:56   - parse()
>    jsonBodyParser.coffee:23   - parseBodyAsJSON()
>                events.js:64   - EventEmitter.emit()
>                  http.js:137  - parser.onMessageComplete()
>                  http.js:1410 - socket.ondata()
>                   net.js:354  - onread()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to