You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That is unexpected since the prerender-node middleware checks for WhatsApp as a substring of the incoming user agent (both lowercased before compared) So I would expect both of those requests to return a prerendered page.
I'm not able to reproduce this in local testing either. Using both of those user agents seem to return a prerendered page for me when testing a website of mine with prerender-node installed.
So when you use WhatsApp/2 is it just returning your javascript page?
Hi @thoop, I would assume the prerendered page is returned cause I can see the response on the Prerender server console when I share a link on my mobile (tried both and Android phone and Iphone):
2019-03-30T16:28:31.613Z got 200 in 13ms for https://www.activitree.com/
This is similar to the responses when I share from Whatsapp on my MAC, the only difference is that MAC Whatsapp and browser Whatsapp show the preview. You can experience that with this link https://www.activitree.com and I can confirm in advance that the Prerender server will have similar responses (all my routes are Prerendered already.)
Hmm, could it be possible that WhatsApp on mobile had a previously cached version of your page from before you installed Prerender? Otherwise, that seems like it's working as expected but WhatsApp just isn't showing the info properly.
I use the latest versions of node and server Prerenders.
WhatsApp/0, as I see it in the logs is for the mobile App and WhatsApp/2 is for both Web and OSX App (possibly Windows App too)
Will just link my comment into another Issue:
From the server log:
#168 (comment)
The text was updated successfully, but these errors were encountered: