Obsolete
Status Update
No update yet.
Comments
dt...@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
ch...@chromium.org
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
ph...@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
[Deleted User] <[Deleted User]>
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
ph...@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
ch...@chromium.org
same
[Deleted User] <[Deleted User]>
SAME ! - Google can't do sth working in 100 percent?
[Deleted User] <[Deleted User]>
same issue - Google Play services out of date. Requires 3159100 but found 3158130
ch...@chromium.org
Having the same issure:
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
sa...@chromium.org
API 18 (4.3) same issue
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
nh...@chromium.org
Same issue here.
ch...@chromium.org
Same issue here. How can i fix this bug?
is...@google.com
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
Description
Steps to reproduce the problem:
1. Set SameSite to 'Strict' for session cookies on your site. e.g. for Django:
SESSION_COOKIE_SAMESITE = 'Strict'
2. Log in to your site e.g. 'example.test'
3. Email yourself a link to a page that requires a login, e.g. 'example.test/admin'
4. Click the link in the email
What is the expected behavior?
Clicking on the link should require a login as the cookies will not be shared.
What went wrong?
Access is granted e.g. to '/admin' without requiring a login.
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 80.0.3987.106 Channel: n/a
OS Version: OS X 10.14.6
Flash Version: