-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker invocation of local browser not working #32
Comments
Hey there @aryan-nvd , many thanks for taking the time to make a note of this. I have re-authentication in a long time so I need to familiarise myself again with how this flow goes. Please allow me some time to check and get back to you. |
Hi @jamesread Regarding scopes, they seemed to have renamed Missing Unchanged I raise it, because I'm looking into my python response after the login-cookie.dat was generated and referenced and I now get WARNING:googleapiclient.http:Encountered 403 Forbidden with reason "accessNotConfigured" |
Okay, good news @jamesread , its all working now. The last bit, and it was there in front of me in the logs, but I had misread it from earlier, was enable the Gmail API So coping the https://console.developers.google.com/..... uri, pasting it into the same browser that was used to authenticate the account, brought me to google cloud and API enablement option. Once complete, run in deamon mode, and it all works. |
@aryan-nvd , thanks for your patience here, my free coding-time has been entirely consumed by another project of mine recently! Here's some positive changes made on the feedback you've provided;
Thanks for your patience, and time to provide feedback - I think this should address all your feedback for future users of this project? |
This is more a note, for the docker component.
I tried to setup using docker and a simple compose.yaml, but the docker execution does not invoke a local browser to complete the authentication path.
I invoked the python stream, and the local browser popped up, and the invocation was complete (albeit not working yet). I'm hoping its just the delay required for the API
Can we amend the readme to guide users to do the python execution to generate their login.dat file as that works perfectly.
The text was updated successfully, but these errors were encountered: