Languages

Menu
Sites
Language
Unable to debug properly on Tizen SDK 2.3.1 (wearable)

Hi,

I am using Tizen SDK 2.3.1 for Developing a wearable web app.

I am using the "Debug as" option of SDK. "Debug as" option of SDK is not working smoothly.

I am getting the following error "7 out of 10 times"

 

Setting the debugging URL... > Fail
socket closed
 (Return Code:1101)Inspector response error.

 

My development time is getting increased unnecessarily because of this error. (Unable to launch web inspector)

Please help if someone has encountered the same problem before.

Devices used are Gear S and Gear S2

List

Responses

7 Replies
Seoghyun Kang

Hello,

 

That's strange. Did you install the Chrome brower in your PC?

 

If you installed it, please check the preferences in Tizen SDK.

The following data is my preferences. Please refer it.

 

1) General > Web Browser

  : Use internal web brower / Default system web browser

 

2) Tizen SDK > Web > Chrome

   - Location : /opt/google/chrome/google-chrome (Please check your path)

   - Extra parameters : --no-first-run --activate-on-launch --no-default-browser-check --allow-file-access-from-files --disable-web-security --disable-translate --proxy-auto-detect --proxy-bypass-list=127.0.0.1

 

Thanks.

Gaurav Singhal

Hi,

Yes, Google Chrome is installed in my machine. I am able to launch the inspector tool around "3 out of 10 times", but not always.

I checked the above settings and they exactly match with the ones you have specified.

It seems to be the default SDK settings.

Google Chrome location is different for my SDK.

It is C:\Program Files\Google\Chrome\Application\chrome.exe

But I think, It can vary from one system to another.

Earlier I used Tizen SDK 1.0.0 and I didn't get to see this error.

Alex Dem

Hi,
Is there the same issue with emulator? What SDK 2.3.1 (Win32/64 or Ubuntu) do you use?
Alexey.

Chanyou Hwang

I'm also getting pain from this issue... any other solutions?  I've tried all above..
and I'm debugging on the real device (Gear S2)

Egor Schavelev

Same problem here. I can debug on emulator normally, but on real device most times it doesnt launch. Same with topic starter, 8-9 out of 10 launches cannot be debugged. Chrome just doesn't start, and app is crushing on device, ide anserws with same error

Setting the debugging URL... > Fail
socket closed
 (Return Code:1101)Inspector response error.

 

 

Alessandro Mancini

I have the same issue.

9 out of 10 times.

I try with chromium, chrome, firefox, but I have the same problem.

Hendrik Boshoff

+1 since this issue affects me as well.

Using Ubuntu 14.04 with Tizen SDL Version : 2.3.1 Rev1, Build id : 20151104-1527 and Chromium.

As with other commentors, it works sometimes, so the configuration could not be the problem.

But the success rate is really low (~20%) so it is hugely frustrating.