Ensure Gmail permissions are requested before using withTimer(). #68
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Per issue#63, at least some Gmail account types do not pop up the Gmail Permissions banner when Gmail APIs are called behind `withTimer()`. This change ensures a simple Gmail API is called as the first step when users click on either the "Process Now" or "Start auto processing" menu buttons.
mlsad3
force-pushed
the
request-permissions-synchronously
branch
from
61f9fac to
7cb9637
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per issue #63, at least some Gmail account types do not pop up the Gmail Permissions
banner when Gmail APIs are called behind
withTimer().This change ensures a simple Gmail API is called as the first step when users
click on either the "Process Now" or "Start auto processing" menu buttons.