Hi,
Thank you very much for the report!
It looks like it is a minor issue when checking for the image existence, and somehow the null values are not properly recognized.
It should not cause any issues though, as the execution basically finish with that call on the request.
You can safely ignore this warning, I will make sure to handle it for the upcoming release.