-
Notifications
You must be signed in to change notification settings - Fork 10
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
Sync stopped working #5
Comments
I have not encountered this before. Can you try to remove the It may also be related to the new sync protocol that is gradually being rolled out (see juruen/rmapi#187). I am currently still on the old version, so this is difficult for me to test. |
Reauth didn't work. It's probably related to new sync as you say. |
Same problem here... :( Tried the reauthentication, but getting the same error |
I got this today, but the message is preceeded by
|
I tried starting remarkable-pocket with Also, it seems that |
To enable debug logging for the rmapi client you can add I'm still on the old sync protocol so it's working fine for me. If you could paste the result of the GET request that would help confirm it is indeed the new sync protocol causing this issue. |
@nov1n I'm getting this on a new build / install. Would debugging output still be useful to you? |
I’m getting a 401 Unauthorized.
Does this help? (: |
I suspect this is indeed the new sync protocol. Adding support is still on my list, but it will be much easier to test once I also get the new version (not sure why that's not happening...). |
Same issue here. I definitely am on the new sync protocol - so that would explain it. Hope they roll it out to you soon! |
So I finally got upgraded to the new sync protocol and found some time to add support. I used rmapi to connect to Remarkable Cloud, and their readme states that support for the new protocol is not yet tested through so it is recommended to keep a backup handy. That said I've been running it for about a week without any problems. The code is currently on a branch, and I will create a release once it keeps working for a few more weeks without problems. If you want to help me test it the command is:
Please let me know if you encounter any problems. |
Thanks for getting this working @nov1n . I don't use docker but have compiled it on a raspberry pi and it's worked well so far. I did see one strange occurrance which is an article I'd just read was marked as read, deleted the re-uploaded. The article remains in my lists whereas the other one that was read is moved to the archive [2022-09-02 20:28:32] Starting sync... [2022-09-02 20:39:23] Starting sync... |
Confirmed working here also. Much better than the solution that I had cobbled together myself! |
Confirmed it works here as well! Thanks so much for sharing the fix! |
@testingtony can you check whether the article was actually archived on Pocket? |
Hi @nov1n, as far as I can see, the articles that keep getting uploaded to remarkable are never put unto the archive on pocket. Other ones are and they don't get reuploaded to remarkable
…On 4 Sept 2022, 15:10 +0100, Robert Carosi ***@***.***>, wrote:
@testingtony can you check whether the article was actually archived on Pocket?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
That is very strange indeed. I cannot reproduce this but will add a check that prevents previously read articles from being reuploaded, regardless of their archive status on Pocket. |
Is there any extra logging that I can turn on that might help? Or, if you point me in the right direction I can try running it in a debugger to see if there's any more (I know nothing of the spring boot framework though)
…On 4 Sept 2022, 15:23 +0100, Robert Carosi ***@***.***>, wrote:
That is very strange indeed. I cannot reproduce this but will add a check that prevents previously read articles from being reuploaded, regardless of their archive status on Pocket.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Can you try |
Closed in #7 |
Okay. I'll give that a go when I'm next near the computer and let you know the results. It might be a day or two.
…On 4 Sept 2022, 15:42 +0100, Robert Carosi ***@***.***>, wrote:
Can you try touch ~/.remarkable-pocket ~/.rmapi && mkdir -p ~/.rmapi-cache && docker run -it --env TZ=Europe/Amsterdam -p 65112:65112 -v ~/.remarkable-pocket:/root/.remarkable-pocket -v ~/.rmapi:/root/.rmapi -v ~/.rmapi-cache:/root/.cache/rmapi ghcr.io/nov1n/remarkable-pocket:0.2.0 -v ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
There are currently a number of problems because Remarkable changed their API again, see #11. |
[2022-01-12 23:22:05] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'nl.carosi.remarkablepocket.RemarkableService': Invocation of init method failed; nested exception is java.lang.NullPointerException: Cannot invoke "java.util.List.stream()" because the return value of "es.jlarriba.jrmapi.Jrmapi.listDocs()" is null
The text was updated successfully, but these errors were encountered: