For some reason the iPhone devices are never able to load the url requested by Protractor, they always show a blank page. It tries to load the url several times and then gives up.
The other BrowerStack devices all seem to work, including Windows, Android, and Safari/Macbook.
Has anyone encountered a similar problem?
For reference, we're using Protractor v2.2.0 (have not been able to updated because we're stuck in an old version of NodeJS, but we could try if that is the cause of the issue).
Related
I am working on a project which is using rails for its backend and react components for its frontend. The app works fine in the Safari browser but for some unknown reason, in the chrome app, it loads the correct path but just renders a white screen showing nothing. If I check the developer tools console, I get to see the following errors
Similarly I refreshed the page and opened the network tab in developers tool and got to realise that some of the packages have not been downloaded.
The point to note is that the app also requires a certificate for running it locally and I have already downloaded that certificate and trusted it so it should also not be a problem. I am stuck at it for a really long time. Can anyone tell me the solution?
As the app works fine in safari, I don't think its related to code but its just a guess. So far I have tried disabling all the extension as well as clearing the browser data but haven't been able to see any progress...
I have a really strange problem with an AngularJS application using Internet Explorer (ver 11.0.9600.18697) as browser.
I am developing an application using AngularJS. The application runs perfectly on Firefox and Chrome, but on IE I'm experiencing the following problem.
What happens is that, when I start the application, the startup stops because IE at a certain point randomly stops loading the necessary resources, simply terminating some calls of js, i18n, css files.. (calls do not arrive at the server, simply IE blocks them, despite being the path all correct).
I have not understood the reasons of this behavior. What I know is that I use RequireJs for loading files (ver. 2.1.22), and that on Firefox and Chrome everything is loaded properly. Moreover, if I start the application on IE keeping Fiddler open, then the application works very well on IE too.
Has anyone ever had a similar problem?
Here the network console:
I have created one ionic app it runs perfectly fine in browser but when I convert it into app it gives white screen.
I have already install white list plugin and allowed all url in config and also have kept meta tag. Am not able to find any other solution.
When kept simple html file am able to view it.
Any help will be grateful.May be good way to debug will be also good.
Connect your phone to PC with USB cable and remember to keep USB Debugging On. Now, navigate to chrome://inspect. You'll find the device name and click on "inspect". On Console tab, the error list will give you a hint about what is wrong there.
In my case, a custom service was Injected in controller which had been removed at some time as It was not used anywhere.
Ok just answering this question so it will be helpful to all.
Below blog was helpful for me that how I can debug
http://gonehybrid.com/how-to-debug-the-white-screen-of-death-in-your-ionic-app/
And guess what was issue, folder name in app is case sensitive. I was just need to change a folder name as per exact case sensitive path I provide in index file.
Mostly such thing occures because of a javascript error. You say it runs in your browser. Are there some exception in the console?
Not everythings is equal between browser and device, for example plugins. You have to be sure, that all used plugins are installed properly.
If you deploy on android, you can use android monitor to get console output. On ios xcode has already an integrated debugger.
I had this horrible issue because I compiled my Android application with Cordova 6.x and the project worked with CrossWalk plugin. In my case, the solution was uninstalling Crosswalk. If your project has installed that plugin, try to uninstall it and compile your project again.
I have an Angular App that we recently upgraded to AngularJS v1.3.8 and now we get intermittent "Aw, Snap" crashes in chrome. But the app runs fine in other browsers and on certain computers.
Any time we encounter this error a refresh fixes it immediately.
We have explored many options trying to figure out the root cause of this issue:
- Verify memory profile
- Verify CPU profile
- Verify Hardware Acceleration on/off
- Verify minified/unminified AngularJSv1.3.8
When we reverted back to Angular v1.2.7 we no longer see this crash. We have isolated this change and is the ONLY change between revisions.
Has anyone experienced this as well? Or does anyone know of any reasons for this? Or any compatibility issues that could lead to this error?
Error encountered using Chrome Version 39.0.2171.95 (64-bit)
For us, this occurred when we did an $injector.invoke inside a responseError interceptor. It seems that it is sensitive to that.
I want to use selenium/webdriver to simulate a browser and scrape some website-content with it. Even if its not the fastest method, for me it has many advantages such as executing scripts etc.
For many websites it is forbidden to access them via an automated method, for example search engines like google or bing.
For one tool i need to scrape the estimated resultstat from google for several keywords. This will look like the following: simulate the browser that visits google.com and types in a keyword and scrapes the results, then after a little pause type in the next keyword, scrape the results and so on...
My question is: Is it possible for a website to recognize that I'm using selenium to simulate the browser instead of using the browser by hand? Especially the google case gives me some doubts. I know selenium is partly developed by google or at least by some guys working for google. So does leave selenium some fingerprints or isn't it possible to decide if I'm using the browser by myself or simulated by selenium, even for google?
No, nobody can actually see that you're using Selenium and not hand-operating the browser yourself with WebDriver. I'm not sure about the old Selenium RC, but it should be the same way. Here's how it works:
Selenium opens up a browser with a clean profile (or with a profile you selected)
Selenium is hooked up to the browser so it can steer it, control it. But the browser still does most of the work. Basically, Selenium replaces the user inputs to the browser, but not more.
You can easily verify this by reading the contents of the HTTP headers sent by your browser.
If you ever actually needed Selenium to be recognized by your server, you can use Browsermob-proxy and add a custom header to your requests.
All that said, there is one thing you must be aware of. While there's no way to detect Selenium directly, there can be some indirect clues picked up by the website you're visiting. Those usually include scanning for too many requests made in virtually no time - this might be an issue for you. Make sure your Selenium is behaving like a user.
EDIT 2016/04:
Apparanetly it is possible as https://stackoverflow.com/a/33403473/2930045 states that a company can do it. My guess - and it is nothing but a guess - is that they can run some JS that Selenium installs into the browser to operate.
Signs point to yes, sites are able to regonize that you are using Selenium.
Counter Example: www.stubhub.com detects and blocks my browser instance launched using Selenium while "normal" browsing done manually (not using the browser launched by the Selenium web driver) work with out issue.
See this stackoverflow question for additional details
Can a website detect when you are using selenium with chromedriver?