08-20-2015 10:34 AM - last edited on 08-28-2016 11:05 AM by kathleen_jo
Hello Thomas, The method CookieManager.getInstance().setAcceptCookie(true); should suffice. We have read some issues surrounding the timing that method and WebView creation, so we've vended a config option of the same name in the Tealium.Config object of the latest version of the library (https://github.com/Tealium/android-library).
08-20-2015 11:29 PM - last edited on 08-28-2016 11:05 AM by kathleen_jo
Can you give more info around: We have read some issues surrounding the timing that method and WebView creation, so we've vended a config option of the same name in the Tealium.Config object of the latest version of the library (https://github.com/Tealium/android-library). Indeed we have seen some crashes in the app
08-21-2015 06:35 AM - last edited on 08-28-2016 11:07 AM by kathleen_jo
In terms of timing, the library will call CookieManager.getInstance().setAcceptCookie(...) after the WebView creation in light of http://stackoverflow.com/questions/17230757/how-to-enable-cookies-in-android-webview. If you are observing crashes involving the Tealium Library, we invite you to post issues in the GitHub repo or reach out to your account manager to get them resolved. Please be sure to supply steps to replicate and stack traces so we can swiftly resolve your issues.
08-24-2015 08:46 AM - last edited on 08-28-2016 11:08 AM by kathleen_jo
As of release 4.1.3 (https://github.com/Tealium/android-library/releases/tag/4.1.3) there's a config setting called "setAcceptCookie", but when you say 3rd party cookies are you referring to the Lollipop-introduced "setAcceptThirdPartyCookies" API (http://developer.android.com/reference/android/webkit/CookieManager.html#setAcceptThirdPartyCookies%...)?
I did find it. It would have been nice to have as a built-in feature, as I can imagine quite a few might overlook this as part as an implementation. I can hardly find a case where I would intentionally block the cookies from the WebView:)
Do you by any chance have any scenarios where this would not work? I have set up a small demo app and it works just fine, my cookies are persisted and transferred to both Tealium and GA with weeks of inactivity of my app.
However our agency duplicated my code over to our app, but it seems like the internal web view still drops the cookies. I can have the app running open, come back to my device 30 min later and I would receive a new GA cookie.
Both apps has been tested on the same device.
Any ideas are greatly appreciated, even just vague pointes I can take back to the agency:)
I'm interested in knowing the evolution of this topic over the years ...
I need to preserve the cookie value in the Android system WebView used by TealiumIQ in our app because the cookie changes (not only after killed the app but also while using the app) and I found a recent answer on StackOverflow .com which suggests using "CookieManager.getInstance().Flush()", but I think this change should be done in the Tealium SDK, right?