Tested the issue using #60.0.3112.107 on Pixel 7.1.1 and was unable to reproduce the issue.

@graham: Could you please provide us the details of you device and a screen cast of the issue which you're facing, that would help us in further triaging of the issue.

Thanks!!

I've been trying and I can't reproduce this with the developer tools in Chrome connected to the phone.

I added some debug logging into a server to test the issue.

I load the sign-in page of the web-site I'm testing against. Close Chrome and leave it closed for some amount of time over 1 minute (the exact amount of time I'm unsure of - immediately reopening Chrome tends to result in a request being sent on load of Chrome, while waiting seems to lead to Chrome skipping this request). Open Chrome again, note that no request is made to the server (key point). Attempt to sign in, and see that no cookies are sent in the request, leading to an inability to validate the form submission (comparison of form submission data with session contents stored in cookie fails due to no cookie).

See the attached log file.

Initial page load at 21:32:11 - note cookie/session populated.

After reloading Chrome, attempting to sign in at 21:35:21 - note authenticity token restored, while cookies/session are empty. Also notable is the lack of a request to the site in question, despite the "must-revalidate" cache-control being specified in the response.

What I find strange is that I can't reproduce this pattern once the Chrome developer tools are connected to the phone's browser. Interestingly, I can go through the steps (load the sign-in page, close Chrome, wait 1+ minutes, load Chrome, verify no request was made to the server), and then connect the Chrome developer tools, see the session cookie is set as expected, and successfully submit a login request.

Let me know if I can provide any more useful information. It's a real pain that I can't reproduce this with the developer tools, or I'd just screencast the session that way, which would make it a lot simpler to see what is happening.

Deleted: 2017-08-28 Chrome test log 3.2 KB

2017-08-28 Chrome test log 3.2 KB View Download

Sorry I forgot to give the details of the device. It's a Samsung Galaxy S6 (SM-G920W8) running Android 7.0.

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested the issue using Chrome Stable# 62.0.3202.73 / 62.0.3202.84 and Chrome Canary# 64.0.3262.0 using Pixel (Android 8.0.0) & Samsung SM-J710F (Android 7.0.0) and could not reproduce the issue.

@graham -- Could you please re-check on the latest versions and provide us the update.

Thanks in Advance.

Hi graham@, were you able to try this the latest version of Chrome, as requested in comment #8?

This is still happening for me in Chrome 62.0.3202.84 on Samsung SM-G920W8

Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Request you to check the issue on latest Chrome #63.0.3239.111 and update the behavior?

Thanks!!

Closing this issue for now, if you're able to reproduce the issue with the latest Chrome, feel free to re-open the bug.