We're tracking this issue here.
We're tracking this issue here.
Hi. Responding about the preview issue, here's one of our repositories as a reference: https://stronger.prismic.io/
I am facing the same issue. Our repository is https://pageport-playground.prismic.io/
Looking forward . . . thanks!
Here are some insights what I see in the browser. Maybe it helps:
This is in Chrome:
This is in Firefox:
Prismic toolbar is also empty in Chrome and Firefox:
Sure, here's the screenshot of my cookies on local and production site, with io.prismic.preview highlight:
Hope that helps. I'll be following the issue via the link you're sharing too.
Let me know if you need any else info. Thanks!
Adding some additional context here for reference.
I recently created a new repo and used the same stack to reference prismic as my older repos, the new repo works as expected for previewing content. So, this preview issue only seems to occur on older repos, possibly the ones that were migrated from the previous version of the toolbar.
When inspecting the cookies between the two repos/sites, I'm not seeing "io.prismic.previewSession" in the older repo which the preview functionality is not working.
this issue has been openned for more than 10 days now, and at this time we have no visibility on its resolving status.
As it is an everyday feature used by our integration team, we are really concerned regarding this.
Could you give us updates on this resolving ?
Do you have any idea how long the fix will take to be deployed ?
Any idea of a workaround ?
We apologise for the delay, our dev team are still investigating the issue and for some users we are suspecting this issue:
A cookie associated with a cross-site resource at http://prismic.io/ was set without the `SameSite` attribute. It has been blocked, as Chrome now only delivers cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
Meaning that if that is the issue then it can be due to a change on chrome side that will require some changes of the way we create preview cookies.
But we are still investigating the issue that the other users having, and we let know if have any updates.
I tested the preview this morning. And out of nothing it works again for me. Did not change anything regarding the preview.
So I am happy that it works again. But it's a pity to not know why, or what the problem was.
Cheers and good luck with the further investigations
we are experiencing the same problem on Firefox, so I don't think it is a Chrome side issue.
And for the record, we have a problem on one repo, on the other repo it works fine.
But thanks for the update
I have 3 different repos with this problem occurring.
Using v4, nothing loads on localhost:8000
On live URLs I'm getting constant refreshing. Which is slightly different to what i had before which was just a blank page.
Same issue here. All I can add is that old browser sessions with a cookie still work but starting a new preview in incognito doesn't generate the io.prismic.preview cookie.
May I have the repository name with the issue (in a private message if necessary)?
We are still investigating the issue and we have narrowed down the cause to a few possibilities, we need to gather some impacted repositories to test the proposed fix.
So we've identified the issue and are working on resolving the problem. We will update you once this is done.
Thank you for your patience and understanding.
We've deployed a fix and we are now adding it to all your repositories. We'll let you know when this is done. If you haven't done so yet, please share your repo URL so we can make sure we deploy the fix for you.
Great, thanks. I DM'd you just in case. Are you able to give us a bit more info of what caused the bug for the more curious among us?
We introduced a change in the way we manage sessions a few weeks ago that prevented the preview session to be triggered properly. This was done as part of more important work to improve the login experience.
The progressive deployment is explaining why some people faced the issue in a progressive way and not all at once.
Thanks for the info, useful to know