What steps will reproduce the problem?
1. go to http://partychapp.appspot.com/room/galaxy.nexus.kaskus and click send
invitation
2. sign in on talk app for android on samsung galaxy nexus running android
4.2.1.
3. no invitation displayed on talk app for android contact/buddy list.
4. since no invitation is received on talk app for android, accept the
invitation at http://partychapp.appspot.com/room/galaxy.nexus.kaskus
What is the expected output? What do you see instead?
1. both my gmail and google apps domain talk accounts should receive 2.
galaxy.nexus.kaskus@im.partych.at chat invitation.
galaxy.nexus.kaskus@im.partych.at should be displayed on the talk app for
android contact/buddy list, there's no galaxy.nexus.kaskus@im.partych.at
contact there.
Additional information:
1. Signed in to google talk on windows pc or inside gmail webmail.
galaxy.nexus.kaskus@im.partych.at is on the google talk for pc or gmail webmail
chat contact/buddy list. still on talk app for android,
galaxy.nexus.kaskus@im.partych.at keep disappears. i do get the chat window
opened if someone posts in the partychat room though on three of them (google
talk on windows pc, gmail webmail chat, and talk app for android).
2. i tried to reproduce this bug by creating two rooms which were nexus.id
@im.partych.at and android.id@im.partych.at. i got chat invitation
notifications on talk app for android on both gmail and google apps domain
accounts and be able to accept the invitation and they were all listed in the
buddy list.
3. all chat invitation from partychat room were sent to each email account and
received without a single flaw.
4. My real problem with galaxy.nexus.kaskus room which the chat invitation from
galaxy.nexus.kaskus didn't show up on three different platform of google talk
client, and after accepting the invitation through website, the partychat room
was not displayed ONLY in talk app for android contact/buddy list. :(
Thanks in advance. Have a nice weekend!
Original issue reported on code.google.com by charlesa...@gmail.com on 12 Jan 2013 at 8:43
Original issue reported on code.google.com by
charlesa...@gmail.com
on 12 Jan 2013 at 8:43