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

Authenticating always fails #11

Open
RenaudBompuis opened this issue Feb 17, 2022 · 4 comments
Open

Authenticating always fails #11

RenaudBompuis opened this issue Feb 17, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@RenaudBompuis
Copy link

Not sure if it's me or if something has changed on Audible's side but I'm systematically getting these errors when using the US site:

There was a problem: Enter a valid email or mobile number
Error authenticating: step[6]: auth verification failed
@jvatic
Copy link
Owner

jvatic commented Feb 19, 2022

Yeah, I think there may be either different markup breaking cross-region support, and/or additional prompts that aren't handled. I'm not sure when I'll have time to dig into this. PRs are always welcome ;)

@jvatic jvatic added the bug Something isn't working label Feb 19, 2022
@jasonehines
Copy link

I'm getting this on MacOS as well. I was able to authenticate the first time, but every time I run the cli or gui, I get that error. Is there some cache I can delete to make the auth a fresh one?

@jvatic
Copy link
Owner

jvatic commented Sep 28, 2022

Is there some cache I can delete to make the auth a fresh one?

Nothing is being cached by the app across runs. My guess is this has to do with Audible serving an altered flow based on your IP that the app doesn't currently handle.

Running either cli or gui with LOG_LEVEL=trace env will record responses to ~/audible-downloader-config/debug (which will be stripped of all or most potentially sensitive information unless REDACT_DISABLE=true). Finding the form the app is getting stuck on would be helpful towards getting this fixed.

@rasmusbe
Copy link

I had the same problem and my solution was to activate 2FA on the account. Seems to work fine with 2FA, but not without.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants