I have a website which I hot on WinHost.com. In the past few weeks, I have found that 80% of the time, a page stalls while loading. That is, it never loads. It just sits there trying to load.
This issue never happens on my PC.
It does however, happen on my wife's phone too (Same network provider).
We both use Chrome, but it happens on all browsers.
I found a 'Phone Emulator' site, and have no such problems. It seems to load the mobile version fine. It only happens on my, and my wife's phone. The site is in development, so we're the only users.
Is there a way I can debug what is happening, on my phone? Like in the Desktop version of Chrome, I can F12 and see what's happening?
The site runs Asp.Net MVC4, with a Twitter Bootstrap UI.
Sure you can do it by using the latest version of Chrome.
https://developer.chrome.com/devtools/docs/remote-debugging
After connecting, just open the Inspector tool, and select Network tab in PC, reload the page to see what happen.
I found the easiest way was to share my phones internet connection, tether my laptop to it, and run Chrome, pressing F12 to get the network traffic.
Related
Goal: Test android app on a physical device with various network connectivity issues (Offline, Slow 3G etc). Android Emulator is not an option for my use case.
Steps I have tried: (Remote Debugging)
Connect my phone to my computer and open the app on my phone.
In chrome "Remote devices" I select my phone and click on inspect for the app opened on my phone. Once the Developer Tools window opens I can play with my app from chrome.
In the network tab I can see the throttling options but when I try the offline option or any other option to slow down the network it does not seem to work.
The offline/slow 3G option works for a normal website but not when using remote devices. I wanted to see if anyone has tried this option before and if it worked for them and I would appreciate suggestions for better alternatives to test an android app with various network settings other than using chrome remote devices?
Other options I have come across are installing a proxy app on PC/Mac and configure networking throttling in the app and then create a wifi hotspot and connect my phone with it. This is possible but it would be tricky with the tools we use so I was looking for a more elegant solution.
The "remote devices" of chrome won't affect your native app. It will not even affect another opened tab other than the one you are "inspecting" and throttling. If you really need to throttle your device's network connection you should use a proxy. A good and easy to handle proxy is Charles web debugging. The free version will cover your needs if you are willing to reconnect every 30 mins. But for sure I recommend you purchase a license since this tool will be always helpful and developers also need to make a living ;)
Here is an example of setting up Charles as a proxy for an android device.
It's a little unclear from your question, but I'm assuming that you're using Remote Debugging to run a webpage on an Android device, and you want to profile the webpage from a laptop/desktop connected to the Android.
One workaround is to use https://www.webpagetest.org/easy. This actually runs your webpage on a real Motorola G device in Virginia with a Slow 3G connection. It gives you a detailed report on your loading performance, just like the DevTools Performance panel.
One of the DevTools team members said that Remote Debugging + Network Throttling should work, but neither of us has tried it recently.
This is a doozy. Will try and make it short and sweet.
Hitting the same web URL, my desktop computer reports SSL errors for many sites. HTTPS with a red line strike through and red padlocks in descriptions.
My mobile phone does not, on wifi or mobile network. My remote computer in a remote location does not. Green padlocks for all.
Chrome browser is up to date and latest (Version 47.0.2526.106 m) across all browsers. Extensions are identical across local and remote desktop.
I cannot for the life of me figure out what is loading up on my desktop at home that isn't loading up on my remote desktop at my moms. Both machines are on Win7 64 bit. Both chrome browsers are same version, same extensions running. Recently 'reset' chrome on my home desktop to try and fix. Worked first time, but problem came back. Second time it didn't do anything. Very random. Somedays i'll get green padlocks, somedays i get red ones. The intermittent nature of this has me dumbfounded. Also, all of the browsers actually state the info about an obsolete cipher, but only my desktop deems it to be redlock worthy. It also claims there are other insecure resources on the page, but my remote desktop and mobile device don't see them. wth?!?!
Should i completely remove chrome and reinstall it from scratch? Since i already used the 'Restore settings to their original defaults.' button in the settings.. this doesn't seem like it would cure it.
One other aspect i haven't been able to determine is whether my computer being hardwired into a TL-WPA4220 WiFi Powerline Extender is the culprit. Does the fact the extender/repeater not a direct connection to my router have anything to do with this? Altho my mobile phone is connected to that wifi access point and it shows a green padlock on the same sites so....
I am currently running a virus scan as we speak.
Any guesses? Thanks in advance.
Attached pics.
home desktop | remote desktop
if you look at the dialog at the home desktop closely you will see
connection is not private because the site loaded an insecure script
Since you don't see the message at the remote desktop it is very likely that a locally installed browser extension causes this problem. Thus check your extension, disable them and retry.
I figured it out after thinking long and hard about the differences between computers. Ultimately i realized that all the working browsers were either fresh installs, or browsers that didn't have my user account connected and synced through it.
I ultimately went to Settings > Sign In / Disconnect your Google Account... and made sure all cookies/data for the local device were removed. Then i did a full browser 'Reset'.
Once i had the default standard page asking me to sign it, i tested the offending page. It showed up with a green padlock. I tested other offending bank sites as well. All green.
From there i closed the browser and restarted it, and when presented with the page to log into my google account, it resynced all my bookmarks/toolbars/extensions.
And still all green padlocks. Hopefully this is a permanent fix but for now it's all holding well. I also got slightly more updated to Chrome Version 47.0.2526.111 m.
My assumption here is that somewhere between the time i first synced my chrome to my google account years ago on this computer, whatever version it was then (42,45,who knows) that one of the updates to chrome didn't take well on my desktop and was creating conflicts only on this computer under this local profile. No amount of clearing cookies or resetting the browser could fix it. Fully disconnecting my account and re-syncing my chrome to my google account is what fixed the HTTPS / SSL padlock problems.
Not sure if this will help anyone, seems i was the only one on the internet with this problem. :P
Is there any way to see the network related logs in chrome mobile phone browser?
I have tried and I found that in desktop browser we can view network related information
I want to see how page load time in network tab for chrome mobile browser
Yeah, you definitely can. Check out this tutorial:
https://developer.chrome.com/devtools/docs/remote-debugging
It'll allow you to debug your mobile browser from the desktop dev tools.
Maybe it is a little late but i still leave my answer here.
Android
if your android app is using stetho, then you can:
Connect your device with a usb cable to your PC
Navigate to chrome://inspect/#devices
It opens a page which includes the list of your devices
Click on the link of your device and it opens Developer tools of chrome for you, which includes console, and Network tabs
But, keep in mind that your app must benefit from stetho, otherwise you don't see anything.
IOS:
Install Charlesproxy
Follow this guideline
Mozzila decided they don't need error console in their mobile browser, so they instead invented "Remote debugging", something that would probably be cool if it ever worked. I tried it few times before just for fun, but never got it to connect. Now I really needed and I was also expecting the feature improved over time. Not at all.
Enable on Mobile
To enable remote debugging, you're first supposed to allow USB debugging and then remote debugging in Firefox Mobile. These are just two buttons, so it's no problem. My Firefox Mobile version is 39.0.
Enable in browser
In browser, as I understand it, WebIDE is used, which is a special Firefox debugger and virtualiser. Can be launched using Shift+F8. The connected USB device is supposed to appear in menu:
I was wondering why I see Install ADB Helper in menu when it's already installed. It's probably because this:
I guess Firefox hates me.
The question
Since Mozzila obviously disabled their only means of debugging mobile Firefox, I came here to ask for some workaround. With all those mobile web pages I expect lot of you guys know how to debug them. Possible solutions I'm looking for:
Debug over IP instead of USB. I am much more comfortable with using WiFi than USB.
Force Firefox to enable ADB Helper even though it's incompatible.
To get ADB Helper working, update your Firefox desktop version. It looks like you're on 37, which is unsupported, insecure, and ~6 months out of date.
Wi-Fi Debugging landed in Firefox 42: https://developer.mozilla.org/en-US/docs/Tools/Remote_Debugging/Debugging_Firefox_for_Android_over_Wifi
I have an application build with Rhodes that runs well in many kinds of devices.
But, in a Samsung GalaxyTab with Android 3.2 it has a problem (GT-P6210).
The device doesn't have 3G, only Wi-Fi.
When Wi-Fi is enabled, it works fine.
When Wi-Fi is disabled, it works for some minutes and so it shows a page saying "Web page unavailable" and shows the URL (http://localhost:53899/app/....) exactly the same screen that appear on the Android's default browser when it do not find an URL.
If I copy the URL and go to the browser and try to access it so the page is loaded normally.
Do somebody has any idea of what could be happening?
Thanks in advance.
On Launchpad there's currently a proof of concept to fix this:
https://developer.motorolasolutions.com/message/11817#11817