-
Notifications
You must be signed in to change notification settings - Fork 6
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
Infinite loop Retrieving audiobook url... #17
Comments
Probably this is the page element to display when the timeout period expires: |
Fixed in 57c364b |
I am getting the same issue. In LibbyApp from a phone and the libbyapp.com website: Script: repeating waiting..waiting..waiting message after the message "Retrieving Audiobook URL" From OverDrive (browser) am able to still listen to the audiobook. This is from both library cards used for testing. Seems to be the case for regular/epub books as well. Accessing audiobooks from both Libby app and Libby browser seems to not work. Overdrive is intact. |
@flyswimr Very curious. I phoned my library to ask about this issue and they didn't know what the problem was. They could reproduce the error message on their computer but didn't know what was causing it. They suggested I come to the library and have them issue me a new library card. |
If you want to talk offline via email on this let me know. Replacing a library card, now allows usage of both Libby and Overdrive (browser only of course). When before, could only use Overdrive in the browser. I have not tried LF yet, can't chance if they block. |
At the point in the session where the message is displayed "
Retrieving audiobook url...
" it keeps displaying "waiting
" repeatedly until the process is killed.To troubleshoot I tried to use the Libby website in a browser and the audiobook appeared in my Loans and when I clicked "Open Audiobook" a new page appeared with the message "Access to this magazine is not allowed with your active library card." This happens for all the materials I have on loan (books and audiobooks). (Maybe my card has been blocked for some reason?)
So this scenario is probably pretty rare but
libbyfetch
should probably timeout after waiting for some period of time and try to dump whatever it knows to an error message.The text was updated successfully, but these errors were encountered: