Using geckodriver v.09,jdk 1.8,selenium-java-3.4.0,selenium-server-standalone-3.4,downloaded two mozilla firefox 46 and 53.but in control panel-->program folder only able to see mozilla firefox 53 version.Getting error for below code.
geckodriver v0.9.0 was released in July 2016. So last year. In the meantime, several Firefox versions were released, so most likely your geckodriver version is way too old to be able to work with Firefox 53.
One way to solve this is to update to the latest version of geckodriver, meaning v0.16.1. One note though, for v0.16.0 it's mentioned that you need Selenium 3.4.
You can see more here.
To answer the other question, regarding the Firefox version, this is what I'm doing to make it possible:
Install any FF version (even the latest one) and make sure you uncheck Maintenance Service (or something similar it's called)
Go to FF Options and disable the automatic updates
Uninstall Firefox (using the default options, without manually deleting anything)
Install the version that you need
Otherwise, even if you install an older version, it will automatically try to update and at the next restart it will be the latest version.
Related
I want to upgrade React Native Debugger from version 0.10.0 to version 0.10.2, but clicking to upgrade when the program itself prompts me isn't working because (as they indicate on their page), there's a bug that prevents this upgrade. People have suggested "manually" upgrading or using brew cask reinstall react-native-debugger. The latter doesn't work, so I was wondering how you go about manually upgrading a package like this?
You can go to the release page https://github.com/jhen0409/react-native-debugger/releases/tag/v0.10.2 and download the appropriate .dmg file (for MacOS) from there. Afterwards you can just install it like any regular .dmg.
Appium version 1.14.1 did not support chrome browser latest version 76 and higher.
I tried to find so many possible solutions but still, I'm not able to find any solution about this and finally, somehow I manage to downgrade chrome version in my mobile device and test run successfully.
I'm attaching an image of the error log here for better understanding.
Try explicitly specifying the desired chromedriver version during Appium installation:
npm install appium --chromedriver-version="76.0.3809.68"
For more information and troubleshooting tips see:
Using ChromeDriver
ChromeDriver on Android
appium-chromedriver
I've been using the React developer tools extension in Firefox for some time, they're great. But yesterday the tools stopped working. The Components tab is available, but it doesn't show any content - my React component tree is simply missing, the pane is blank.
I've tried uninstalling the extension, closing Firefox, and reinstalling the extension.
I've tried rebooting my machine.
I've checked the Components tab settings, everything looks OK.
I've tried reverting to an old version of my project, back when the Developer tools definitely worked.
Has anybody got any ideas? There's no error, and I can't think of any way to investigate what's causing the problem. I haven't found anything by web searching.
And I can't switch to Chrome, because the tools won't install on Chrome under Linux!
OS: Linux mint Cinnamon
Firefox version: 63.0.3 (64 bit)
Phew, got it working again! I'm posting what worked for me in case it helps anybody else.
I completely uninstalled Firefox and reinstalled it following these instructions:
https://www.fosslinux.com/13881/how-to-clean-uninstall-and-reinstall-firefox-in-ubuntu.htm
Then re-added the Developer Tools extension, and it is now working. Firefox is now at version 69.0.
I've installed PostgreSql, pgadmin4 came along with it first. It didn't work so I installed the latest version of pgadmin4 v4 again but still its the same. It was showing a fatal error message earlier which said "Failed to open the system default web browser. Is one installed?." After that, it somehow worked & it started in my IE when I set it as my default browser. I tried opening it in Firefox too setting it as default browser but the result was same.
It shows the following screen rather than the expected normal screen that should appear as soon as we start it.
To resolve the issue, use the Windows Registry Editor to reset the value of
HKEY_CLASSES_ROOT.css\Content Type
to
text/css
and then restart pgAdmin4.
Ref: https://www.pgadmin.org/faq/#6
Note: Use Chrome or Firefox latest version with pgAdmin4, IE11 does not support many latest HTML technologies, for example with IE11 you will not able to download the graphical explain plan.
Since I installed XCode 4.6, it keeps on downloading the Doc Set each and every time I open it. I've seen a lot of threads talking about this topic, so I tried to manually install the doc set in the Developper/Shared/Documenation/Docsets folder. But even with that, I opened XCode this morning and.... it started downloading the thing again. What can I do to make it stop ?
Click the link under Xcode->Preferences Click on Xcode 4.6 doc set you will see an installed location. click on that link and delete the file. In my case there was another Xcode 4.6 file I think it was called Xcode 4.6 Documentation set I deleted that as well.
I closed XCode and opened up again the told it to download it again and it took.
You should only have one Xcode 4.6 file in your list I had two and I don't know why. Might be something left over from the 4.6 beta.
Hope it help
Go to the "Xcode->Preferences->Downoloads" and unselect the check mark under "Check for and install updates automatically" in the "Documlentation" tab.
Downloading Fresh Doc
As the other answers suggest, Xcode is merely detecting, downloading, and installing new versions of the documentation available on the Apple servers.
Disable Auto-Download
As pablok said, if you don't like this behavior, disable the behavior by unchecking Xcode > Preferences > Downloads > Documentation > Check for and install updates automatically.
Fresh Doc Stored Outside App
One interesting twist is that the old versions are stored inside Xcode.app while the fresh downloaded versions are stored outside the app.
For example, in Xcode 4.6.3 on Mountain Lion obtained from the developer.apple.com iOS Dev Center, the Xcode 4.6 doc set is bundled with the Xcode app. That bundled doc set, according to the Finder, is:
Version: 509.12
Size: 268.4 MB
Location: …/Xcode.app/Contents/Developer/Documentation/DocSets
The newly downloaded doc set is:
Version: 511.5
Size: 286.8 MB
Location: ~/Library/Developer/Shared/Documentation/DocSets
So, two mysteries:
Why does Apple bundle doc inside the app but download new doc somewhere else?
After doing so, why does Apple leave the old doc in place? Why not delete it?
As an experiment, someday I will delete the original ones inside the app. I'm not suggesting any benefit (other than recovering storage space) nor am I saying there is no adverse effect.