You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several months ago, I switched from a normal email/password based account with getpocket.com to a firefox account (I can't remember if I did this voluntarily or not - it would be out of character for me, so maybe it was forced?) I believe pocket-reader was still working for me after that, up until about 3 weeks ago, when I repaved my machine.
Now, when I pocket-lib-reset-auth, approve in the browser, then try to launch pocket-reader again, I get an error saying it is unable to access the token:
Inspired by this comment, tried logging out (which is what reminded me I had switched to a Firefox account), logged back in again, but I still got the same error as above.
I thought of trying to create a new, non-firefox account, to see if that was the issue, but it doesn't look like that is even possible anymore:
I tried some other work arounds I saw in other issues (downgrading pocket-lib and pocket-reader, re-evaling them, evaling plz, ...) but keep getting the error above.
Has anyone else had issues with Firefox accounts or is it just me, or me barking up the wrong tree? Any other information I can provide or debugging I can do to fix this? Thanks in advance for any information.
The text was updated successfully, but these errors were encountered:
That's disappointing to hear. If you have time, please try v0.2 of pocket-lib (e.g. use quelpa-use-package to install it from git); I don't think that should make any difference, but I'm curious.
If that doesn't help, then I'm afraid that fixing it will require stepping through the code carefully, something I just don't have time for right now, so help would be appreciated.
By the way, I note in the error you reported: (x-error . "User rejected code.") (x-error-code . "158") and (x-cache . "Error from cloudfront"). I don't know what those mean, but they're likely relevant.
Several months ago, I switched from a normal email/password based account with getpocket.com to a firefox account (I can't remember if I did this voluntarily or not - it would be out of character for me, so maybe it was forced?) I believe pocket-reader was still working for me after that, up until about 3 weeks ago, when I repaved my machine.
Now, when I
pocket-lib-reset-auth
, approve in the browser, then try to launch pocket-reader again, I get an error saying it is unable to access the token:Inspired by this comment, tried logging out (which is what reminded me I had switched to a Firefox account), logged back in again, but I still got the same error as above.
I thought of trying to create a new, non-firefox account, to see if that was the issue, but it doesn't look like that is even possible anymore:
![image](https://private-user-images.githubusercontent.com/8772/345184795-b635d9b0-e68f-43b1-8632-e5a806bc6b68.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAyMDA4NjgsIm5iZiI6MTcyMDIwMDU2OCwicGF0aCI6Ii84NzcyLzM0NTE4NDc5NS1iNjM1ZDliMC1lNjhmLTQzYjEtODYzMi1lNWE4MDZiYzZiNjgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcwNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MDVUMTcyOTI4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZmNhMjhhZDRmYTIzY2Y1MGM0YzFhNjM2ZmMzODkwMTYyOTFlNDIxZTE2YzIyNTljMmRkNDhkMTFhYzA2Y2Q5ZCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.BU67R3pHkn5_aNdVaDpX_JK56Z7Z6sj91ay9wtAKZSQ)
I tried some other work arounds I saw in other issues (downgrading pocket-lib and pocket-reader, re-evaling them, evaling plz, ...) but keep getting the error above.
Has anyone else had issues with Firefox accounts or is it just me, or me barking up the wrong tree? Any other information I can provide or debugging I can do to fix this? Thanks in advance for any information.
The text was updated successfully, but these errors were encountered: