Mobile content not loading when tapping on shared article on Facebook.


Recommended Posts

On my phone (not that it probably matters, but is a HTC One M7 Google Edition), if I tap on a Neowin article in the Facebook app, Chrome opens the page, but none of the article specific content will load.

To make matters worse, if I clear Chrome's cache none of content for the entire page, including images, CSS and JavaScript loads either, except for the adverts which load fine.

If I tap the Neowin link at the top to go back to the homepage, find the article on the homepage and click it it loads correctly, almost as if some referrer checking is stopping the content from loading.

Attached are some screenshots showing the issue when cache is completely cleared and when viewing an article not previously seen.

post-2905-0-46857800-1426408199.png

post-2905-0-97504700-1426408213.png

Link to comment
Share on other sites

To clarify, you mean from the Neowin Facebook page? We updated the Facebook api to v2.0 (required from April) maybe something went wrong there :p If this is the case I will pass it on to Marcel who did the update on Friday morning.

Link to comment
Share on other sites

I mean from within the Facebook Android app, which I have set up to open web links in the default browser, not the one built into the Facebook app.

Everything seems to work fine from the Facebook mobile site.

Link to comment
Share on other sites

We don't have an Android (Facebook Neowin) app, so whatever you are using is unsupported and probably broke due to the API update on our end..

Link to comment
Share on other sites

  • 5 months later...

Like @HeyRatFans, I'm following Neowin on my Facebook feed. When I want to read any Neowin article, I will click on the article, and it pops up onto my Chrome browser with the full article.

@StevenP, this issue that HeyRatFans was facing has also been plaguing me for months after Neowin upgraded their site recently. The images do not seem to be rendering correctly on my Android Chrome. It just displays an "image-not-found" placeholder.

The workaround is to load neowin.net on Chrome for the first time, manually (as in physically type neowin.net on on-screen keyboard in Chrome app). Read an article. Then any subsequent Neowin articles referred from Facebook app will load the images correctly.

Perhaps the index page has a piece of code which prefetches some code beforehand. Once that code has been prefetched, any direct links to any articles in Neowin will load fine.

Link to comment
Share on other sites

Like @HeyRatFans, I'm following Neowin on my Facebook feed. When I want to read any Neowin article, I will click on the article, and it pops up onto my Chrome browser with the full article.

@StevenP, this issue that HeyRatFans was facing has also been plaguing me for months after Neowin upgraded their site recently. The images do not seem to be rendering correctly on my Android Chrome. It just displays an "image-not-found" placeholder.

The workaround is to load neowin.net on Chrome for the first time, manually (as in physically type neowin.net on on-screen keyboard in Chrome app). Read an article. Then any subsequent Neowin articles referred from Facebook app will load the images correctly.

Perhaps the index page has a piece of code which prefetches some code beforehand. Once that code has been prefetched, any direct links to any articles in Neowin will load fine.

Can you check if this still happens please? We think we have done a fix. 

Link to comment
Share on other sites

Can you check if this still happens please? We think we have done a fix. 

Good work, @StevenP. It loads perfectly fine now, although the image placeholders appeared on the thumbnails in the related stories section initially. But subsequent articles were ok. Maybe it is just a timing issue.

Link to comment
Share on other sites

Great! yeah the placeholder thumbnails for related stories never work directly after publishing, it's a bug that I keep forgetting to report.. will do it now. (Y)

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.