I have installed termux API from the Google Play store and in the termux app with pkg install termux-api on my Nokia 2.3 (Android 10) but when I try a simple command like termux-torch on, it just "hangs" there and does nothing.
Anything I can do to fix this problem?
1st: use 'pkg' not "apt"
pkg update
pkg upgrade
pkg install termux-api
run:
For on: termux-torch on
For off: termux-torch off
Download
https://play.google.com/store/apps/details?id=com.termux.api
And give it all permission
here is the fulfilled solution to your problem!
Make sure you have the f-droid version of termux installed on your device because the playstore version of this app has been stopped their updates and closed some of their reposetries. That's why you can't do anything more than basics on that version of application.
Make sure you have installed the termux API(application form) from playstore or any other source. The command
pkg install termux-api
Just install the API handler which termux needs to connect with the API application, but you must need to install the termux API application install first.
After installing the API give it all the permission.
Hope it'll help you to fix your problem. Happy coding ; )
Download the Termux API on Fdroid, then install with the command:
pkg install termux-api
and then type:
termux-torch on.. enj
It's just that the team is not updating termux in playstore. They have an updated version in FDROID APP. So you have to download fdroid. Go to appstore, then download the termux from there and you're good to go.
Has anyone successfully installed and used C++ on Jupyter Notebook on a windows machine? The installation instruction here never worked for me.
conda install -c conda-forge xeus-cling
gives me
"PackagesNotFoundError: The following packages are not available from current channels:"
If anyone has succeeded in installing on Windows, could you please share your instructions? Thanks.
The "issue" is that conda-forge/xeus-cling isn't available for Windows (yet?) (as indicated on this page of conda-forge/xeus-cling on anaconda.org). You can instead use gouarin/xeus-cling (you still have to have the compatible environment, though). Of course, the online C++ Jupyter Notebook is available too.
I am getting the below error while sending keys.
Result Message:
System.InvalidOperationException : unknown error: call function result missing 'value'
(Session info: chrome=65.0.3325.146)
(Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 10.0.14393 x86_64)
I have updated the chrome driver to 2.36 but still my code search for 2.33?
Any idea ?
I've gotten the same error, please download the last ChromeDriver version and/or update chrome browser version and it will be working fine :)
https://chromedriver.storage.googleapis.com/index.html?path=2.36/
After updating the Google Chrome browser to Version 65.0.3325.146 (Official Build) (64-bit), I'm also encountered with the same error
while sending values to the input field, here's the error message...
selenium.common.exceptions.WebDriverException: Message: unknown error: call function result missing 'value'
using Chromedriver 2.32 and Google Chrome 65.0
As I did some research on the same, I found a recent commit on Google chrome v65 changelogs which help me to resolve the issue.
Solution:
Update Google Chrome to latest stable version (in my case it's v65 on 9/mar/2018)
Download and configure latest chromedriver (v2.36).
For configuring chromedriver (on Ubuntu) follow these steps...
Extract the downloaded zip file.
Copy the extracted chromedriver file to /usr/local/bin or to the location where you usually store the executable binaries.
Add the same path (where you place the chromedriver file) to environment variable PATH as
export PATH=$PATH:/usr/local/bin
For testing the installation, restart the terminal and type this command
chromedriver --version
it would show the version of chromedriver that you just installed.
Note: If the chromedriver already installed and configured then just replace the existing driver file and If you don't know where the Chromedriver binaries already stored then try to find the file using following command
sudo find -H / -type f -iname chromedriver
It is because of the update of chrome browser version from 64.xx to 65.xx
Now you have 2 options to run your tests successfully.
Downgrade your chrome browser to previous version and with the old chromedriver which you have now.
Upgrade your Chromedriver to 2.36 version with the updated Chrome browser.
visit https://chromedriver.storage.googleapis.com/index.html?path=2.36 and download the new chromedriver.
Option 2 is better.
Replace your ChromeDriver.exe with latest version.. Same can be downloaded from Google easily.
Also its better to get it done automatically by using webDriver manager as explained below -
1. Add Mvn dependency to your project POM:
<dependency>
<groupId>io.github.bonigarcia</groupId>
<artifactId>webdrivermanager</artifactId>
<version>${webdrivermanager.version}</version>
<scope>test</scope>
</dependency>
Now in your Browser instantiation class instead of using traditional way to create driver i.e. by using System.setProperty(See belwo)...
System.setProperty("webdriver.chrome.driver","src/test/resources/drivers/chromedriver.exe");
Use below approach:
WebDriverManager.chromedriver().setup();
webDriver = new ChromeDriver(chromeOptions);
And that's all, you are done!
Use below links for your reference-
What is Browser Binary Manager how to use it for Selenium
or chkout git project for same-
https://github.com/bonigarcia/webdrivermanager#webdrivermanager-as-java-dependency
Need to update chromedriver :
In console, run: chromedriver-update 2.36
The error says it all :
System.InvalidOperationException : unknown error: call function result missing 'value'
(Session info: chrome=65.0.3325.146)
(Driver info: chromedriver=2.33.506120
The error clearly complains about InvalidOperationException
Your main issue is the version compatibility between the binaries you are using as follows :
You are using chromedriver=2.33
Release Notes of chromedriver=2.33 clearly mentions the following :
Supports Chrome v60-62
You are using chrome=65.0
Release Notes of ChromeDriver v2.37 clearly mentions the following :
Supports Chrome v64-66
Your Selenium Client version is unknown to us.
So there is a clear mismatch between the ChromeDriver version (v2.33) and the Chrome Browser version (v65.0)
Solution
Upgrade Selenium to current levels Version 3.11.0.
Upgrade ChromeDriver to ChromeDriver v2.37 level.
Keep Chrome version in between Chrome v64.x-66.x levels. (as per ChromeDriver v2.37 release notes)
Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.
Use CCleaner tool to wipe off all the OS chores before and after the execution of your test Suite.
If your base Web Browser/Web Client version is too old, then uninstall it through Revo Uninstaller and install a recent GA and released version of Web Browser/Web Client.
Execute your #Test.
If you are on Mac:
brew upgrade selenium-server-standalone
brew upgrade chromedriver
if the above two are not installed:
brew install selenium-server-standalone
brew install chromedriver
I'm running Protractor and have encountered the same issue.
The solution in my case was rather simple.
$ npm update protractor -g
$ webdriver-manager update
If you are on the latest stable Google Chrome (e.g. 67) I recommend to:
brew uninstall chromedriver
brew tap homebrew/cask
brew cask install chromedriver
These set of commands will uninstall your current chromedriver, check for updates and install the latest found (e.g. 2.40).
Use xpaths instead of class names to locate elements
After updating chrome and its drivers it didn't helped me at all!!
I don't know how much it makes sense but it worked for me when i replaced class name with xpath. This is the xpath , i used to automate sending whatsapp message using python.
driver.find_element_by_xpath('//*[#id="main"]/footer/div[1]/div[2]/div')
previously i Was Using
driver.find_element_by_class_name('Some class Name Here')
In my case the team I'm on points selenium to a specific chromedriver file we had. In order to get Selenium to use the updated chromedriver, I first installed it with brew and then created a symbolic link to point where Selenium looks for it:
brew install chromedriver
ln -s /usr/local/Cellar/chromedriver/2.36/bin/chromedriver /path/where/selenium/expects/chromedriver
On the chance this might be helpful to someone I needed an additional step:
I am on MacOS X. I did
brew upgrade chromedriver
bundle exec chromedriver-upgrade
I have the chromedriver-helper gem installed, but it is stashed and requires the "bundle exec" prefix or the shell can't find the command.
The above fixed my problem.
As mentioned by others, the latest chromedriver did the trick for me. In case you downloaded the driver manually and want to tell appium to use the new chromedriver you can do so by this command:
appium --chromedriver-executable /path/to/driver/chromedriver ....
I'm running Protractor (webdriver-manager) with Selenium in a Windows environment, and I had to do the following:
webdriver-manager update --versions.chrome="2.36" (This downloaded the new Chromedriver to the right path but didn't enable it in protractor.)
Edit %userprofile%\AppData\Roaming\npm\node_modules\protractor\config.json and changed the chromedriver value from 2.32 to 2.36.
Delete my old chromedriver_2.32.exe from %userprofile%\AppData\Roaming\npm\node_modules\protractor\selenium for good measure (not sure if that was required.)
Or:
When another Chromedriver update became needed, I was no longer able to update this way. A configuration setting still expected the old path and filename, and I couldn't figure out where to change that setting. So I just renamed the latest chromedriver to "chromedriver.exe" and stuck it in C:\Windows\system32 (which is always referenced by PATH). Crude, but effective.
If you're using gulp-protractor plugin, make sure to update it as well.
I don't know if you're still on this, but I was receiving a similar error. I had the latest version of chromedriver in my PATH and Google Chrome was updated. I run Python 3.6 on windows 10 x64 bit. What I was getting trying to select a value from a dropdown menu on a webpage. The weird thing was, it would select the dropdown value correctly and the page would be updated nicely, but I'd receive that stupid error anyway and my script would freeze. So I just made an exception error handler for it, because like I said it selected the dropdown value correctly, so I just wanted to bypass that dumb error message:
# select by value
try:
select.select_by_value('100')
except:
pass
hopefully someone finds this helpful.
The issue is because of mismatch in chromedriver and chrome browser version.
Below link specifies the versions of chromedriver supporting the chrome browser's version.
http://chromedriver.chromium.org/downloads
I was following this tutorial for aws-php sdk Tutorial.
I Installed composer manually by using Composer-Setup.exe.
So when I am trying to install composer by clicking composer.json>Composer>install
this error appeared.
And if you have some proper tutorial for using php-sdk, please comment it here.
The tutorial is 2years outdated.
What you are trying to do is execute composer.
The correct way to execute composer in a windows based system is:
php composer.phar install
or
c:\path\to\php php composer.phar install
The approach of using ./ works with linux based systems after you have made the file executable. You generally do not require that in windows.
Go through the following links for details:
https://www.codementor.io/php/tutorial/composer-install-php-dependency-manager
https://www.codementor.io/php/tutorial/composer-install-php-dependency-manager
aapt missing MACOS Use the `android' tool to install the "Android SDK Platform-tools".
i have already use android download times.
but i can't find any usefully aapt file
only link to /usr/local/Cellar/android-sdk/r22.0.1/platform-tools/aapt
but under /usr/local/Cellar/android-sdk/r22.0.1/platform-tools/ only adb
the "aapt" tool was moved to the Build Tools folder. Run "android" and make sure you install the build tools (18.1 is currently the latest one).
also see this other post:
Android Maven Could not find tool 'aapt'
Run the android command and ensure that the SDK tools for your target platform are up to date. It is possible that you updated the SDK but not the build tools.
Hope that helps.
The android tools from brew expect version 17 of the SDK Build-tools to be installed.
I had a similar problem recently and found it to be an error with my HomeBrew setup. I think HomeBrew was expecting a particular version of the build tools that I didn't have.
I found that updating HomeBrew
brew update
gave me a new error which was much more informative:
It appears you do not have 'build-tools-19.0.3' installed.
Use the 'android' tool to install them:
android update sdk --no-ui --filter 'build-tools-19.0.3'
Unfortunately the filter in the suggested command didn't work but I found I could install it manually through the UI by running the android tool and selecting the version HomeBrew was expecting.
See https://stackoverflow.com/a/16585846/440362 for correct answer. The file's directory has changed from tools to build-tools/