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

ASF GitHub Bot commented on CB-6757:
------------------------------------

GitHub user jsoref opened a pull request:

    https://github.com/apache/cordova-blackberry/pull/158

    CB-6757 Provide useful hint when simulator does not seem to know its IP

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/blackberry/cordova-blackberry cb-6757

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cordova-blackberry/pull/158.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #158
    
----
commit 301713a319cb0b5629e990ba7896e210528dd9b0
Author: Josh Soref <[email protected]>
Date:   2014-05-16T21:39:46Z

    CB-6757 Provide useful hint when simulator does not seem to know its IP

----


> Provide useful hint when simulator does not seem to know its IP
> ---------------------------------------------------------------
>
>                 Key: CB-6757
>                 URL: https://issues.apache.org/jira/browse/CB-6757
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: BlackBerry
>    Affects Versions: 3.4.0
>            Reporter: Josh Soref
>            Assignee: Josh Soref
>
> Right now, if you use a simulator w/ cordova-blackberry and have web 
> inspector enabled (the default), you get an alert which doesn't help you 
> connect to web inspector because the simulator doesn't reflect in enough 
> information via the interfaces that the web system is expecting in order to 
> know its IP address.
> The browser has a different way to calculate the IP address, but a user can 
> see the VM's IP address at the bottom of the VM window, all that's really 
> essential is the port.
> We know the port, so we can show it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to