-
Notifications
You must be signed in to change notification settings - Fork 7
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
Unable to login correctly #3
Comments
I had a similar problem on my forked version, and I solved it by not adding any header at all in the requests (so you don't send the SID in the Cookie header anymore), this seems to fix it, but I am not sure if this is the right way to do it, bit it just works again. I am not sure that this is what you need to do also here, in fact I am using json to get the new posts and not xml. |
I am having the same issue for days now, is there any way to download a fixed patch for this? or anyone share a forked version that does? |
Yeh, check out godenzim's fork (click his name above). He's made something called Google Reader Reloaded which uses the JSON API rather than XML - the only annoying thing with that one is that the system bar menu layout has changed, meaning i keep "open all items" instead of "mark all as read" - but you'll get used to it :) |
sweet, just tried it. Works like a charm. Thanks a bunch guys for the fix and the tip ;) |
From today, Reader Notifier is broken.
While i've figured out whats wrong, my knowledge doesn't extend to fix it.
Basically, when it reads the ATOM feed for new posts, its getting the login page HTML, rather than valid XML, which results in an XMLError, (the code to show an error when this happens is commented out, hence why it hangs on updating)
Login seems to work and loginToGoogle contains a valid SID cookie, but for whatever reason, that isn't working anymore.
Maybe google now require another header to be set or something?
The text was updated successfully, but these errors were encountered: