You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by GitBox <gi...@apache.org> on 2019/08/21 09:27:35 UTC

[GitHub] [cordova-android] th3hamm0r commented on issue #802: Cookies not stored on first application launch

th3hamm0r commented on issue #802: Cookies not stored on first application launch
URL: https://github.com/apache/cordova-android/issues/802#issuecomment-523376472
 
 
   I've the same issue, but actually it looks like after a fresh install or a data wipe, cookies which are set often don't remain after a force close of the app. This does not only happen on the first start, but often also on subsequent starts.
   
   For example:
   1. Fresh start after a data wipe
   2. In our case a privacy popup inside an iframe sets some cookies.
   3. Force close the app
   4. The cookies do not exist anymore. New cookies are created.
   5. Force close the app
   6. Again, the cookies do not exist anymore.
   
   Only after some time navigating through the app and using some other iframes for this domain, the cookies seem to stay. But maybe the reason for the remaining cookies is not because of the user's navigation. I really don't know...
   We've reproduced this with several devices from android 5 to 9, and also with the chromium 77 engine.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org