I am getting the following error when attempting to run an Appium script on the Chrome Version 65:
selenium.common.exceptions.WebDriverException: Message: unknown error: call function result missing 'value'
(Session info: chrome=65.0.3325.109)
(Driver info: chromedriver=2.33.506106 (8a06c39c4582fbfbab6966dbb1c38a9173bfb1a2),platform=Mac OS X 10.13.4 x86_64)
I have found that the chromedriver version needs to be updated but I can't find a way to successfully do this.
So my question is how do I upgrade the chromedriver version to the latest version?
So first, with each update to Chromedriver there is an increase in the minimum supported version of Chrome => older devices are often unable to be automated with the bundled version.
So its not appium/chromdriver compatibility, its your device browser/ chromdriver versions compatibility check.
To check versions compatibility you go look here
When you figure out whats version works for you, run:
npm install appium --chromedriver_version="2.37"
This version supports Chrome v 64-66
The subjected issue can be resolved (In my case this works) if we pass the additional argument while starting the appium server in the local system.
CLI Command: appium --allow-insecure chromedriver_autodownload
The script will automatically search for the newest chromedriver version that supports the given browser/web view, download it (the hash sum is verified as well for the downloaded archive) and add to the chromedriverChromeMappingFile mapping.
For more details please refer to the official documentation of appium: Compatible chromedriver issue fixes options
Hope this helps!
Thanks.
Please download the latest chromedriver from here :
https://sites.google.com/a/chromium.org/chromedriver/downloads
Upgrade your appium server, appium java client to latest version.
Related
Can some one help where our app is not showing in Appium inspector and even not working for Automation code in intellij after upgrade to Flutter driver version 3.0
getting error: Unable to create a new remote session. Please check the server log for more details. Original error: An unknown server-side error occurred while processing the command. Original error: Cannot read property 'match' of undefined
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
To fix this, Upgrade to appium-flutter-driver v1.7.0 with Appium 2 (2.0.0-beta.43 is the latest when I'm posting this)
Start Appium server using the command appium -p 4726 --base-path /wd/hub as sometimes starting server with default port was not working fine!
If you are not on Appium 2 already, check this guide for migration, I found it helpful
https://www.headspin.io/blog/migrating-to-appium-2-0-part-1-capability-prefixes
https://www.headspin.io/blog/installing-appium-2-0-and-the-driver-and-plugins-cli
My app was working fine until I did 2 small changes.
On Target runner in Xcode I enabled bitcode for the project.
I update the Android studio to the latest version.
Android Studio Bumblebee | 2021.1.1
Build #AI-211.7628.21.2111.8092744, built on January 19, 2022
Runtime version: 11.0.11+0-b60-7590822 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 12.0.1
GC: G1 Young Generation, G1 Old Generation
Memory: 1280M
Cores: 4
Registry: external.system.auto.import.disabled=true
Non-Bundled Plugins: Dart (211.7798), org.jetbrains.kotlin (211-1.6.10-release-923-AS7442.40), io.flutter (63.2.2)
After that When I run my flutter app on iOS simulator I'm getting this error.
Although I have disabled bitcode and tried again.I got same error. I installed and reinstalled cocapoads still same error. I don't know what causing this error. Can you help? please
Warning: CocoaPods not installed. Skipping pod install.
CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
Without CocoaPods, plugins will not work on iOS or macOS.
For more info, see https://flutter.dev/platform-plugins
To install see https://guides.cocoapods.org/using/getting- started.html#installation for instructions.
CocoaPods not installed or not in valid state.
Error launching application on iPhone 13.
UPD: Fixed in 2021.1.1 patch 1, see release notes here
This might happen because AndroidStudio doesn't know anything about $PATH provided in ~/.*rc files (.bashrc,.zshrc, etc.)
You can ensure by launching it from terminal:
open /Applications/Android\ Studio.app
EDIT: It's a confirmed bug in Bumblebee release
The workaround is to add missing flag:
chmod +x /Applications/Android\ Studio.app/Contents/bin/printenv
You have to do it only once
Open terminal run -> chmod +x /Applications/Android\ Studio.app/Contents/bin/printenv
Try again...And it should work.
I got an exception on the pod availability check.
which pod
It seems that $PATH env for the updated studio is not picked properly. (you can check it by enabling verbose logging mode on the flutter plugin).
Workaround is to start Android studio from the terminal:
open /Applications/Android\ Studio.app
Updated:
Android Studio Bumblebee (2021.1.1) Patch 1 fixes this issue.
I came across this problem too using Android studio on Apple Silicon MacBook launching from command line or directly both failed
I updated the ruby version to 2.7.3 using rbenv, and then it worked from the command line.
open /Applications/Android\ Studio.app
Note: default macOS system ruby is version is 2.6.8, and there are some incompatible gems with this version
If the top voted solution doesn't fix this for you with the Bumblebee release, then you can try the beta Chipmunk release of Android Studio.
I am running the M1 Mac and this version 2021.2.1 Beta 1 is able to run the flutter apps from the toolbar correctly.
I've searched all of solutions, and current post's answers do the trick. But basically it seems like flutter android studio(only lately-updated bumblebee version) plug-in triggers the pod error, since both xcode and android studio terminal run work just fine.
We might have to keep tracking this issue. Before flutter team gives a clear answer, i'm planning to use flutter run --debug, since terminal run provides "r" for hot reload and "R" for hot restart. Or we can also use open /Applications/Android\ Studio.app everytime.
I fixed it by running:
sudo gem install ffi
In my case i check $PATH variable and in this do not exist path to pod executable
Using MacBook Pro M1 with pod installed by brew
I am making an automation script to automate a Real SMartphone Android 8.1:
Environment
Python 3.7
Windows 10 64Bits
Build-tools 29.0.3
java version "1.8.0_241"
Appium 1.17.1
Node v12.15.0
sdkmanager 4.0.1
ADB (Android Debug Bridge) version 1.0.41
Version 30.0.3-6597393
When I run my script, I get these error message:
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
--> We can't open Instagram. Please check if device is connected. Let's try again!
Message: An unknown server-side error occurred while processing the command. Original error: Performing Push Install
C:\Users\Nino\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk: 1 file pushed, 0 skipped. 87.8 MB/s (470052 bytes in 0.005s)
Appium log file:
https://github.com/gauthierbuttez/public/blob/master/appium_issue04082020.log
What I've tried:
I added this desired capability:
desired_caps['remoteAppsCacheLimit'] = 0
It didn't help.
I reset factory my Android device but it didn't help.
Does anyone already faced this issue?
Try to add noSign: true to capabilities. It might help.
I also suggest manually removing Appium Settings and Instagram apps before starting a new session.
I followed Appium instructions to upgrade Appium version to 1.5 . But I observed below exception when I start a server from Appium UI (Appium.exe)
Launching Appium server with command: D:\Appium\node.exe lib\server\main.js --address 127.0.0.1 --port 4723 --no-reset --platform-name Android --platform-version 23 --automation-name Appium --log-no-color
> module.js:338
> throw err;
>
^
> Error: Cannot find module 'D:\Appium\node_modules\appium\lib\server\main.js'
Before starting appium server , I checked appium version & it is still 1.4.16.1
Has anyone tried to upgrade on win 64 machine ? Please suggest if any additional setting needs to be done before upgrading / starting server.
Simplest way to Upgrade Appium
Check checkbox from appium settings GUI for "Check for Updates"
Close Appium GUI and re-launch again OR
You will get a push/pop up as new market version released for Appium
Click on upgrade pop up and follow simple steps to upgrade
Appium GUI does not support version 1.5 currently.
https://github.com/appium/appium-dot-exe/issues/170
If you have installed appium using npm then you can easily upgrade appium to 1.5
Below is the command :
npm update -g appium
and if you want to upgrade to any specific version below is the command :
npm install -g appium#1.5.3
You can enter version number after '#' in the command
Following command automatically upgrade appium , internet connection should be require,
npm install appium
Install latest version of Node js application on windows and download and install latest version from Appium site.
Check your Appium version by running Appium application.
There are 2 types in Appium:
1. Appium GUI version
2. Appium Command line
To update appium GUI version, uninstall the older version and then download the latest version from https://github.com/appium/appium-desktop/releases and install.
To update the command line version run, npm install -g appium. It will automatically take the latest version and install it.
Now we can download the latest version(1.7.1) from the official website.
We Really need some help on this one:
We've Struggled with all the Apple Mumbo-Jumbo for the Last two months and can't seem to get our APP on the APPStore...
Right now my problem is after Validating the ARCHIVE compilation and sharing it.. in the Submit Process I Get -
"An error occurred uploading to the iTunes Store"
I Really don't Know what I'm doing wrong and don't seem to find ANYTHING on the Internet that solves the problem...
I've been stugling with this for over a week now... I've tried:
Creating a new Distribution Profile for Code Signing.
Checking All the Target Settings over and over.
Changing the FTP mode from Passive to non-Passive
Connecting from different networks
Reinstalling Xcode4
some other Work Arounds like Downloading the application Loader (Haven't installed it yet, but I Don't Know if I Should)
Please help us, what do you think could be the problem?
Thanks
Hernan
If you are unable to upload Apps to Apple and installed the JavaOSX update (April 3, 2012) this may help you regain your ability to upload Apps:
You can work around this issue by re-creating the old Java 1.5 symlinks:
cd /System/Library/Frameworks/JavaVM.framework/Versions
sudo ln -s CurrentJDK /System/Library/Frameworks/JavaVM.framework/Versions/1.5
sudo ln -s CurrentJDK /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0
Edit Oct 5, 2012 Oracle's Java 7
Elaborating on Hackmonford's comment below.
This exact error message also occurs with Oracle's Java SE 7 1.7.0_10 package installed. To resolve, open "Java Preferences" and either change the order to have Apple's Java SE 6 first, or untick Oracle's Java 7 while submitting to the app store. Verify your change by opening the Terminal:
prince$ java -version
java version "1.6.0_35"
I was having this problem this week, and installed the Java for OS X Lion 2012-002 update, and the problem cleared up. Resetting disk permissions had no effect.
This just happened again.
For OSX 10.8.2 users (does not have Java preference), the only way to fix this is to uninstall oracle jdk.
cd /Library/Java/JavaVirtualMachines
sudo rm -rf jdk1.7.0_09.jdk/
I had also a JavaVM / JRE issue. I have installed the JDK 7 preview from Oracle and that mixed up the upload process which told me the known "An error occurred uploading to the iTunes Store".
A quick check of /var/log/system.log (e.g. using tail in a terminal: tail -n 100 /var/log/system.log) brought up the following error message:
Java 1.5, 1.6, or 1.7 is required. Currently, java is the default java version. Please upgrade.
I had installed the MacOS Preview of JDK 7 directly from Oracle. To fix this issue, simply launch the Java Settings app in Utilities and uncheck JDK 7 from Oracle. Of course you should have an alternate JRE from Apple. See the screenshot how my configuration looks. The upload works for me now.
The odd thing is that the Oracle JDK isn't recognized as Java 1.7 by Apple. This seems like a bug.
UPDATE:
The GUI tool was removed from MacOS. Now, the only solution I know of is to remove the JDK 1.7 folder manually. See the JDK 7 docs how to do this:
Navigate to /Library/Java/JavaVirtualMachines and remove the directory whose name matches the following format:
/Library/Java/JavaVirtualMachines/jdk<major>.<minor>.<macro[_update]>.jdk
For example, to uninstall 7u6:
% rm -rf jdk1.7.0_06.jdk
A bit late, I know - but for anyone still having this problem - Look in your /var/log/system.log log file. In my case the problem was that the iTMSTransporter script (used by the Organizer when uploading the file) used 'awk', and I had to replace it with '/usr/bin/awk'.
Completely solved my problem.
Y.
Just in case this is useful for anyone else - for me it was that the Java JRE was not up-to-date. I checked the console and Application Loader was complaining
I had this problem today after installing latest XCode.
I fixed it by running software update and installing latest Java Update.
I tried the same thing as Hernan, but even with application loader 1.3 I wasn't able to upload.
I noticed that this has happened after installing OSx Lion and upgrading XCode to 4.1!
I followed Joe's tip and I found out that JAVA wasn't even installed.
Follow this blog entry:
Unable to Upload App to App Store
My mbp now run Xcode4.2(4D199) on Lion, I installed the latest java for Lion. And finally I sovled this issue.
Many guys said, he can used the old Application Loader app to upload the apps. so I guess the problem is the latest Application Loader app(2.4.1 (190)), and the fact told me I am right
Okie, in short words:
Here is the solution:
1.I hope you guys do not delete the old Xcode(4.1). We Should pick up the old version Application Loader app.
cd <Install Xcode app>/Contents/Resources/Packages
cp ApplicationLoader.pkg ~/Desktop/
Now, you get the ApplicationLoader package.
2.Install the old one.
Tips: you can remove the latest Application Loader app in path: /Developer/Applications/Utilities/ or just remane it.
That's All.
Hope this way can help you and enjoy the new Xcode4.2. Also hope apple developer can saw this problem and test the latest Application Loader app more.
No Problems submitting to AppStore on April 1st. Issue occured on April 9th. Installing the Java for OS X Lion 2012-002 update via Mac-OS software updater and rebooting the machine fixed it.
Just update to the latest JAVA at your Mac Software Update.
Here is the steps to resolve this issue:
To start with I had installed Oracles Java 1.7 JDK, which was really messing things up.
Went to Finder>Applications and entered in Search box - JavaAppletPlugin.plugin
Right clicked and removed to trash.
A check in Terminal for Java version still showed Java 1.7
my-imac:~ my$ java -version
java version "1.7.0_07"
Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
1. Finder>Library>Java>JavaVirtualMachines showed the 1.7 SDK (make note of exact name of the Directory name)
Just in case anything went wrong I copied the 1.7 SDK folder to my desktop before doing the next item
2. In terminal type
cd /Library/Java/JavaVirtualMachines
3. You should now be in that directory
sudo rm -rf jdk1.7.0_06.jdk (or whatever the exact name of the directory is in step 1.)
You may have to enter your administrator password
The directory should now be deleted and you can verify in Terminal by
java -version
Mine now showed "Java 1.6_xxx"
Went into Xcode Organizer and distributed my app to the iTunes store without a problem. Whoo,hoo!