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

Cannot login walkaround using Google Wave ID on AppSpot #35

Closed
GoogleCodeExporter opened this issue Aug 6, 2015 · 3 comments
Closed

Comments

@GoogleCodeExporter
Copy link

*What steps will reproduce the problem?*
1. Deploy Walkaround on AppSpot
2. Go to https://(appid).appspot.com
3. Login with your google ID
4. Go to https://(appid).appspot.com/import
5. Import a wave
6. Go to https://(appid).appspot.com/inbox
7. Notice list is empty.

*What is the expected output?  What do you see instead?*
1. On the local machine go to http://localhost:8080/import
2. Login with the google wave id: (yourgmailname)@googlewave.com
3. Import a wave
4. Go to http://localhost:8080/inbox
5. Notice the wave is there!
I expect to see the imported wave on appspot.com also. The reason why it isn't 
visible is probably because (yourgmailname)@gmail.com (the only ID you can use 
to login on appspot.com) does not match the (yourgmailname)@googlewave.com 
which is used in the waves.

*What browser and browser version are you using?  On what operating system?*
Not applicable.

*What URL does your browser show when the problem occurs?  Did you compile
walkaround on your machine, or are you using a public instance?*
https://(appid).appspot.com/inbox
http://localhost:8080/inbox
Compiled both on my machine and deployed as public instance.

*Please provide any additional information below.*


Original issue reported on code.google.com by guillaum...@gmail.com on 28 Dec 2011 at 7:53

@GoogleCodeExporter
Copy link
Author

These steps don't reproduce the problem for me.  Maybe there is some difference 
between the wave you're trying to import and the ones I'm testing with.  Can 
you describe a sequence of steps that starts with "create a new wave on 
wave.google.com" and reproduces the problem with that wave?

I don't think your diagnosis is correct: 
http://code.google.com/p/walkaround/source/browse/src/com/google/walkaround/wave
/server/googleimport/ImportWaveProcessor.java#82 replaces @googlewave.com with 
@gmail.com when importing, and 
http://code.google.com/p/walkaround/source/browse/src/com/google/walkaround/wave
/server/googleimport/ImportWaveProcessor.java#140 adds the importing user as a 
participant.

Please also make sure you've deployed the latest version from git, the code to 
add the importing user is a recent addition.

Original comment by oh...@google.com on 28 Dec 2011 at 9:24

@GoogleCodeExporter
Copy link
Author

Original comment by oh...@google.com on 4 Jan 2012 at 12:36

  • Added labels: Component-Import

@GoogleCodeExporter
Copy link
Author

Fixed according to 
https://groups.google.com/d/msg/walkaround-dev/GzsczUISc-Y/_KTto0ZZPaUJ .

It's true that private import is less useful than shared import, but that's a 
different problem tracked in bug 41.

Original comment by oh...@google.com on 13 Jan 2012 at 9:14

  • Changed state: Fixed

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

No branches or pull requests

1 participant