add some (very) basic checks for "error: 'missing version'" from the server

only done in the game score update code - but this is run early, and just once, when loading IITC. it also refreshes at intervals
This commit is contained in:
Jon Atkins
2014-03-21 17:11:28 +00:00
parent 61ed2307e4
commit ed185c39ec

View File

@ -17,16 +17,21 @@ window.updateGameScore = function(data) {
// to detect the problem and try a different set is easiest in a place where there's only a single request of that type // to detect the problem and try a different set is easiest in a place where there's only a single request of that type
// sent at once, and it has no extra parameters. this method matches those requirements // sent at once, and it has no extra parameters. this method matches those requirements
if (data.error || (data.indexOf && data.indexOf('"error"') != -1)) { if (data.error || (data.indexOf && data.indexOf('"error"') != -1)) {
window.updateGameScoreFailCount++; if (data.error == 'missing version') {
if (window.updateGameScoreFailCount <= window.requestParameterMunges.length) { dialog({
//TODO: methods to try a different munge set? title: 'Reload IITC',
// window.activeRequestMungeSet = (window.activeRequestMungeSet+1) % window.requestParameterMunges.length; html: '<p>IITC is using an outdated munge set. This can happen when Niantic update the standard intel site.</p>'
// console.warn('IITC munge issue - cycling to set '+window.activeRequestMungeSet); +'<p>You need to reload the page to get the updated changes.</p>'
+'<p>If you have just reloaded the page, then an old version of the standard site script is cached somewhere.'
updateGameScore(); +'In this case, try clearing your cache, or waiting 15-30 minutes for the stale data to expire.</p>',
buttons: {
'RELOAD': function() { window.location.reload(); }
}
});
return; return;
} else { } else {
console.error('IITC munge issue - and retry limit reached. IITC will likely fail'); console.error('game score failed to load');
} }
} }