Closed dylanyoung-dev closed 10 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
sitecore-migration-game | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Dec 15, 2023 7:08pm |
Forgot this was the first time I implemented Engage, and Developer Portal was after. I learned on the Developer Portal implementation that if you enforce the cookie, then Vercel just doesn't work correctly, and you'd want the value to not be set (and then it works fine). And because I wasn't setting it, that's why I was getting that error of it not being configured correctly.
So long story short, this removes that requirement, so now this should work in all Vercel preview environments as well as in production.
To test, make sure you can go to the environment, make sure nothing extra is displaying that you wouldn't expect, and then go into the console and type
Engage.getBrowserId()
and make sure it returns an Id. If you would like to take that further, send it to me and I'll send over what it logged and confirm it made it into the correct tenant.