Today I saw that I have "apiserving#google.com" as an owner of my Google App Engine project, and I cannot understand why it ended up there. I have tried to find any documentation related to it, but a search won't give me anything.
The only hit I have on "apiserving#google.com" as owner is a link (http://grokbase.com/t/gg/google-appengine/1519zm7na4/a-apiserving-google-com-is-suddenly-appeared-on-account-list-as-another-owner-of-my-own-project) to someone asking the same question.
I consider this question answered by Adrián. I removed an user that was owner to my application, and it was replaced with apiserving#google.com. The user disappeared after the fix was put into production.
We are aware of this issue. We have confirmed that this happens when a deleted account is added to the project. As the deleted account's information cannot be loaded, apiserving#google.com is used as the default one.
The engineers are working on it but there is no ETA on this. However, I'll update this thread when the fix goes into production.
UPDATE
The fix went into production on 5th February and #patrick has confirmed that the issue has been solved.
Related
I am trying to obtain my production keys for my QBO app following the steps in this link
here
However, when I try to start the "App Assessment Questionnaire", I get the error message below:
You currently do not have a developer account, please click here to complete setting up your developer account. Once that is complete you will be able to access the help pages.
This is what I see, and I DO have a developer account. It won't let me continue.
Please help!
UPDATE
I see this error in the address bar:
ErrorCode=ERROR_CREATING_USER&ErrorDescription=License+Limit+Exceeded
UPDATE #2
I tried creating a brand new account, a new app, on a different PC and the same thing happened. So this is not a cache issue.
UPDATE #3
Created 2 support tickets for this issue
#00114423
#00114415
I had to use a different account to access the help site
https://help.developer.intuit.com
I've the same issue since Friday (02/18) and spent hours to figure out what's the problem.
tried from different browsers and different IP addresses
made a brand new developer account to test with it
had a 1+ hour chat session with QB support (but not developer support)
sent an email to an address received from the chat assistant
sent a feedback at https://www.surveymonkey.com/r/AppAssess
According to the browser's developer tools:
the Start questionnaire button opens this URL:
https://developers.intuit.com/app/developer/appdetail/prod/questionnaire?appId=xxxxx:UUID_of_app
then it redirects to:
https://login.salesforce.com/services/auth/sso/yyyyyyyyyyy/Intuit_Enterprise?community=https://help.developer.intuit.com
finally, SSO to salesforce fails and it redirects back to:
https://developer.intuit.com/app/developer/qbpayments/docs/qbms-payments/hosted-paypage/faqs/help-redirect?**ErrorCode=ERROR_CREATING_USER&ErrorDescription=License+Limit+Exceeded**+-+Customer+Community+Login&ProviderId=xxxxxx&startURL=%2Fs%2Fquestionnaire%3Fapp%yyyyyyyyyyyyy
So, it seems to be, QB have reached a license limit at salesforce, which prevents new logins to create and the questionnaire from to load.
And the funny part is: the same thing happens, when I tried to create a support ticket and used the "Ask a question" button at https://help.developer.intuit.com/s/
Which means, I can't start the questionnaire and can't start a ticket about the error either.
I guess, if QB developer accounts whom created support tickets previously or started the questionnarie before the license limit has been reached, they have have a SSO login account at salesforce and able to fill in the form or start new support tickets, but others are stuck because of the license limit.
If somebody have a working QB developer account and able to start a support ticket, please do it, and link this page in it.
Or maybe, we should contact salesforce support to let QB know about the license limit.
I'll give it a try.
This seems to have been fixed. I tried running the questionaire and it worked.
I have also been having this problem the last several days and had the same lack of success with QB support. The URL callback error I see is:
ErrorCode=REGISTRATION_HANDLER_ERROR&ErrorDescription=Please+sign+the+terms+of+service+before+you+login+to+community
I don't see anywhere I can sign a TOS in my account page - it's possible that in fact QBO hasn't signed a TOS with Salesforce. What a joke.
I get this error when I try to add a domain which I have previously deleted from my Yandex account.
domain_must_be_migrated: Domain must be migrated from PDD
and
Unable to complete action. A 422 error occurred.
I could not find any related issue in the documentation or google. could anyone give some advice regarding this issue, please?
I also have the same problem with the long domain when i tried to add domain in to new oraganization. So i added another domain shorter (even i do not own it), it is success.
When i created a new organization, i add the correct domain into the organization
I was having the same issue and I contacted the Yandex customer support for the same but i did not get any resolution even after a month.
So I just tried adding www.mydomain.com as a new organization instead of mydomain.com and it worked perfectly.
I have a simple Script deployed as a Web App. What I'm looking to do is for the URL to include a single parameter which returns a value from a Google Document Spreadsheet. It all works when signed on as me.
What I want is anyone to be able to use this. I thought that Execute the app as: me and Who has access to the app: Anyone, even anonymous would be what I want.
However, it always puts up a Google login screen and after that starts asking for permissions on the App and the Google document.
Am I doing something wrong?
Many thanks.
OK ... I think I've solved it.
I needed to create a new version of the project and then Deploy this one with the final permissions rather than changing the permissions of the existing one.
I hope that helps someone else as I've been banging my head against the door on this one!
With old GAE console you could invite others to join a project as owner or developer. Recently this option is moved to the new cloud console.
I used to use the old console to get access to client's so I can deploy application and make changes to it. The process involved with login into the project and inviting the new user. Then an email was sent to the new user and after he/she accepts the invite he/she could access this application directly from his/her console at appengine.google.com.
I tried the same process with the new changes couple of days ago, logged in into the new project and from the permission menu added myself to the project. However no email was sent to me and I still don't see this new application in my console!
Interestingly enough if I go to https://console.developers.google.com/project I see this new project there is no logs or data-objects listed. If I go to appengine.google.com I won't see this project and that's where I can go to application's console!
Not sure what's going on, has anyone seen this? Is there something I'm doing wrong?
Amir
I found the issue!
If you add a new project via appengine.google.com (old way) the application won't show up under Compute/App Engnie section of console.developers.google.com as simple as that.
The proper way to get all functionality is to add the new project using the console and then use the permission to add others.
It's strange and I couldn't find any documentation that explains it but I've tested and resolved my own issue this way. Hope this helps others.
Amir
I am trying to duplicate my app in the administration console, but receive the following error:
There were errors: developer does not own the app id being forked
My gmail account is showing up as the "Owner" in the Permissions Tab.
Did anyone ever have the same experience? Any thoughts or advice on how to tackle this problem?
I already tried through inkognito mode in chrome like it is described here: http://code.google.com/p/googleappengine/issues/detail?id=8106
Edit:
I changed to two factor authentication 2 weeks ago. I just tried it with deactivated 2factorauth, it does nothing.
Do you own the name that it's trying to tie the duplicate to?
Check this by attempting to create an app with the same name before you attempt to duplicate, I guess.