hafaio
schema version 4 not supported: update to schema 4 compatible api
Since a few days I always get an error message: "_Conversion to epub failed. Error: schema version 4 not supported.__" What does this mean? I haven't changed anything. Using Windows 11, Edge or Chrome browser, newest version of the extension.
Without more information it's reallt hard to help. I could / probably invest iv better logging support so I can debug these issues more easily. In the meantime, I'm going to ask you to follow some steps that will make it easier for me to figure out what's going on. Unfortunately, you're on edge not chrome, but hopefully you can find similar functionality:
The instructions are all listed in #20 , essentially go to extensions, turn on developer mode, then go to the extension, toggle on collect errors.
After that, do what triggers the error (does it happen everywhere?).
Now when you go back to the extension details page, you should see an Errors button. Can you copy the more detailed error information you see there?
I followed your instructions and made a screenshot of the error message. Do you need further informations? And yes, it happens every time.
Oh no. This doesn't portend well, but I'm not sure what I can do at the moment.
A brief explanation: reMarkable doesn't publish their api. Originally I copied the code of someone who reverse engineered it. Then it changed, and I learned how to reverse engineer it. The very first step is getting information from a google cloud server about how it stored, and it appears that they're updating the version.
Unfortunately I don't have access to the version 4 api yet, since my account hasn't been upgraded, and I can't think of another way to test and reverse engineer it. Even after I do, it may still be a process to get a working version of the api.
For now I'll update the extension page to indicate that this might be happening and redirect to this issue. In meantime, I suggest you just download them as epubs and upload using the official apps.
I'm sorry for the inconvenience. I wish reMarkable just made this public.
I'm sorry I don't have a better solution. At some point my access will also break, and then I'll be able to patch in support. I'll try to do that as quickly as possible, but it takes manually reverse engineering it. If you find any information about someone adapting to the recent change, feel free to attach that here, and I'll do my best to incorporate their learnings.
@erikbrinkman API changes like this are extremely frustrating. I just wanted to say thank you for your work on this wonderful extension. It's been, in my experience, far superior to the official one.
I, potentially naively, assumed that this roll out would be quick, but it doesn't seem to be as I have retained access this whole time. If someone is comfortable around a terminal, and willing to test some things out, we could try working together to reverse engineer the v4 api to try and unblock this.
It has come to my attention that being enrolled in beta access might make this more likely. I wonder if anyone who's having this problem is, and if un-enrolling creates a temporary fix. Enrolling myself might also allow me to finally debug this.
I just submitted v5.5 to the web store. With some help from a kind reMarkable enthusiast, I patched in fallback that will try to use a legacy upload api if the schema version fails. This api is the same one the remarkable extension uses, and it's not as feature rich, but it does work independent of your schema version. You should see something like this when you're on version 5.5, and it should be enabled by default.
v5.5.0 is out. If you update, you should be able to upload again. Thanks for your patience while this was down!
Note: I'm still working on schema 4 support, but without having access there's only so much I can do.
I know it's been 8 months, but to anyone still following this, I should have something that works for schema v4 now, although I still haven't been able to test it myself.
Below is a zip of the extension that should work. Github doesn't allow uploading zips, so you might need to rename it to .zip before testing. If anyone who has has trouble with schema v4 could try it, it'd be greatly appreciated!