-
Notifications
You must be signed in to change notification settings - Fork 51
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 sign in #14
Comments
Another one here. gem:
It looks login problem, so I inspected the def conditionally_sign_in_to_amazon
retries ||= 0
if @kindle_logged_in_page.nil?
signin_page = mechanize_agent.get(KINDLE_LOGIN_PAGE)
p signin_page
signin_form = signin_page.form(SIGNIN_FORM_IDENTIFIER)
signin_form.email = email_address
signin_form.password = password
p signin_page
post_signin_page = mechanize_agent.submit(signin_form)
p signin_page
... and found that login failed although the form looks correctly got completed( Try changing UserAgent to the same one of my browser made no effect. same issue found on stackoverflow: Using Mechanize to log into https://kindle.amazon.com/login |
I've experienced some sign-in related issues, but they are tough to debug. Are you still having issues here? |
It appears that Amazon has changed their Kindle Notes/Highlights site around, a lot. Since this gem assumes a certain structure as it crawls the Kindle site, it broke. I am working on some fixes. Stay tuned! |
@speric I'm on v2.0.1 and experiencing sign in issues. I don't get any errors, but it returns empty for my books array, even though I have confirmed that there are indeed books there. Any suggestions ? |
@rkartzman I am facing a similar issue. Were u able to resolve this? |
I'm using
v1.0.2
of this gem onmacOS 10.12.3
. My ruby version is:ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15]
.My test code:
I know my email address and password are correct because I'm copying and pasting the exact values I use when logging into amazon.com manually.
I'm receiving this error:
I've tried passing different values for
mechanize_options: { user_agent_alias: 'Mac Safari' }
but I still recieve the same error.Have you seen this issue before? TIA
The text was updated successfully, but these errors were encountered: