Google chrome does not start when running through Twist with Seleniumn - google-chrome

Where i work uses Throughworks Twist 2.2 with Selenium for testing automation. For some odd reason on my particular machine the chrome driver starts but does not load chrome. The console reports no errors and i have no feedback on which to progress with. I installed Twist in the exact same way as everyone else here and it works for them. Twist will run with firefox for me but it is not as reliable as chrome and really impinges on development. The Twist site is typically useless source of information.
I'n not expecting answers but would appreciate any hints as to where i can start looking into this.

Turns, out Chrome driver was trying to launch a Chrome version installed under another user account, that was probably out of date. Delete old user profile and it works.
It would be good to find out where Chrome Driver gets this config from.

Related

Dev Tools Crashing on Chrome Version 50.0.2661.102 m

So i have the following problem.
Any time i click on a request to view the headers/payload/response
i receive a not responding window.
If i wait ~2 minutes it works.
So what i receive here is a developer tools not responsive status when working on local machine.
I tried to re-install chrome. Nothing changed.
Current Version is: Version 50.0.2661.102 m listed as up to date.
Is there any possibility to get some logs or did anyone faced the same problem?
I think it can be relevant if i show what extensions i have installed.
But i tried to enable/disable them and nothing changed.
And i get the same comportment in incognito mode too.
Later edit: I somehow identified the problem. Idea is that chrome is trying to display the cookie (request headers) which was 18k characters long and it looks like this is slowing a lot developer tools and sometimes make him crash.
I just saw that in Mozilla cookies are limited to a couple of characters (display perspective) and after that they show ...
I can't find any known issues regarding this crash, so here are a couple of steps you could take:
Use the Chrome Cleanup Tool and see if that helps.
Fully clean and re-install Chrome (including deleting user folders). If it works after that, you can slowly add extensions and plugins back and see if any reintroduce the problem.

How to test mobile chrome's "save to homescreen" prompt

I'm resurrecting an old project of mine as a way to learn some new stuff.
I'm doing this code lab from IO Add Your Web App to a User's Home Screen.
Is there any way, other than connecting a phone and waiting a lot, to test if users will be shown the prompt below?
I've tested it with Lighthouse and all tests come back green, but I've never seen the prompt. It feels very random at the moment.
The answer to This question puts the stuggle into perspective:
The user has visited your site twice over two separate days during the course of two weeks
Does that mean I need to wait 2 days between changes to see if it worked?
Enable chrome://flags/#bypass-app-banner-engagement-checks and you will see the banner as long as you have a manifest (configured correctly) and are on HTTPS and have a service worker.
Increasing Engagement with Web App Install Banners
anshulix has correctly answered the question, but I thought I'd put in a more verbose answer.
To remove the waiting and other requirements for the save to homescreen prompt, then you need to enable a flag.
Enable chrome://flags/#bypass-app-banner-engagement-checks and you will see the banner as long as you have a manifest (configured correctly) and are on HTTPS and have a service worker.
Which comes from Increasing Engagement with Web App Install Banners
It's important to remember that you are setting this flag on the mobile browser, not on your desktop browser. For some reason this didn't occur to be for a while!
You also need to restart mobile Chrome for the flag to take effect. If you've got your tabs mixed in with your other apps, this can be tricky because you need to hunt down all the tabs and close them. (Or find a better way to close Chrome.)
I found it much easier to do this debugging in Chrome Dev, rather than regular chrome because a) I know it's got the latest fixes in it, and b) because I only have 1 tab open, so it's easy to restart the browser.
If you are doing remote inspection, there is an issue about the messages that come up in the console. In Chrome 50 you get:
App banner not shown: could not determine the best icon to use
This doesn't seem to be true; in more recent builds—e.g. mobile Chrome 52—save to desktop works just fine. It's a disconcerting but useless error.
As a bonus helpful thing, realfavicongenerator does an excellent job of generating all the icons and the manifest file that you need.

Allow multiple instances of Google Chrome?

Disclaimer: This may be a better question on SuperUser, but my use
case matches SO.
I'm trying to develop an Angular app on my local computer; I'm not yet ready to set up a webserver or anything like that. I'm loading some JSON configuration files from the same directory, and I'm running into Origin Policy issues (which was expected).
I know that programs like gChat can run multiple instances with the /mutex flag (I think that's it, it's been a while since I tried that). Is there any such provision for Google Chrome? Basically, I'd like to run Chrome as my main browser for everything I do, and then open a separate instance with lowered web security for testing purposes.
Thanks!
You can bring up a development web server, serving data from the current working directory, using:
python -mSimpleHTTPServer
This doesn't directly answer your question, I know. But hopefully it's even better than a direct answer. :)
I found a solution to this - although Chrome won't let you run multiple instances, you can run Chrome and Chrome Canary side-by-side simultaneously. So now, Chrome is my main browser, and Chrome Canary (with the --disable-web-security) flag is my testing environment. So far, I haven't had any issues with discrepancies between the browsers.

Making Google Chrome leave itself alone

Let me preface this question by saying: It's crazy. I know it is. But the requirement is not mine, it's someone else's, and I'm trying to honor it.
I need to install a months-out-of-date version of Google Chrome so I can run repeated tests against it. But it's proving to be surprisingly difficult to turn Chrome updates off.
I did the trick of disabling the "Google Update" plugin in chrome://plugins. After that, I uninstalled Chrome and installed the old version. I double-checked that the version was the old version and that updating was non-functional ("error 3"). I didn't even see "Google Update" listed in chrome://plugins at all after this. So I thought I was good.
Then just now, I fired up Chrome to look at it again, and it was back to the newest version!
Is there something I overlooked? Are they doing some kind of black magic here?
Windows
For Microsoft Windows, here is the simplest and lowest-impact solution I have found.
Create a text file with these lines:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update]
"AutoUpdateCheckPeriodMinutes"=dword:00000000
"UpdateDefault"=dword:00000000
Save it to a file ending with ".reg" somewhere on your desktop. Double-click it to install new registry keys.
This disables automatic updates, and when you open "About Google Chrome" from the tool menu, you get the helpful message "Updates are disabled by the administrator."
Mac
(Instructions anyone may want to add for Mac OS can go here...)
Don't do this.
Really. I wasn't kidding. Updates are important.
See #1.
You're still here, so I can only assume that you're crazy enough to really want to turn off updates: http://support.google.com/installer/bin/answer.py?hl=en&answer=146164 explains how you can disable updates via policy. Editing registry entries locally should be effective.

Chrome 22 Developer Tools - Global Sources Search not working right (ctrl-shift-f)

this morning I noticed my Chrome updated to Chrome 22 and that the search in the top right has been removed and can now be accessed with ctrl-f.
I also noticed that ctrl-shift-f is no longer working as expected... (but this is inconsistent)
The global search has been a huge time saver for me, and now sometimes it doesn't work until I've viewed a script at least once.
For example, I have 5 scripts that I know all contain "fn_init"
I search for fn_init and nothing comes up.
I open one of those scripts and then ctrl-shift-f again, and finally get a matching result for just the one file...
Is this working as intended? Am I missing an option or something? My dev tools config options are:
General
Disabled cached
Sources
Show folders checked
Search in content scripts checked
Also: how can I install an older version of Chrome and stop it from updating automatically?
To get an older version of Chrome your best bet is to find a build of Chromium from https://chromium-build.appspot.com/p/chromium/console however if this if for devtools stability you are missing out on a lot of new features and bug fixes.
As for Search across all files it is still there and CTRL-SHIFT-F on Windows and CMD-OPT-F on Mac. See Addy Osmani's post https://plus.google.com/115133653231679625609/posts/e4W2kdrFJY9
If you find issues as bugs, it is better to raise the issue on http://crbug.com/new as it will get direct attention from the engineering team there.