3 Answers

• I would love to see this on the roadmap too. My use case is where i'm loading images where they are redirects (tumblr does this on large images so the urls are friendly). the only thing i've see that may be a workaround is where you run a toBlob() and assign a timeout, but i really don't want to take the memory hit when loading tons of images in.

• did you try the native JavaScript try/catch? In catch try outputting the error object (the argument to catch) to the console like:

  try {
  ..
  }
  catch(e) {
  Ti.API.info(e);
  }
  

• Hi,

  Maybe you can try to use a HEAD httpRequest at the same time you're trying to load your image, to check the state of the picture on the server. It will cost a little more bandwidth, but not that much because it's only a few bytes (you're not downloading the picture twice, but just asking the server what's the status of the file).

  xhr = Titanium.Network.createHTTPClient();
  xhr.setTimeout(10000);
  xhr.onload = function() {
      if (this.status != 200) {
          somethingsWrong_function();
      }
      else {
          everythingsOK_function();
      }
  };
  xhr.onerror = function(e) {
          somethingsWrong_function();
  };
  xhr.open("HEAD", "http://www.blahblah.com/pictures/blah.png");
  xhr.send();