Obsolete
Status Update
No update yet.
Comments
sa...@chromium.org
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
[Deleted User] <[Deleted User]>
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
va...@chromium.org
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
va...@chromium.org
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
rs...@chromium.org
Having the same issue:
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
[Deleted User] <[Deleted User]>
SAME ! - Google can't do sth working in 100 percent?
is...@google.com
same issue - Google Play services out of date. Requires 3159100 but found 3158130
Description
Steps to reproduce the problem:
1. chrome cannot accept unsecure cert when chrome is being controlled by automated test software, detail see attached file
2.
3.
What is the expected behavior?
chrome should accept the unsecure cert automatically
What went wrong?
$ chromedriver version
Starting ChromeDriver 80.0.3987.106 (f68069574609230cf9b635cd784cfb1bf81bb53a-refs/branch-heads/3987@{#882}) on port 9515
In the older version chrome can accept unsecure cert automatically, like 77.0.3865.120
Did this work before? Yes Not sure the latest version it worked but the version 77.0.3865.120 worked
Chrome version: 80.0.3987.122 Channel: stable
OS Version: fedora28
Flash Version: