Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Enable cookie support after the SDK has been initialized
See original GitHub issueWe have a home page / with a cookie banner. We are not allowed to write cookies until the user consents. We initialize the SDK with isCookieUseDisabled=true. Once the user consents, we would like to immediately write the cookies so when they continue to the next page /sign-in, same session ID is used there.
We can call appInsights.properties.context.sessionManager.update() but there seems to be no way to set CoreUtils._canUseCookies to true once the SDK has been initialized.
Issue Analytics
- State:
- Created 4 years ago
- Comments:22 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
As part of the change that was just checked in, I’ve added some documentation on the readme but I thought here would also be a good location. Moving forward, cookie support will be based on the appInsights instance so enabling disabling after initialization will be simply a case of using. appInsights.getCookieMgr().setEnabled(value: boolean)
I’ve added support for the existing _canUseCookies, but usage is problematic in ES3 environments (won’t always work) and it’s still also global, so if you share an environment with another instance using this will affect other users. And for backward compatibility, disabling via this will still disable globally – even for instance based cookies
Seems like a bug. Will get this in to next release (2.3.1)