chrome v88 inspector page is blank

[mousne]

same issue

[prozanne]

Hi,
I've tested on v88.0.4324.190(chromium), and It seems ok.
Could you please check the version of WITs?
As you mentioned, we had a similar issue before. and the bug was fixed over v2.1.1

This option value was added for fixing the issue#25
https://github.com/Samsung/Wits/blob/master/lib/appLaunchHelper.js#L154

[sobbe81]

Hi,

I have the same issue running Chrome v91 on Mac OS X Big Sur. Using Witz version 2.5.0

[pwsses]

Hi,
I have the work well running Chrome v91.0.4472.114 on Windows.
Do you have any message like issue image?

[sobbe81]

T211-WL000598:fooPlay myUserID$ wits -s --verbose

---

| | /| / / / /
| |/ |/ // / / / (-<
|/|// // /__/

Start running Wits............

[@tizentv/tools]tools.getToolPath: toolName = sdb

  > [ Stored Information ]

  > baseAppPath  : /Users/myUserID/projects/foo-samsung-tv/dist/build/fooPlay
  > width        : 1920
  > deviceIp     : 192.168.1.59
  > isDebugMode  : true

  > profile path : /Users/myUserID/tizen-studio-data/profile/profiles.xml
  > hostIp       : 192.168.1.42

connect to....192.168.1.59
192.168.1.59:26101 is already connected

Success to connect 192.168.1.59
List of devices attached
192.168.1.59:26101 device QE55LS03RAUXXC

secure_protocol:enabled
intershell_support:disabled
filesync_support:pushpull
usbproto_support:disabled
sockproto_support:enabled
syncwinsz_support:enabled
sdbd_rootperm:disabled
rootonoff_support:disabled
encryption_support:disabled
zone_support:disabled
multiuser_support:enabled
cpu_arch:armv7
sdk_toolpath:/home/owner/share/tmp/sdk_tools
profile_name:tv
vendor_name:Samsung
can_launch:tv-samsung
device_name:Tizen
platform_version:5.0
product_version:4.0
sdbd_version:2.2.31
sdbd_plugin_version:3.7.1_TV_REL
sdbd_cap_version:1.0
log_enable:disabled
log_path:/tmp
appcmd_support:disabled
appid2pid_support:enabled
pkgcmd_debugmode:enabled
netcoredbg_support:enabled

content src is : index.html

Start packaging Samsung Tizen TV Platform......

[webide-common-tizentv]projectHelper.buildWidget() profilePath = /Users/myUserID/tizen-studio-data/profile/profiles.xml, excludeFiles = undefined
After build package, signature tempory files were removed
[webide-common-tizentv]projectHelper.widget.on(): Build Package completed!
============================== Build Package completed!

============================== Start to install the package

uninstall fooPlayWITs
app_id[fooPlayWITs] uninstall start
app_id[fooPlayWITs] uninstalling[4]
app_id[fooPlayWITs] uninstalling[9]
app_id[fooPlayWITs] uninstalling[13]
app_id[fooPlayWITs] uninstalling[18]
app_id[fooPlayWITs] uninstalling[22]
app_id[fooPlayWITs] uninstalling[27]
app_id[fooPlayWITs] uninstalling[31]
app_id[fooPlayWITs] uninstalling[36]
app_id[fooPlayWITs] uninstalling[40]
app_id[fooPlayWITs] uninstalling[45]
app_id[fooPlayWITs] uninstalling[50]
app_id[fooPlayWITs] uninstalling[54]
app_id[fooPlayWITs] uninstalling[59]
app_id[fooPlayWITs] uninstalling[63]
app_id[fooPlayWITs] uninstalling[68]
app_id[fooPlayWITs] uninstalling[72]
app_id[fooPlayWITs] uninstalling[77]
app_id[fooPlayWITs] uninstalling[81]
app_id[fooPlayWITs] uninstalling[86]
app_id[fooPlayWITs] uninstalling[90]
app_id[fooPlayWITs] uninstalling[95]
app_id[fooPlayWITs] uninstalling[100]
app_id[fooPlayWITs] uninstall completed
spend time for wascmd is [1987]ms
cmd_ret:0
WARNING: Your data are to be sent over an unencrypted connection and could be read by others.
pushed WITs.wgt 100% 130KB 0KB/s
1 file(s) pushed. 0 file(s) skipped.
/Users/myUserID/.nvm/versions/node/v10.18.1/lib/node_modules/@tizentv/wits/container/WITs.wgt 599KB/s (133804 bytes in 0.217s)

install fooPlayWITs
package_path /home/owner/share/tmp/sdk_tools/WITs.wgt
was_install_app return WAS_TRUE
app_id[fooPlayWITs] install start
app_id[fooPlayWITs] installing[10]
app_id[fooPlayWITs] installing[12]
app_id[fooPlayWITs] installing[15]
app_id[fooPlayWITs] installing[17]
app_id[fooPlayWITs] installing[20]
app_id[fooPlayWITs] installing[22]
app_id[fooPlayWITs] installing[25]
app_id[fooPlayWITs] installing[27]
app_id[fooPlayWITs] installing[30]
app_id[fooPlayWITs] installing[32]
app_id[fooPlayWITs] installing[35]
app_id[fooPlayWITs] installing[37]
app_id[fooPlayWITs] installing[40]
app_id[fooPlayWITs] installing[42]
app_id[fooPlayWITs] installing[45]
app_id[fooPlayWITs] installing[47]
app_id[fooPlayWITs] installing[50]
app_id[fooPlayWITs] installing[52]
app_id[fooPlayWITs] installing[55]
app_id[fooPlayWITs] installing[57]
app_id[fooPlayWITs] installing[60]
app_id[fooPlayWITs] installing[62]
app_id[fooPlayWITs] installing[65]
app_id[fooPlayWITs] installing[67]
app_id[fooPlayWITs] installing[70]
app_id[fooPlayWITs] installing[72]
app_id[fooPlayWITs] installing[75]
app_id[fooPlayWITs] installing[77]
app_id[fooPlayWITs] installing[80]
app_id[fooPlayWITs] installing[82]
app_id[fooPlayWITs] installing[85]
app_id[fooPlayWITs] installing[87]
app_id[fooPlayWITs] installing[90]
app_id[fooPlayWITs] installing[92]
app_id[fooPlayWITs] installing[95]
app_id[fooPlayWITs] installing[97]
app_id[fooPlayWITs] installing[100]
app_id[fooPlayWITs] install completed
spend time for wascmd is [2458]ms
cmd_ret:0
wascmd cannot working in released image

... successfully launched pid = 5426 with debug 1 port: 45811

listening on 9604
a user connected
new client connected, id = p0knVDhsr9MvSEIAAAAA
socket on::::push_request
[warning] Failed to get Wits ignore Error: ENOENT: no such file or directory, open '/Users/myUserID/projects/foo-samsung-tv/dist/build/fooPlay/.witsignore'
socket on::::watch_request
Total File Number : 88
Chrome debugging port running on 51189

In Chrome on the page with the "Wits link" I see some errors in the console.

The 2nd 404 is when trying to get this: http://192.168.1.59:43714/undefined

This is what I see in the console after pressing the "Wits" link

[pwsses]

It is same issue from chrome version, Temporarily, I recommend use other browser or lower version of chrome with http://192.168.1.59:43714. We well check again

[sobbe81]

Ok, thanks.

I tested Safari and Firefox but get the same behaviour.

[mousne]

chrome version 95.0.4638.54
wits version 2.5.2
also same error

[hygortc]

Hi,
test this
"isDebugMode": true in .witsconfig.json

killall -9 sdb

go wits -s --verbose

wait chrome open
before open access link wits in page

before link open copy ip and port in url ws=192.168.1.6:35537

open other aba go to chrome://inspect click em configure and add ip address u copy in url
192.168.1.6:35537

in remote target click in inspect....

sorry my bad english
hope this help...

[mousne]

Hi, test this "isDebugMode": true in .witsconfig.json

killall -9 sdb

go wits -s --verbose

wait chrome open before open access link wits in page

before link open copy ip and port in url ws=192.168.1.6:35537

open other aba go to chrome://inspect click em configure and add ip address u copy in url 192.168.1.6:35537

in remote target click in inspect....

sorry my bad english hope this help...

It's works for me!
Thanks!

[MacgyverMartins]

@prozanne
I am having the same problem here.
I was trying to debug using just sdb but I had to do this same process that @hygortc told about.
So I decided change to wits to not have to do this process, but looks like even with wits we have to open the
chrome://inspect and confige it for every build 🙁🙁

Does someone know why this step is needed ? There is some way we can launch chrome inspector without need to open chrome://inspect and confige it manually ?

[MacgyverMartins]

My page just got stuck with this warning :

There is some idea about what is happening ? This issu was open more than one year ago

[IceProgrammer15]

You will keep getting a blank white screen in developer tools unless you use Chrome 79.0 or older

[zemlanin]

Using bundled DevTools (devtools://devtools/bundled/inspector.html) seems to work in newer versions of Chrome