Hi all I had to spend 2 days to figure out a strange problem relating to using Google Users service.
Problem: I recently enabled Google Accounts sign in in my app. But in production, when someone signs in with their Google account, the landing page (/trees/list.htm in my case) after the sign in returned None (null) for the users.get_current_user(), in Python. I think this problem would exist in Java world as well. Strangely, if I hit the landing page after 5 to 10 min in the same browser page, the function returned the signed in Google user!! Solution: I figured that this happens when the landing (redirect) page given to Google is *different* from the page that redirects or generates the link to the Google sign in page (/login.htm in my case), this 5 to 10 min of delay occurs when the users.get_current_user() api returns the signed in Google user. When I am instructing Google to redirect to the same page (login.htm) that generated the link to the Google sign page, this bug was solved. Possible explanation by me: It might be due to something like sticky sessions, in which the cloud server that generated the Google Login URL sees the signed up user instantly than the other servers in the cloud. So when the landing page is different from this URL, the request goes to some other machine in the cloud, where it takes 5 to 10 min for the data of Google user signed-in to be propagated!! Thoughts? -- Jagan -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
