The call “Gmail - Small Business - Send Text Email” is still giving me the error message about not being initialized (but the email does send). However the “Gmail - Small Business - Send Text Email (with Cc)” call does not give this error, so it makes me think the specific “Gmail - Small Business - Send Text Email” call specifically is not initialized?
Will need to wait until tomorrow to test this again to see if the authentication refreshed
I have reinitialized that particular call again (sent text email) and republished the plugin. Please install the latest version to give it another try
thanks!
That initialization must have worked now, no more error message.
However the refresh token doesn’t seem to be working correctly. I had to re-authenticate with Gmail again. I double checked the token expiration conditions listed here: https://developers.google.com/identity/protocols/OAuth2#expiration
To try and help troubleshoot:
I know I haven’t changed the Gmail password, and I can still see my app has access rights from my Gmail account, and the access was just granted last night. So the only possible errors are the Refresh mechanisms are not working or this “The user account has exceeded a maximum number of granted (live) refresh tokens” - which I wouldn’t think is happening, but I don’t think we can view this data.
I was expecting some difficulty with this API connection, hence why I thought I would save time by getting the plugin, but it seems like it hasn’t been used too heavily or I am guessing this would have been solved. Hopefully we can figure this out soon as this is a powerful plugin once we get it right
Hey Geoff,
sorry about that, i’ve tweaked some other parameters of the Oauth flow making them identical to our other Google plugins where offline proved to work. Could you please install the latest plugin version and give another try? if it still doesn’t work there is still one more little change i could try making 
Thanks
It is still expiring, tried re-authenticating and re-trying things on my end. The token seems to be valid for around 24 hours then expires
Hey @gf_wolfer i’ve made another change, can you please install the latest version, refresh the editor and retry?
Thanks
Looks like this change worked - thanks!
(at least has worked for 30 hours)
great, hope it continues working
So, the connection is working, but to get Verified by Google (so they don’t warn users about granting access to the app), we need to adjust our Scopes.
Is there a way to allow the Plugin to allow for variable Scopes to only ask for what we use?
I have a feeling the plugin currently uses the https://mail.google.com/ scope, but Google has told us that is asking for too many permissions for what our application does and suggests we only use these scopes:
https://www.googleapis.com/auth/gmail.compose
https://www.googleapis.com/auth/gmail.readonly
https://www.googleapis.com/auth/gmail.send
Documentation around scopes = https://developers.google.com/gmail/api/auth/scopes
Geoff, if we remove the scopes then some plugin calls won’t work
Understood, but unfortunately this Plugin won’t get past the Google Gatekeepers!
The Scopes requested of a User need to match what is actually used in the app and many some of the Scopes in the plugin are not needed for every app.
Is there a way to customize the plugin code for a specific plugin? (Clone it and add it to an app?)
Or can you DM me the ‘source’ of the plugin so I can re-create things as needed (I think my client purchased the plugin outright instead of subscribed) - and avoid any future back and forth
Trying to think of the easiest way to get these scopes right, and if it’s built into the plugin that would obviously be best for it in the end, but may not be easy to put in
i’ll create a private copy with the scopes that you only need, what’s the app name to authorize?
need to keep these scopes though for the oauth to work I believe, is that ok? https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/userinfo.profile
if not i can try removing them as well but not sure if the oauth will work fine
@levon What are the limitations to the type of HTML tags that this plugin can accept when using the “Send HTML Email” capability? I have HTML code that I validated works (currently using it when sending via Outlook, as well as confirmed runs and produces the expected results on Best HTML Viewer, HTML Beautifier, HTML Formatter and to Test / Preview HTML Output). While troubleshooting, I stripped the (body) Message down to: 
for example.
The email successfully sends, however when I open the email, there is nothing in the body of the email. I would expect the body of the email to contain a “7” that is linked to “https://google.com”.
Hello @dillon.blakes
Than you for reaching out.
We will inspect the reported issue and will do our best to help you. I will keep you updated.
Best regards,
Zeroqode Team
hello
Tryy to find and replace https:// by nothing. Let me know if it works
@petit-ricard
Specifically, the inline styles seem to be a problem. Example:
<p style="color:blue;font-size:46px;">
@petit-ricard - thanks for pointing me in the right direction!
Disregard this one as well… I was able to do a find “:” and replace with the escape character : throughout the entire HTML and that enabled all of the in-line styling to work as well.
@petit-ricard Also, removing https:// causes issues with the images displaying in referenced images as well as difficulties navigating to linked pages when doing so from the phone.
Disregard this question about removing “https://”. You instead can replace HTTPS:// with the special character formatting: https://
We also need a private copy with only the scopes we need. The only API call we are using are Send HTML Email.
Scopes:
https://www.googleapis.com/auth/userinfo.email
https://www.googleapis.com/auth/userinfo.profile
https://www.googleapis.com/auth/gmail.send
App Name: Proscore
