Is this a persistant error? it happens every time? This looks like bitly gave some bad/empty response and the bitly library didn't handle it, attempting to look for information in a null object. That hasn't changed in several releases, so it's not a new problem. I'm inclined to believe that bitly is at fault for a bad response. I could try to add guard code here, that would just not expand the URL in the event of a similar error, but I would expect the problem to go away on it;s own.