Hey Osama,
It's good to see you back.
Thanks for pointing this out. I'm guessing it's got something to do with how the content is passed from the cookie to Next.js' preview system.
I'll make a note to add this is the next.js preview documentation. I'll also confirm with the team about why exactly this breaks it.