Feature Request P2
Status Update
Comments
aj...@chromium.org <aj...@chromium.org> #2
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
sw...@chromium.org <sw...@chromium.org> #3
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
ya...@chromium.org <ya...@chromium.org> #4
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]> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
da...@gmail.com <da...@gmail.com> #6
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
ma...@chromium.org <ma...@chromium.org> #7
same
[Deleted User] <[Deleted User]> #8
SAME ! - Google can't do sth working in 100 percent?
pe...@google.com <pe...@google.com> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
ha...@google.com <ha...@google.com> #10
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
is...@google.com <is...@google.com> #11
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
pe...@google.com <pe...@google.com> #12
Same issue here.
pe...@google.com <pe...@google.com> #13
Same issue here. How can i fix this bug?
Description
Chrome Version : 81.0.4044.113 (Official Build) beta (64-bit)https://airhorner.com/
URLs (if applicable) :
Other browsers tested: N/A
What steps will reproduce the problem?https://airhorner.com/
(1) Open
(2) Open dev-tools
(3) Open Application
(4) -> Cache -> Cache storage -> select cache
(5) click on an item in the cache, eg /index.html
(6) notice that the 'Headers' show up in the pane below
(7) -> Service Workers
(8) Try to find the headers for the service worker...
What is the expected result?
I expect to be able to see what the headers were for the network request for the service worker.
What happens instead?
No way to do that...the only option it to attempt to reload the app with the dev tools already open, and then look in the network panel; but that is a different request...
Please provide any additional information below. Attach a screenshot if
possible.