Skip to content
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

Closed
salomegeo opened this issue Feb 18, 2015 · 8 comments
Closed

Comments

@salomegeo
Copy link
Collaborator

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.

@iislucas
Copy link
Contributor

@dborkan Does this cause our XMPP google social provider integration tests to fail?

@dborkan
Copy link
Contributor

dborkan commented Feb 18, 2015

I'm having problems running "grunt jasmine_chromeapp" right now, and get this error before Chrome is even started:

Running "jasmine_chromeapp:all" (jasmine_chromeapp) task
Building...Done.
Starting Reporter...Done.
Starting Chrome...Fatal error: spawn ENOENT

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.

@dborkan
Copy link
Contributor

dborkan commented Feb 18, 2015

Just created freedomjs/freedom-social-xmpp#102 for the jasmine_chromeapp issues

@klazizpro
Copy link
Collaborator

I am seeing this issue too . it's interesting it's happening only for bob in my case sam is ok
talk2

@klazizpro
Copy link
Collaborator

attaching the full log on the link .
https://docs.google.com/document/d/1gYNg_WiXUkpoU67DI2zrUrsChb-7lg7XBkQcg3Ixu_Y/edit?usp=sharing

errors are followings

[XMPPSocialProvider] received end event, status: offline null Logger_console.print

[Module uProxy] Incoming message claimed to be an RPC returning for unregistered call 0 Logger_console.print

@dborkan
Copy link
Contributor

dborkan commented Feb 18, 2015

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.

@iislucas
Copy link
Contributor

Turned out to be a glitch in XMPP/Hangouts.

@iislucas iislucas modified the milestone: v0.9 Allardice (Web Store Feature Complete) Feb 19, 2015
@dborkan
Copy link
Contributor

dborkan commented Feb 19, 2015

2 things we can do to debug if we see this again:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants