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

Andrew Grieve commented on CB-1807:
-----------------------------------

Okay, thanks for giving that a go. I'll test it out on my device tomorrow.

I should also make sure you're not doing any navigations. There was a bug
in 2.2 that if you navigate at all the connection API is busted. Fix is
here:
https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=blobdiff;f=framework/src/org/apache/cordova/NetworkManager.java;h=af2fc7d3b4fcd330c1898d8d5792cc83f2081519;hp=5d8791809227877d604c98cf029c26242d9642b8;hb=dc459c84a36f90f2383203ceab56a47341360937;hpb=e51b4897a34c8d4430ad8036cff86f7fd95747b8




                
> Android navigator.connection.type is not equal to 
> navigator.network.connection.type
> -----------------------------------------------------------------------------------
>
>                 Key: CB-1807
>                 URL: https://issues.apache.org/jira/browse/CB-1807
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 2.2.0
>            Reporter: Thejaswi Puthraya
>            Assignee: Andrew Grieve
>             Fix For: 2.3.0
>
>         Attachments: index.html
>
>
> As per the documentation and example navigator.connection.type is what was 
> previously navigator.network.connection.type.
> """
> Before Cordova 2.2.0, the Connection object existed at: 
> navigator.network.connection.
> To match the spec, this was changed to navigator.connection in 2.2.0.
> navigator.network.connection still exists, but is now deprecated and will be 
> removed in a future release.
> """
> But in the file that I am enclosing to reproduce the bug, 
> navigator.connection.type is always (irrespective of connection) 'unknown'(0) 
> though navigator.network.connection.type returns the correct value.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to