I am getting 412 Gmail_API: Request had insufficient authentication scopes while trying to configure service in Email JS. Also, receiving the same error while sending email using React.js library.
Below is the screenshot of the error.
Image displaying error while adding service
I had the same and submitted the question, their answer was:
"To solve this problem, you need to go to EmailJS dashboard -> Services, click on the Gmail service in your list, and reconnect your account. Please click on the checkbox "Send email on your behalf" to allow us to send the emails through your Gmail account. The new Gmail access popup leaves all permissions disabled by default."
Had to disconnect and re-connect my email address:
Go to emailJS dashboard and select "Email Services" on the top left
Clicked on the service that is getting the error in your list of email services and select "Disconnect" next to your connected email address
Then select "Connect Account" to reconnect your email address (I'm using gmail) and finish by clicking "Update Service"
That solved the issue for me, best of luck!
Piggy backing off of what abo mentioned, the error may also arise because it was your first operation via EmailJs.
I also got the 412 status code. I logged error.text from the emailJS.sendForm() call and got this:
"Gmail_API: Invalid grant. Please reconnect your Gmail account"
Ksenia's answer was the fix for me as well. If you're curious as to why it's happening see this post.
In my case it was due to my account being inactive for 6 months.
Just repeat the process, when you get the notification that emailjs has found n-number services with your email already click done then proceed and click continue. this worked for me.
Related
I am trying to disconnect one of my email addresses (a corporate address) from my personal Trailhead account.
a) From https://trailblazer.me/settings?lang=en_US and then...
b) From section "EMAIL ACCOUNTS Manage your connected email accounts", when clicking the button "Disconnect" next to the corp. email address I want to disconnect, Salesforce shows me this red message:
I have disconnected any Salesforce Account and I have even tried to perform the disconnection of the email address from a different laptop but I am getting the same above mentioned red message again.
How can I get over this red message and effectively disconnect the corporate address? Should I perhaps wait 24 hours?
Thank you very much.
Answer from Salesforce Team which has resolved the issue:
Thanks for getting in touch with the Trailhead help team.
You have two salesforce orgs connected to the trailhead. Please check
any of the salesforce org use the email id which you are trying to
disconnect. If yes, please disconnect that org before you try to
remove the email id.
I have a simple azure logic app as follows.
Now I add a new action after the first one.
Select an email action.
Look for send email action
Now no mater what I do, I get this error
Please check your account info and/or permissions and try again. Details: REST API is not yet supported for this mailbox. This error can occur for sandbox (test) accounts or for accounts that are on a dedicated (on-premise) mail server. clientRequestId: 9295041e-4d27-4d7f-8ac7-9f90f1cc65ff serviceRequestId: 17c7df3b-7f07-6d27-4f7b-68a4475e9b55 More diagnostic information: x-ms-client-request-id is '51B43F16-6D7C-4BE7-9AE2-7B4A6B73BA49'.
I click Change Connection above and I see these increasing number of connection, and I find no way to delete them. See the last image at the bottom.
And when I click Save, I get this message.
Save logic app failed. Failed to save logic app vivek-logic-app. Some of the connections are not authorized yet. If you just created a workflow from a template, please add the authorized connections to your workflow before saving.
And finally when I click Api Connections, I find no connections to delete.
So two questions.
How to authorize hotmail account te be used by Azure Logic App
How to delete the un-necessary connections
Ok, here it is after a good 3 hour PIA.
For the connections to manage(or delete), look at the resource group and not the Logic app.
And next for the send email action, choose Outlook.Com connection and not Office 365 Outlook. Found the answer here. Mine is personal account and not for work or for school.
Once you setup this action successfully, you can take a look at this page for managing the connection access.
My company has an application that was verified through the Google OAuth Review/Verification process and is listed as "Published" in the Cloud Console; however, end users are starting to receive the "This app isn't verified" warning when needing to re-authorize.
We tried emailing them Google Cloud Platform/API Trust & Safety Team directly but immediately received the reply "Please note that your email was not received because api-dev-oauth-verification#google.com is not a monitored alias."
Since the application is verified in the console, the "Submit for verification" button is greyed out so we can't contact them that way and we don't want to modify the scopes to require verification again as we want to preserve everything so Google can investigate it in its current state.
That's why I'm reaching out here:
Has anyone experienced this before and have any ideas what could be the cause?
Anyone know a way to reach the Google Cloud Platform/API Trust & Safety Team without the use of "Submit for verification" button?
You are receiving the "api-dev-oauth-verification#google.com is not a monitored alias." message because the address you are trying to send the email to, is a bit wrong.
The correct address to contact the trust and safety team is:
**
api-oauth-dev-verification#google.com
**
Remember that only the project owner should contact the T&S team.
When trying to login into gmail Couldn't sign you in error is displaying in automation
Scenario: I have a automation test case which performs login to gmail and read email content present in inbox.
From last one week this test case getting failed due to Couldn't sign you in error
Full error message:
You're using a browser that Google doesn't recognize or that's set up in a way we don't support.
To keep your Google Account secure, sign in on another browser or change your browser's settings. Learn more
Error page link
Note: This work's in local machine but failing in AWS EC2 server
As per this link google restricts automation but for me its working in local machine!
Need help to resolve this!
Try the following Steps:
First Enter emailid using SendKeys, than Inside the Email text box SendKeys (Keys.Enter) rather than clicking next button.
Same goes for Password field.
I am receiving this error 'The envelope specified either does not exist or you have no rights to it.' when I click to sign a Document that was sent to a gmail account. This only happens when I first click on 'Review Document'. If I close the tab and click again on 'Review Document' I am able to sign the Document. This is happening in my Salesforce Sandbox with gmail accounts. If I use the company email I have no issues.
I have tried with another corporate account and it doesn't throw an error but tried with 1 other public email and still have the same error.
I'm sorry you're having this difficulty with the DocuSign system.
For help on this type of problem, please contact our support department: https://support.docusign.com/contactSupport
StackOverflow is for developers' questions.
Many thanks.