Re: KeyError: 'refresh_token' error in fetchmail-oauth2

Mandi! Marco Gaiarin
  In chel di` si favelave...

> Juergen Edner say that the OAuth client created in 'Test mode' least at
> maximum a week.
> But if i try to publish the app, i need the Google approval process, because
> the api used (eg, GMAIL API) is 'restricted'.
> So, it is needed to publish the app? If yes, what is the shortest and error
> prone path to get it approved?

OK, i can confirm Juergen is true; after 7 days:

 /home/famiglia/fetchmail-oauth2.py -c /home/famiglia/.oauth2.conf --auto_refresh
 Traceback (most recent call last):
   File "/home/famiglia/fetchmail-oauth2.py", line 591, in <module>
     main(sys.argv)
   File "/home/famiglia/fetchmail-oauth2.py", line 502, in main
     newTok = response['access_token']
 KeyError: 'access_token'

I've redone the auth with '--obtain_refresh_token_file' and now works back
as usual.


I perfectly agree that big G is not fair on this, but... more practically,
how can i 'register' a (fake?) fetcmail app?

-- 
  Son giunto alla conclusione che, almeno una volta nella vita, bisogna
  usare Windows a fondo, perché è un'esperienza che rende uomini.
  Almeno, io, dopo, ho sempre due palle così.		(Leonardo Serni)