Tealium Andriod library and tags with cookies

[thomas_annerel]

Dear, We are testing Tealium andriod sdk for our native Xamarin App. We have a custom tag that set a cookie. We notice that on some Android devices this cookie isn't set. I think we can solve it with putting this in our native app: CookieManager.getInstance().setAcceptCookie(true); Any one a better idea? Kind regards T

[brian_kranson]

Thomas Thank you for taking the time to reach out to us. A request has been put in to our Engineering team to see what the best approach is. Please standby for a response.

[chad_hartman]

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).

[thomas_annerel]

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

[chad_hartman]

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.

[thomas_annerel]

Chad, Can you not build it into the component and put it as a config setting so that we can also use 3th party cookies in the webview (for this one we need a reference to the inner webview) Kind regards Thomas Annerel

[chad_hartman]

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%...)?

[thomas_annerel]

Indeed, The problem is that alot of tags still use persistant cookies and third party cookies. I'm even not sure that persistant cookies are kept over app restarts.

[larhan]

Did you get any progress on this? I seem to be having the same issue, none of our tags loaded retains cookies which really mess with our external tools depending on it.

[craig_rouse]

Hi @larhan. You need to make sure you have followed this guide to enable cookies on Android: https://community.tealiumiq.com/t5/Mobile-Libraries/Mobile-110-Getting-started-with-Android-amp-Andr...

There is no additional config required on iOS - all cookies are enabled by default.

Let me know if you need further assistance.

Craig.

[larhan]

Thanks Craig,

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:)

/Lars

[craig_rouse]

You're right @larhan. I will log this internally and see if it's possible.

[larhan]

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:)

Thanks

/Lars

[craig_rouse]

Hi @larhan,

The only reason this would happen is if they have missed the cookie enablement code when they initialise the Tealium library. If it's not missing, then it hasn't been implemented correctly.

To avoid confusion, we are considering changing the default behaviour back to having cookies enabled by default, as this is the most common scenario. I'm not sure exactly when this will be released, but I expect that it should happen early in the new year.

If the agency can't get it to work, please contact support.emea@tealium.com, and I can set up a call with them to troubleshoot.

Thanks and Merry Christmas,

Craig.