You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the calendar quickstart and behaviour is different on Safari vs. other browsers (Chrome, Firefox).
After signing in successfully, I can see the calendar entries.
After closing the browser I expect not to have to log back in.
Actual Behavior
In Safari (MacOS and iOS), I am forced to authenticate each time the browser session expires (60 mins) or after quitting the browser.
In our web application this is causing us considerable problems because Safari is forcing the user to sign in after the session expires (60 mins).
This is resulting in considerable friction and poor user adoption. If all the user wants to do is check the calendar (via our app) then they don't need the extra steps of signing in again. This is especially tedious on a mobile device.
I researched as best I could and
After clearing Safari -> Preferences -> Privacy -> Manage Website Data... -> google & "mywebsite" -> Remove the problem went away for a short period.
On the iPhone you can't clear cookies for a subset of sites so this is unacceptable but likewise the problem reappeared on our test devices.
Also, it appears that the login authentication (perhaps) is being saved in persistent storage as when I look in Local Storage on Firefox, I see this created under https://accounts.google.com after authorisation.
handleClientLoad (testauth.html, line 44)
initClient (testauth.html, line 52)
initClient.then (testauth.html, line 59)
updateSigninStatus false (testauth.html, line 78)
Expected Behavior
I'm using the calendar quickstart and behaviour is different on Safari vs. other browsers (Chrome, Firefox).
After signing in successfully, I can see the calendar entries.
After closing the browser I expect not to have to log back in.
Actual Behavior
In Safari (MacOS and iOS), I am forced to authenticate each time the browser session expires (60 mins) or after quitting the browser.
In our web application this is causing us considerable problems because Safari is forcing the user to sign in after the session expires (60 mins).
This is resulting in considerable friction and poor user adoption. If all the user wants to do is check the calendar (via our app) then they don't need the extra steps of signing in again. This is especially tedious on a mobile device.
I researched as best I could and
Safari
->Preferences
->Privacy
->Manage Website Data...
-> google & "mywebsite" ->Remove
the problem went away for a short period.Also, it appears that the login authentication (perhaps) is being saved in persistent storage as when I look in
Local Storage
on Firefox, I see this created underhttps://accounts.google.com
after authorisation.It is created also on Safari but on Safari it doesn't persist after quitting where as on Firefox it does (as it also does on Chrome)
JavaScript Console Output
There are no errors but I added simple
console.log
messages in each method in to track the flowFirefox (working as expected) after first authorising and then quitting the browser
Chrome (working as expected)
Safari (not working)
Specifications
Chrome 78.0.3904.97 (Official Build) (64-bit)
Firefox 70.0.1 (64-bit)
Safari Version 13.0.3 (13608.3.10.10.1)
Mac OS 10.13.6
The text was updated successfully, but these errors were encountered: