dtmilano / CulebraTester-public

Public repository corresponding to CulebraTester
11 stars 0 forks source link

Windows Desktop not launching the Culebra GUI #10

Open kselvaakumar opened 6 years ago

kselvaakumar commented 6 years ago

Hi, I have done the setup of Android studio, through which able to launch the emulator. Now, i have installed both Culebra tester and instrumentation in the emulator. with the address shown in the Culebra App, the url is not found in my windows desktop PC. can you please let know what i should do to get the Culeber GUI on my desktop PC?

dtmilano commented 6 years ago

Plase, take a look at Using emulator with Google Play support.

Don't hesitate to ask or comment here if it doesn't solve your problem.

clahzita commented 6 years ago

I can't open the main page in my desktop browser. I don't have sucess with any of the two address that is showed on the screen. In my case I'm using a physical device.

dtmilano commented 6 years ago

@clahzita can you describe the issue in greater detail? Can you tell me the url you are trying to reach? Can you successfully do adb shell to that device?

wntdt commented 6 years ago

I have complete all the setup as androidviewclint, android studio also download culebra tester and culebra instrument but the url which is displayed in screen when open culebra tester app can not open in my windows 7 laptop browser. Please help to resolve the problem.

both mobile device and laptop device was connected through same AP.

dtmilano commented 6 years ago

@wntdt Can you successfully do adb shell to that device? What's the url? Can you ping the device IP on your wifi network from your windows laptop?

clahzita commented 6 years ago

I executed those steps:

  1. Install Culebra Tester and Culebra Tester Instrumentation.
  2. Connect the device (galaxy S6) with depuring usb on and I tested adb device to see it was online.
  3. Run Culebra Tester and put the IP on my browser: http://192.168.2.18:9999

After that, I waited to open the Culebra page, but it's not happened. Now, I'm using Linux. "Can you successfully do adb shell to that device?" I don't know what it's mean. Do I have to send some shell command to my device before run culebra page on my browser?

Update 16:45, 03/06/2018: I tested shell comands on the device, an it works.

dtmilano commented 6 years ago

@clahzita I understand from your comment that 192.168.2.18 is the IP of the phone on the same wifi network as the Linux desktop computer you are using the browser on, correct?

Then from that Linux computer can you ping 192.168.2.18? From the same computer, can you run adb shell ip addr show and see 192.168.2.18?

clahzita commented 6 years ago

http: //192.168.2.18:9999 is the address that is showed on Culebra Tester screen. when I use the ping command as you asked, this message appears "PING 192.168.2.18 (192.168.2.18) 56 (84) bytes of data." and when I use the adb command I can see the IP addr in the middle of some lines showed in the terminal screen.

dtmilano commented 6 years ago

@clahzita let's try this from your Linux machine

$ curl -v http://192.168.2.18:9999

and you should expect

* Rebuilt URL to: http://192.168.2.18:9999/
*   Trying 192.168.2.18...
* TCP_NODELAY set
* Connected to 192.168.2.18 (192.18.2.18) port 9999 (#0)
> GET / HTTP/1.1
> Host: 192.168.2.18:9999
> User-Agent: curl/7.54.0
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently 
< Content-Type: text/html
< Date: Tue, 6 Mar 2018 21:30:35 GMT
< Location: /Assets/culebra.html
< Connection: keep-alive
< Content-Length: 93
< 
* Connection #0 to host 192.168.2.18 left intact
<html><body>Redirected: <a href="/Assets/culebra.html">/Assets/culebra.html</a></body></html>

if it doesn't happen, then the wifi router might be blocking traffic between devices.

dtmilano commented 6 years ago

@clahzita also, if while you are seeing the Culebra Tester screen showing the message

Service started. You can access

http://192.168.2.18:9999

you run

$ adb shell netstat -ta | grep 9999

you should see

tcp6       0      0 :::9999                 :::*                    LISTEN 
clahzita commented 6 years ago

I used curl command and I saw:

* Rebuilt URL to: http://192.168.2.18:9999/
*   Trying 192.168.2.18...
* connect to 192.168.2.18 port 9999 failed: Connection timed out
* Failed to connect to 192.168.2.18 port 9999: Connection timed out
* Closing connection 0
curl: (7) Failed to connect to 192.168.2.18 port 9999: Connection timed out

the adb command showed: tcp 0 0 :::9999 :::* LISTEN

Probably, the problem is the permission config of my university network. I gonna try use it in my home and I come back to give you an answer. Thank you anyway for help me!

dtmilano commented 6 years ago

@clahzita most probably your network is blocking traffic between wifi devices.

Another alternative would be to use an emulator with Google Play as described in Using-emulator-with-Google-Play-support.

Based on this conversation I also started Troubleshooting to help others.

Thanks and let me know if it worked for you.

clahzita commented 6 years ago

I tried to use on my personal computer and the culebra browser page worked. So, I saw the Troubleshooting and I gonna try to use the forward adb shell command tomorrow, I hope it works.

I'll be back here to talk about the result.

dtmilano commented 6 years ago

@clahzita Nice to hear that.

wntdt commented 6 years ago

My laptop device OS is windows 7.

I installed Culebra Tester app and Culebra instrument also Completed all setup asandroidviewclint.

  1. now when i launched culebra tester app shows a url: http://192.168.0.103:9999
  2. try to open this url in my laptop device browser, can't able to open(adb shell command run successfully)
  3. also can run the command C:\Users\Anil.Mishra>adb shell netstat -ta grep 9999 Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 localhost:36898 :::* LISTEN

tcp 0 0 :::9999 :::* LISTEN

tcp 1 0 ::ffff:192.168.0.103:45 maa05s03-in-f14.1e100.n CLOSE_WAIT

tcp 1 0 ::ffff:192.168.0.103:34 ::ffff:222.66.158.137:h CLOSE_WAIT

tcp 0 0 ::ffff:192.168.0.103:58 sc-in-f188.1e100.net:52 ESTABLISHED

tcp 1 0 ::ffff:192.168.0.103:44 maa05s03-in-f14.1e100.n CLOSE_WAIT

tcp 1 0 ::ffff:192.168.0.103:44 maa05s03-in-f14.1e100.n CLOSE_WAIT

tcp 1 0 ::ffff:192.168.0.103:45 maa05s03-in-f14.1e100.n CLOSE_WAIT

tcp 1 0 ::ffff:192.168.0.103:45 maa05s03-in-f14.1e100.n CLOSE_WAIT

tcp 1 0 ::ffff:192.168.0.103:50 maa05s09-in-f5.1e100.ne CLOSE_WAIT

C:\Users\Anil.Mishra>

  1. My mobile device and laptop device both are connected to same AP. 5.Mobile device connected to laptop through USB.

Please help to tell how i can open that url in browser.

On Wed, Mar 7, 2018 at 11:06 AM, Diego Torres Milano < notifications@github.com> wrote:

@clahzita https://github.com/clahzita Nice to hear that.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dtmilano/CulebraTester-public/issues/10#issuecomment-371028524, or mute the thread https://github.com/notifications/unsubscribe-auth/AOI_eLZsP2sRGjYLWq5S3d9FCy8iHnf9ks5tb3HLgaJpZM4SIOJn .

clahzita commented 6 years ago

So, @dtmilano, I used this: $ adb forward tcp:9999 tcp:9999 And I opened http://localhost:9999 on my browser. It's worked to open the culebra url using my device connected via USB.

Thank you for your help! :+1:

dtmilano commented 6 years ago

@wntdt probably the traffic between your device and computer is filtered by your AP/router. The service is listening and you have access to your device via adb which is great.

Check Troubleshooting and see if the adb forward workaround works for you too.

wntdt commented 6 years ago

Hi,

When i tried to open the url as you suggested: http://localhost:9999 on my windows laptop device, url open successfully but shows below problem as attached, please suggest for resolution.

On Thu, Mar 8, 2018 at 2:46 AM, Diego Torres Milano < notifications@github.com> wrote:

@wntdt https://github.com/wntdt probably the traffic between your device and computer is filtered by your AP/router. The service is listening and you have access to your device via adb which is great.

Check Troubleshooting https://github.com/dtmilano/CulebraTester-public/wiki/Troubleshooting and see if the adb forward workaround works for you too.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dtmilano/CulebraTester-public/issues/10#issuecomment-371287456, or mute the thread https://github.com/notifications/unsubscribe-auth/AOI_eIpT598RBVikqhINKTYxV3vxLskaks5tcE4xgaJpZM4SIOJn .

dtmilano commented 6 years ago

@wntdt I'm not seeing your attachment. Can you please describe what you see once you open the url?

auuunya commented 6 years ago

image

hi,Tell me about it,please

auuunya commented 6 years ago

图片

嗨,请告诉我

image The browser repeats the interface