Comment 2 for bug 749972

While I cannot reproduce with the latest glance, and returning an image without a name is unhelpful to the user (and in my mind a slightly large/more pressing issue) I realize that the API shouldn't 'blow up' when encountering an image without a name! :)

I should have a fix ready in a minute after checking to make sure other values aren't suffering from the assumption that they should...exist?