I have no idea why it's different, but on my actual mobile device the picasa API requests fail. The XHR doesn't give much explanation, other than the provision headers the don't seem to resolve to a final response.
I've tested using a cors/json proxy while remote debugging and the request works.:
var xhr = new XMLHttpRequest();
xhr.open("GET", 'https://jsonp.afeld.me/?url=https%3A%2F%2Fpicasaweb.google.com%2Fdata%2Ffeed%2Fapi%2Fuser%2F111395306401981598462%2Falbumid%2F6148448302499535601%3Falt%3Djsonc%26kind%3Dphoto%26hl%3Den%26imgmax%3D1080%26max-results%3D5000%26v%3D2%26start-index%3D1')
xhr.onload = function(e){console.log(e.target.response)}
xhr.send();
@crhym3 can we standup an endpoint that proxies XHR requests and returns the json?
I have no idea why it's different, but on my actual mobile device the picasa API requests fail. The XHR doesn't give much explanation, other than the provision headers the don't seem to resolve to a final response.
I've tested using a cors/json proxy while remote debugging and the request works.:
@crhym3 can we standup an endpoint that proxies XHR requests and returns the json?
This affects https://github.com/GoogleChrome/ioweb2015/issues/1425 and is in prod. We've never caught it :(