Google Developers Console - Error when inviting user to project - console

I have a new project in the developers console, and cannot seem to add new users. I send the invitation, this is forwarded to the correct Gmail account with the RSVP link:
'https://console.developers.google.com/project/[appname]/rsvp/'
which however results in an error message:
'The server has encountered a problem. Please try again.'
We tried inviting other gmail users and still no luck.
We also made this user an administrator of the billing account, and that works fine. Just the project is not visible to the user.
Anyone has an idea what could be the problem?
Thanks!

Ok, so the problem was in the automatic link sent by Google, which read:
https://console.developers.google.com/project/app[projectname]/rsvp/
but should have been
https://console.developers.google.com/project/app%7E[projectname]/rsvp/
It seems somewhere on the way the tilde got lost.
After changing the link by hand the RSVP works fine.
I hope this helps someone else in this situation.

I just had the same Problem, i realised that i was logged in to several google accounts, work, private etc...
I logged out and logged back in with the account i was invited to the console project and hit the link sent in the email, surprisingly it worked.
Good luck, for anyone else encountering this problem.

Related

Telegram Bot sometimes requires User Authentication

When I access to my telegram-bot, after some time, it requires user authentication with the text:
"Stand by...
Hi there!
Before We Can Continue We Need To Verify That You're a REAL User"
When this message appears it seems session is closed, and the user can't receive Bot notifications, until user authenticates.
I can't understand why this authentication is required if I am storing each user telegram_id.
Your bot token might have exposed on git.
You need to change the token.
Instead of hard coding it in the code, pass it as an environment variable.
Just had the same issue!
I guess, someone scraped my bot-token from public repository and tried to steal my account. NEVER leave your bot-token in public rep!!!
Detailed description for others to find this thread:
Bot sent, what it was programmed to do and then
"Hi There!
Before We Can Continue We Need To Verify That You're A REAL User"
Telegram sent me login code -> I entered it (yeah, I'm dumb)
Bot printed
"Please reply with your 2FA (Two Factor Authentication / Two Step Verification) code"
then
"Timeout has been reached , pleaase try again."
(I like the pleAAse part, where you understand it was totally fake)
Telegram said it was
Device: Android
Location: Bulgaria (IP = 185.95.157.122)
I discovered what was wrong!
Lev Vasilyev answer made me think if somebody was able to get my bot_token. So, I changed it. And, the authentication message no longer appeared.
It´s important to get into telegram allowed devices, and delete not authorized accesses.
My bot has ""Stand by... Hi there! Before We Can Continue We Need To Verify That You're a REAL User" too.
When I proceed and send authentication code and sms from Telegram was received I had been authorized as Samsung Galaxy s20 5g from Seychelles ip adress which was not mine... This was very strange. If anybody had that experience please post your answer too. Maybe somebody had stolen my bot ...Sorry if my English not very correct and nice. I hope you understand.
I had the same problem, changed the Token and resolved the problem. I needed set the webhook again to work.
All replies are correct:
your token has been stolen and used by hackers, once you enter your credentials - you will see unknown sessions in your telegram.
Change token via BotFather and do not publish it in public places.
If you have already put your cred's to the telegram bot - you need to change the password immediatelly.

How to get rid of "Send email as you" permission in Appmaker

I have an appmaker app that used to send emails. However, my users objected to the permissions required for this feature, so I removed it. However, the "Send email as you" permission is still being requested and I can't seem to get rid of it.
I did the following:
deleted (not just commented out) all references to MailApp I was able to find via the search bar
exported my code and searched for Mail just in case I missed anything above
removed mailto: links, in desperation
pubished to a new deployment to verify the permissions required
I can see in the deployment that "https://www.googleapis.com/auth/script.send_mail" is being requested, which is undesirable. However, I can't edit it, and I can't see why it's being requested.
No matter what I do, I keep seeing "Send email as you" being requested. Am I missing something?
I never solved this problem, but I worked around it by running as developer instead of as user. While doing so, I noticed that I had an old trigger installed. It's possible/likely that old trigger was an email trigger, so perhaps the trigger was what caused the email permission. I'll never know for sure since the trigger was deleted.

Meteor-reddit oauth error ["message::"Forbidden", "error":403]

I am getting the following error when I try to add reddit login service. The app however get registered to the user after the login process. But I dont have a new user account setup in meteor after the login process. Was wondering if anyone else has experience with this.
["message::"Forbidden", "error":403]
I had to use https://oauth.reddit.com/api/v1/me. not https://www.reddit.com/api/v1/me.
Apart from that everything else worked as it was supposed to.

Two accounts made with same email bug - Firebase Auth

I have my firebase authentication set to prevent multiple accounts for the same email, but it doesn't seem to be doing that. See following pictures:
Has anybody experienced this issue before?
**Edit: Here's the details for reproducing this bug:
Pretty much the problem boils down to the updateEmail() function.
When a user signs up for my app I want to ensure I have an email for the user so searching for that user is easier. The problem is Facebook authentication doesn't ensure the user has an email for the following two reasons:
The user could have not allowed email permissions.
The user could have created their Facebook account only using a phone number.
Because of this, my
login code is somewhat complex but here's a link to my code with comments to explain everything (Note that I'm using custom Facebook/Google buttons which is why I had to manually do some stuff): Login Gist
If you look at the func getFBUserData() and see the comments above it, the bug is happening in the Case 1's first bullet point:
// 1) user's facebook does have email. This is common case
// - in this case, sign them into Firebase
// - could be that they previously didn't have email but now they do, so update Firebase user's email
This is the edge case where for some reason a user first didn't allow email permissions, then changed their minds and allowed them. What's interesting is that the code will still throw the .errorCodeEmailAlreadyInUse error, but the account will show up in the Firebase console as seen in the picture in the SO question and the following which I just did: http://imgur.com/yMjYXgH

HybridAuth not working - User profile request failed(Google)

I'm using SocialLogin plugin for WordPress which relies on HybridAuth for authentication. However, when I try to login with Google, I get "User profile request failed. Most likely the user is not connected to the provider and he should to authenticate again." error. I've tried Googling the solution, unsuccessfully.
Also, when I try to login with StackOverflow or Yahoo! I get Unspecified error!
I came across this issue also ...
Your question is more than an year old but here you go the solution:
Go to https://console.developers.google.com/ and activate Google+ API access.
That worked out for me!
It generally occurs to me in two conditions.
Session lost when you use for example back button or directly visiting the page instead of visiting via link.
Some times you need to clear your cache, logout and login to site but clean logout
generally fix.
I also want you to know that Hybrid Auth is a dead project.

Resources