I'm attempting to do some development on iOS for a model-viewer web component through browserstack (using iOS 13 Chrome) and it seems unable to connect to localhost, whether I use bs-local (as suggested via browserstack), my IP, or anything else.
I went through their troubleshooting guides with no success, and their own "Debug Connectivity" test in localhost:45454 seems to return a 200 OK response for my page, but live.browserstack.com still seems unable to connect (it returns "Unable to display the page").
I'm attempting to run it using iOS 13 on Chrome.
I've set up the proxy details, enabled 'Force Local', and installed the Browserstack Local app and have verified that it is connected correctly. The URL formats I have tried are:
http://localhost:8000/dev/index.html
http://bs-local.com:8000/dev/index.html
http://bs-local:8000/dev/index.html
http://<my-ip>:8000/dev/index.html
I am writing my code in VS Code and am using node.js/npm and npm run serve using Ubuntu (WSL) in the terminal to start the web dev server, which starts on its own correctly. Opening the page on my own machine seems to work fine, it is solely unable to connect through browserstack live.
Is there a step that I'm missing? What should I troubleshoot next? I'm a junior developer, so please explain in detail.
Related
I recently followed many guides about how to get the chromebook into dev mode, allow modifications by making the linux OS writable and how the forwarding works. Also opened the firewall to allow any traffic. I've entered the --remote-debugging-port=2253 and --remote-debugging-address=0.0.0.0 to the /etc/chrome-dev.conf file. The reason I entered 0.0.0.0 is because to my understanding, chrome does not by default allow remote hosts to connect and is by default only listening to localhost. (This method worked on Ubuntu, macOS and windows devices.)
Now when I start chrome and browse to localhost:2253 I indeed get to see inspectable pages. However, I cannot access these from another machine. (Even with forwarding enabled)
Is there something I am missing or doing wrong? The reason I want to access these pages is because I'm trying to run an automated remote test (with puppeteer) that takes screenshots while 'using' our application.
I've also tried to take another path and get node running on the chromebook without success. I tried doing this with NVM but When installing NVM it fails because of permissions errors. Even when running as sudo.
I hope someone can help me so I can remotely connect to the device with the chrome devtools.
I have been working on a RESTful service (with VS 2015) for about 4 months now, on a Windows 7 development laptop (I don't know if Windows 7 is playing a role here, but I mention it for completeness).
I just purchased a new development machine with Windows 10. I copied my code to that machine, installed VS2015, etc (re-created my development environment).
When I right-click the service project and select Debug->Start new instance, everything works fine, and I can interact with the service from a browser using "http://localhost:[port]/api....."
However, I wish to interact with the service via my android app, that I am developing. I followed the instructions here:
http://becdetat.com/access-iis-express-from-another-machine.html
Namely, I ran the "netsh" command, made the necessary changes to applicationhost.config, etc. On my Windows 7 machine, this worked great and I was able to develop my mobile app.
However, on my new machine, the command:
netsh http add urlacl url=http://192.168.xx.xx:[port]/ user=everyone
causes me to get an error when I attempt to start the service in the debugger. The error is "There was a temporary DNS error. Try refreshing the page. Error Code: INET_E_RESOURCE_NOT_FOUND"
If I then execute:
netsh http delete urlacl url=http://192.168.xx.xx:[port]/
the service runs fine, but I still cannot access it from my android device.
As I mentioned, this worked just fine on my Windows 7 machine.
Thanks for any help.....
I tried 2 example programs from the IBM website.
timestamp example
I cannot see anything in the debug tab. Debug node is of course activated and its output is set to debug tab and console.
Chrome developer tools gives some more information:
Warning: SVG's SMIL animations (, , etc.) are deprecated and will be removed. Please use CSS animations or Web animations instead.
It also detects that something has happended (Preview "OK", Response "OK").
I also tried Chat example
But even when I try to execute the "Run the app" button the window never displays "connection established" or any chat message. Chrome developer tools throws error:
Uncaught InvalidStateError: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
I did not install anything related to Java, JS, JSON, Node.js on my pc as I asume that everything runs inside Bluemix.
The underlying issue is a failure to establish a websocket connection with the node-red instance running in Bluemix. This is a known issue when accessing from certain networks that is usually resolved by accessing the application using https rather than http.
I am using IBM Mobile Test Workbench for Worklight 8.5.10 plugin for Eclipse and I am trying to add a device using my PC. I've done the same process on a Mac and it works fine no issues. However on my PC when I go to the Workbench URL in a browser, phone, or emulator I go to start the download and I receive this on all devices...
HTTP ERROR: 404 Problem accessing
/android/client/com.ibm.rational.test.mobile.android.client.ui-release.apk.
Reason:
Not Found
Does anybody have any idea why I would be getting this?
a good idea would be to check if your firewall is not blocking port 7878 or 8080 (the ones that are used by MTWW to communicate between device and workbench)
simple test for that : stop your firewall for 5 minutes, retry
if it works, it mean you'll have to configure this firewall to open this port
if you can't open this specific port, you can configure MTWW to change the default communication port (to use one that is open in your firewall) like this :
in MTW, open : windows => preferences => Test => performance Test
Report => Web report
check "Allow remote access from a web browser"
check "no security is required to access reports"
change value of "non-secure port" (default = 8080)
when done, it would be better to restart MTWW before retrying
if all of this fail, last solution is to manually install the client apk
apk is located there :
[IBM shared dir of your install]\plugins\com.ibm.rational.test.mobile.android.runtime_[some version number]\client
apk to install : com.ibm.rational.test.mobile.android.client.ui-release.apk
the simpler is use "adb connect [your device ip]" (if adb is not yet connected to your device), then "adb install [apkname]"
Jerome B.
After much trial and errors I finally fixed my issue. Here's the last thing I did to get it working. I uninstalled everything from Java, Eclipse, and IBM. I then reinstalled everything and placed Eclipse in My Documents and I changed Java versions to 1.6. After all of that it seems to be working fine. It doesn't make much sense.
So today, whenever I try to sign My Blackberry app using the WebWorks packager, I get this error...
"General failure. Please try again. Server may be unavailable".
My proxy settings have not changed and I have been using the same command line instruction with success before.
I've also checked the status of the Blackberry signing server using the following link...
http://isthesigningserverdown.com/chart/index.php?sigType=RBB or RCR or RRT
And everything appears to be online!
So, where could I be going wrong? Here's the command line instruction I've been using. First, I navigate to my Blackberry build folder and run the following instruction against it...
bbwp appname.zip –g <password> –o z:\projects\appname\signed
It goes through through parsing the various elements. The signing tool pops up and then the error is generated.
So, after a couple of days of banging my head against the wall-the answer finally came to me. I'm on a MAC but am also using a Windows virtual machine for Blackberry developement, which is running on another network altogether and this specific network is using a firewall, which, according to the network administrator, is currently experiencing a severe technical problem.
The way round it was to sign my Blackberry app using configured proxy settings to communicate with the signing server and viola! It worked!