-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
profile.name is public.talk.google.com user id instead of a real name #938
Comments
@dborkan Does this cause our XMPP google social provider integration tests to fail? |
I'm having problems running "grunt jasmine_chromeapp" right now, and get this error before Chrome is even started:
But if this affects the test accounts, we should see this test case fail: https://github.com/freedomjs/freedom-social-xmpp/blob/dborkan-test/spec/chrome_integration/gtalk.spec.js#L144 If you can reproduce this, feel free to try out that test case by replacing the credentials in https://github.com/freedomjs/freedom-social-xmpp/blob/dborkan-test/spec/chrome_integration/gtalk_credentials.js with credentials for the bad accounts. Also we should reach out to our contacts on the GTalk XMPP team about this to see if they've changed anything. |
Just created freedomjs/freedom-social-xmpp#102 for the jasmine_chromeapp issues |
attaching the full log on the link . errors are followings
|
BTW, if for some reason this is the new reality of GTalk XMPP that we can't change, we can still always get the logged in user's name (via Google APIs), and send that as part of our instance message. We were considering doing this anyways just last week when we thought it would be needed to fix a bug for users who didn't have a G+ account. |
Turned out to be a glitch in XMPP/Hangouts. |
2 things we can do to debug if we see this again:
|
This started happening today, it only happens for some accounts.
also profile I receive for myself, when I'm logged in with these accounts is email address not a real name.
It looks like xmpp bug to me.
The text was updated successfully, but these errors were encountered: