bckelly1

I've been taking a look at this and to me it looks like they've changed how the JWT token is structured. The old JWT is very different than the one...

> in theory, this _should_ be fixable. if the libby app and the libby webpage can load the data, then it should be possible to determine what api calls they...

I think there is a deeper change that will be required, though it looks easy maybe? I stumbled across [this](https://github.com/bookbonobo/libby-download-extension/pull/195) while looking for answers and it seems to mention similar...

> @bckelly1 have you been able to figure anything else out? Not much, I haven't put a lot of effort into it. I did find that this workaround in the...

I was trying to figure out why this doesn't work. I think the spine content changed: `"spine": [{"path":"_d/record_access_violation"}]` Looks like they changed the API again.