I would like to share my experience while setting up the mail.imap command in G1ANT studio.
For everyone stuck at the invalid credentials error--
Open your gmail account (the one you ware using in your code)
Go to the settings tab to the top right corner and then click on See all Settings.
In the All settings option click on Forwarding and POP/IMAP
Enable IMAP
Now head over to you homepage and click on manage accounts tab for your email account.
In the manage account section click on Security
Scroll down and turn on access to LESS SECURE APPS
Let the site update and go back (Do not close the tab directly)
This procedure should fix the invalid credentials error. However, even after doing all this the LIST variable (where the email data is stored) has no value allocated in it.
If anyone can find a solution to this problem, your help would be hugely appreciated.
I think your messages are already seen, so you can unread them and then try again and also see that you have got some messages that are from the current day.
Thank You for your solution for Invalid Credentials.
Related
For some reason I deleted so called brand entity at my gcloud console. Now I want to create new one using the command in the console:
gcloud alpha iap oauth-brands create --application_title='EmojiRave' --support_email='rebelusgames#gmail.com'
But the console returns me back : INVALID_ARGUMENT: Request contains an invalid argument.
I've used different formats (using brackets and without them)
I've checked whether I have enough permissions to do it (I use owner account, so it's enough permissions)
I'm desperate.
There are two potential reasons for the failure:
1. Incorrect email address. According to the docs: "This [support] email address can either be a user's address or a Google Groups alias. [...] Note: The user issuing the request must be an owner of the specified support email address."
2. Project is not in an organisation. According to this source (see under limitations): If you're [..] outside a Cloud Orginization most likely you'll get an error on step "Creating oauth brand".
Overall, my suggestion is to update the OAuth Consent Screen via GCP Console.
Go to the Google Cloud Platform Console.
From the projects list, select a project or create a new one.
If the APIs & services page isn't already open, click on the Navigation Menu on the upper left and select APIs & services.
On the left, click OAuth Consent Screen.
Click Edit App.
First, it's not possible to delete the OAuth Consent Screen (Brand) once created. This can be seen from #DaImTo's answer, and the lack of delete option in both gcloud command and in the console.
I also tested your command on my Cloud Shell and it works fine as well. I've checked the documentation with regards gcloud alpha iap oauth-brands and it is currently in ALPHA state. It may change without prior notice and it may not be stable or work to all users. If you still want to use the CLI and request to be allow-listed regarding this command, my suggestion is to contact sales, as instructed on the issue tracker you've made.
I created a random sheet and then clicked publish to publish this google sheet publicly but for some reason when i click on my public link after signing out it will ask me to login again. This did not happen in the past. Has something changed with google sheet?
FYI i am not restricting access to anything or anyone i am publishing this as a public link but not able to access the link if i am not signed in.
I suggest others try it out and see if they get a different result or maybe there is restrictions on my account.
This is an ongoing issue that started yesterday. At my workplace, we are using it for years now. But suddenly the scripts started failing. HTML output is working fine but CSV, TSV formats are asking for login.
A temporary fix would be to change the sharing permission of the spreadsheet to Anyone on the Internet.
Issues started popping up on google support:
https://support.google.com/drive/thread/83705117?hl=en
https://support.google.com/docs/thread/83645178?hl=en
https://support.google.com/docs/thread/83744355?hl=en
https://support.google.com/drive/thread/83700244?hl=en
No solution or reply from the google team yet!!
not to sure, but when your posting, there should be a new option that lets you grant and restrict access. from the screen shot you provided, it should be somewhere in the "published content & settings" section at the bottom of the publish screen. once you do that it should open the access options and youll be able to allow anyone to view the document. The link you provided is still coming up as access denied. Let me know if you need more help and ill provide some pics and more details.
I can confirm that we experienced the same error yesterday - out of the blue our export scripts started failing.
We only experience this with CSV/TSV published Google Sheets, and we also made sure that there are no viewing restrictions whatsoever. If I publish as a website, I can still open that anonymously in a browser.
This is however useless as the data was being parsed as CSV.
A workaround is the following:
Click the Share button.
Click get link section of the modal.
Make sure "Anyone with the link" is selected.
Copy the URL and click done.
Post-fix URL with: /export?format=csv&gid=0
If you need a specific sheet, find the gid by clicking on that sheet in your browser and copying the gid from your browser's url. gid=0 is the first sheet.
Adjust all of your bash scripts with the new URL.
Enjoy!
enter image description here
I am unable to sign into my Microsoft account from within Visual Studio 2019 Preview.
I first noticed this when attempting to clone from an Azure Devops repository. However, I get the same error in all circumstances, for example when clicking on “Add an Account” from the Accounts Settings form.
I just get a large completely blank form entitled “Sign into your account”.
I am using Windows 10 on a laptop.
Any help greatly appreciated.
Geoff Olding
I know this was answered but i too was having the same problem and this didnt work.
First, my problem was when clicking sign in, it would bring up two tabs, one just saying this might take a minute and another saying "sign into your account", the second one would remain blank and moveable.
I couldn't find a solution on the internet, but here's my solution;
In the menu, go to Tools > Options > Environment > Accounts. Click the dropdown below "Add and reauthenticate accounts using:" and select System web browser
Exit the option menu and try to log in again. It should bring up Microsoft edge and let you log in, once you have it should also sync with the program.
This issue was finally resolved by Microsoft support - I needed to reset my Internet Explorer settings (yes really, that product none of us have used for years), back to their default settings (which I hadn't changed in the first place).
In the login option page which is displayed, click account settings (if its not displayed then click help report problem sign in option )
On the screen that get opening select , system web browser.
Now you can log in using browser and it will work fine
In the top right near the 'minimize' there should be a section that shows who is logged in, or an option to log in.
Otherwise, go to help-->Register Product and select the sign-in option.
I am creating application in React-Native and it has Google Login. I research on it and I got Google-React-Native from here. I added it and follow all the steps which it say. But I am still getting error. I spend two days behind it, but didn't get any solution.
I also follow this-solution, but my issue is still not resolved. Can any one help me to find the solution?
Its a very small mistake. The issue is in generating key for Google. I follow below steps and generate new key and its work for me.
1) Open “https://console.developers.google.com” and generate one application.
2) You will get three menu on Left size. Click on “Credential” tab.
3) You will get new window with three option. “Credentials”, “OAuth consent
screen” and “Domain verification”.
4) Click on Credentials and then "Create Credentials" from it.
5) Click on OAuth Client Id and fill information. You will get the one key.
Use it into your application and it will work fine.
Hope these steps will help to other guys also.
Happy Coding
I occasionally receive emails from Google (accounts-noreply#google.com), similar to the following:
Subject: Suspicious sign in prevented
Someone recently tried to use an application to sign in to your Google
Account, ________#gmail.com. We prevented the sign-in attempt in case
this was a hijacker trying to access your account. Please review the
details of the sign-in attempt:
Monday, November 19, 2012 8:40:55 PM GMT
IP Address: 184.72.161.49 (amazonaws.com)
Location: Dixmoor, IL, USA
If you do not recognize this sign-in attempt, someone else might be trying
to access your account. You should sign in to your account and reset your
password immediately. Find out how at
http://support.google.com/accounts?p=reset_pw
If this was you, and you want to give this application access to your
account, complete the troubleshooting steps listed at
http://support.google.com/mail?p=client_login
Sincerely,
The Google Accounts Team
© 2012 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
You have received this mandatory email service announcement to update you
about important changes to your Google product or account.
Indeed, this was me, as I have an app running on Heroku (hence why the IP address is from amazonaws.com), and I send email directly from my app via Gmail SMTP (I don't think it should matter, but specifically, I'm using the gmail_smtp plugin which I updated for Rails 3.2).
Is there a way to avoid this warning, or a way to whitelist known IPs?
Short Answer
In a web browser (perhaps Chrome/Incognito), log into your Gmail account (the one via which you're trying to send email from your app).
In another browser tab, open https://accounts.google.com/DisplayUnlockCaptcha -- and follow the steps.
Long Answer
I ended up logging into my Gmail account (mentioned as ________#gmail.com in the Stackoverflow question above) and saw the following warning:
[Note: I'm piecing this Answer together after the fact.] Clicking the link Was it you?, I'm pretty sure I was taken to a page that contained the following, though below it there was a message and button about adding another application to the list:
[Again, I'm pretty sure...] Clicking the button on that page brought me to https://accounts.google.com/DisplayUnlockCaptcha -- which looks like this:
Clicking Continue brought me to another page:
At that point I just went to my app, and made it send an email.
Note: for general live-testing of email in my app, I have a view at triggers#index with two buttons that send PUT requests to these actions: triggers#send_email and triggers#raise_exception. This enables an admin to go to /triggers and send an email or raise an exception to test if the production system is working correctly as far as being able to send email is concerned. Raising an exception in any of my apps emails details to me via exception_notification.
I had the same problem when I tried sending emails through Gmail SMTP using PHP. You shoud complete the troubleshooting steps provided at the end of the email.
On your Gmail mail box look at the bottom right corner and you can see a Details button. Click on it and then on the pop up window change the suspicious warning settings.
To get this working in dev with Rails 4 i had to enable access for less secure apps.
Visit https://www.google.com/settings/security/lesssecureapps while signed on to your gmail account and click 'turn on'. Note, this enables access for less secure apps which could come with unintended consequences.
Some apps and devices use less secure sign-in technology, which makes
your account more vulnerable. You can turn off access for these apps,
which we recommend, or turn on access if you want to use them despite
the risks.
To get this working in Rails 4, in addition to enabling access for less secure apps, as described already (Visit https://www.google.com/settings/security/lesssecureapps while signed on to your gmail account and click 'turn on'. Note, this enables access for less secure apps which could come with unintended consequences.),
one more step may be required in some cases, if account access is still blocked.
If this is the case, also visit https://accounts.google.com/DisplayUnlockCaptcha and click continue, to enable account access to send via gmail SMTP.
Credit to Steve Polito