Google idle Account

[hipstersmoothie]

When a user is logged in for a period of time and leaves the browser, google cannot re-authenticate to get the likes. This may be because we don't get a refresh token, but I though meteor would handle that.

[tssweeney]

Ok, so it took a while to track this guy down. (I made a small fix on commit b3fe6b8 - it only changes the UI if the server request is successful) The timeout occurs after 1 - 1.25 hours of idle. The access token is persists, but I believe it is being invalidated on Google's end. The standard 401 that gets spit out is:

Exception while invoking method 'likeVideo' Error: failed [401] 
{
   "error": {
      "errors": [{ 
         "domain": "global",     
         "reason": "authError",    
         "message": "Invalid Credentials",     
         "locationType": "header",     
         "location": "Authorization"}],  
      "code": 401,   
      "message": "Invalid Credentials"
   }
}

after the Meteor.http.post('https://www.googleapis.com/youtube/v3/videos/rate?id='+id+'&rating=' + like + '&key{'+apiKey+'}&access_token='+Meteor.user().services.google.accessToken); call on line 76 of server/server.js. Oddly enough, all documentation stays that Meteors requestOfflineToken flag should take care of this. I can't find anyone else with a similar issue. Continuing to dig...

EDIT: According to Google the refreshToken should be used. Which we actually have (stored at Meteor.user().services.google.refreshToken).

[hipstersmoothie]

I'll change it to that and see if it is fixed

[hipstersmoothie]

well thats fucked meteor/meteor#522

[tssweeney]

Nice work - clean