joshuatly/libby_ab_bot

/sync command returns no action

Opened this issue · 6 comments

thecougar6 commented

I'm trying this app for the first time today and when I try to input the /sync command with the 8 digit code provided by Libby in the Copy to Another Device section of the settings, with plenty of time left on the 60 second clock, the bot doesn't do anything. No confirmation and no error message. The 8 digit code is being supplied in the same message as the /sync command. Does anyone know what's going on?

joshuatly commented

/sync command has been tricky at many times, requiring two or three tries mostly.
But it will work. Try some other command like /start or /help before /sync if it doesnt work repeatedly.

The problem is on my bot's side.
However its not on my list of priority to fix, because most of the users will use the /sync one time. And it will work, just try again. And I do not currently have the time to look into making this smoother.

If it absolutely does not work for you, send me a message on telegram, i will sort something out for you.

Below are the behaviour of /sync i've observed (from the libby's bot)

  1. Sync code entered, reply from bot says "Synced". --> Desired outcome
  2. Sync code entered, reply from bot says "Sync Unsuccessful" --> Desired failed outcome, as the bot tell you to try again
  3. Sync code entered, no reply from bot. Libby application (showing the code) still counting down --> something went wrong, please try again
  4. Sync code enter, no reply from bot, libby applicatin shows "Done, Libby linked..." --> Proceed to use /list

Some note on other commands for the record.

/save also is not working as good as I hope, use /download most of the time. Use only /save for very short books with few parts.
If a book have many parts, the chance is high that /save will miss out one part or more of the book.
If all parts of the books are successfully sent, you will ideally get a message saying thats all you will get from the book.

Again, no fix is planned, as originally /saved is implemented as an alternative to /download.

/download works the best, if it fails, it should tell you (unless I need to restart the server, then your message might went missing)

From logs, I've seen people try to use the bot in the following ways which is NOT the way the bot is designed:
multiple download on same command -- just not possible.
starting a download before the previous download is completed -- no. your previous downloaded files will get removed. please be patience and download it one at a time.
try to use /save and /download simultaneously. -- please dont.

Log out
just issue /sync 00000000, your previous logged in libby will be removed from the system.

The bot has been getting a lot more traffic than usual, but right now it still works fine.

There has been a lot of discussion of downloading from libby since extensions are not working, if you are comfortable with command line tools and python, check out odmpy linked in the repo README.
My telegram bot is just an implementation using that project.

joshuatly commented

@thecougar6 please try one more time, if it is still not working, please use the /help menu, and message me on telegram directly, I will check and see your specific case.

joshuatly commented

Well, looks like odmpy has stopped working as well. The bot will stop working until an alternative is found.

joshuatly commented

I've made a few changes for the bot, and is going through testing right now.
It is now using the @ahxxm's fix branch here

Let me know if you face any issue with using the bot, or any part of the instruction is unclear.

Also, you have to do a sync every 7 days afaik, else it will give missing chip error.
I will need to write some code to remove the invalid sync logins automatically

ahxxm commented

It worked fine for a few days and then I got error

Access to this magazine is not allowed with your active library card.

for new loans, and I can't even listen to existing ones from web or app.

The JSON response is title_disallowed_for_card, the same as this reply described, and version string is also 16.7.1(from POST https://libbyapp.com/api/inscribe)

I guess it is more likely a server-side issue due to incomplete update:

  • before Libby update: /openbook gives spine info
  • my fix: spine info was moved to https://deway-......./?m={openbook.msg}, get from there
  • likely update again, as of now: it gets 400 title_disallowed_for_card error from GET https://sentry.libbyapp.com/open/audiobook/card/{}/title/{}?t={openbook.msg}

Once they finished migration or decided to use deway- url again, we can fix accordingly

  • 🎉1
rainrdx commented

It worked fine for a few days and then I got error

Access to this magazine is not allowed with your active library card.

for new loans, and I can't even listen to existing ones from web or app.

The JSON response is title_disallowed_for_card, the same as this reply described, and version string is also 16.7.1(from POST https://libbyapp.com/api/inscribe)

I guess it is more likely a server-side issue due to incomplete update:

  • before Libby update: /openbook gives spine info
  • my fix: spine info was moved to https://deway-......./?m={openbook.msg}, get from there
  • likely update again, as of now: it gets 400 title_disallowed_for_card error from GET https://sentry.libbyapp.com/open/audiobook/card/{}/title/{}?t={openbook.msg}

Once they finished migration or decided to use deway- url again, we can fix accordingly

Thank you so much for maintaining this