Developer? Work with the Instagram API? Or work with an Instagram library by a third party? Wondering why your Instagram implementation is suddenly showing grey squares? Wondering how to stop it?
It’s the fault of Instagram Albums, rolled out today. You might have read about it on Mashable – they are not a fan.
At the moment (and hopefully this changes FAST), creating an album in Instagram screws with the official Instagram API. Here’s what happens:
- type field is wrong – thus far, there are two values for “type” – “image” and “video”. Albums are returned as “video” no matter what mix of media is in the album. All photos, all videos, or a mix, type will equal “video”
- no video urls – The video urls are missing. Go figure.
- images urls are all null.jpg – all resolutions – standard_resolution, thumbnail and low_resolution – are being returned with a url of https://instagramstatic-a.akamaihd.net/null.jpg
How to Stop It:
Depends on your implementation. But basically, add a check to throw out any media where the image url ends in “/null.jpg” (or if all the media URLs are equal, that’s probably a good sign too).
If you’re working with a third party library, pester the authors with a link to this post, or contribute a bugfix of your own.
And submit reports to Instagram. This is their problem to fix, ultimately. There’s no workaround right now. Our only option is to ignore the problem or toss out corrupted data.