[TIMOB-28056] Liveview: Unable to connect to device
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | None |
| Status | Closed |
| Resolution | Not Our Bug |
| Resolution Date | 2020-08-20T13:01:18.000+0000 |
| Affected Version/s | Release 9.0.3, Release 9.1.0 |
| Fix Version/s | n/a |
| Components | LiveView |
| Labels | n/a |
| Reporter | Samir Mohammed |
| Assignee | Ewan Harris |
| Created | 2020-07-29T14:08:25.000+0000 |
| Updated | 2020-08-20T13:01:18.000+0000 |
Description
When trying to use Liveview the device is unable to connect to the Liveview server.
*Test Steps:*
Create an alloy application
Enable liveview
Run application to device
*Expected result* Device should be able to connect to the liveview server and be able to make changes. *Actual result* Application hangs on splash screen and following error is seen.
[ERROR] : Script Error {
[ERROR] : column = 24;
[ERROR] : line = 669;
[ERROR] : message = "[LiveView] File Server unavailable. Host Unreachable @ 192.168.86.26:8324\n[LiveView] Please ensure your device and computer are on the same network and the port is not blocked.";
[ERROR] : sourceURL = "file:///var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/app.js";
[ERROR] : stack = "file:///var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/app.js:669:24\nfile:///var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/app.js:685:35\nfile:///var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/app.js:715:30\nfile:///var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/app.js:589:25\nfile:///var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/app.js:423:45\nfile:///var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/app.js:760:15\nfile:///var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/app.js:765:3\nglobal code@file:///var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/app.js:768:70\nrequire@[native code]\nfile:///private/var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/ti.main.js:13966:10\nloadAsync@file:///private/var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/ti.main.js:13894:13\nglobal code@file:///private/var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/ti.main.js:13963:10";
[ERROR] : type = Error;
[ERROR] : }
[ERROR] : Script Error {
[ERROR] : column = 10;
[ERROR] : line = 13966;
[ERROR] : message = "Module \"app.js\" failed to leave a valid exports object";
[ERROR] : sourceURL = "file:///private/var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/ti.main.js";
[ERROR] : stack = "require@[native code]\nfile:///private/var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/ti.main.js:13966:10\nloadAsync@file:///private/var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/ti.main.js:13894:13\nglobal code@file:///private/var/containers/Bundle/Application/E614D646-A8E3-490C-8F9E-91BE5236D262/anewtestii.app/ti.main.js:13963:10";
[ERROR] : type = Error;
[ERROR] : }
Tracked this down to the VPN software Check Point endpoint security which helpfully blocks all incoming traffic once you install it, even if it's not running! Closing as not our bug