Whoops! We couldn't access this Tweet.

[razbakov]

I am getting following error in console: A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver 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 and .

[robsonsobral]

This looks like a twitter issue. Have you tried to embed the same embed manually on a pure HTML to see what happens?

[razbakov]

If I go to my tweet and click embed I am getting this code, which works:

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Learn how to moderate any meeting in effective way<a href="https://t.co/SHkh1rmVi2">https://t.co/SHkh1rmVi2</a> <a href="https://t.co/BpD6Q4ylpb">pic.twitter.com/BpD6Q4ylpb</a></p>&mdash; Alex Razbakov (@razbakov) <a href="https://twitter.com/razbakov/status/997392437189505024?ref_src=twsrc%5Etfw">May 18, 2018</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

This doesn't work if do:

<Tweet id="997392437189505024" />

[JuniorNunes7]

Same error here!

Edit--

I solved it. In my case the problem was the JavaScript string cast, look:

I am inserting the tweet id in my database like a big integer:
1259820671011639297

When I took it on JavaScript I was doing the cast, like:
String(1259820671011639297)

But the JavaScript gets lost and round this to:
1259820671011639300

I do the cast in PHP and it works fine, but I will change the type of database to store this ID like string, I guess it will have less chance of bring me problems later.

OBS.: Sorry for my bad english.

[nmarseaud]

Made a similar mistake
If you fetch tweet ids via the API, make sure you use the "id_str" and not "id"