-
Notifications
You must be signed in to change notification settings - Fork 24
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
Unable to authorize app with pocket #87
Comments
hey @deleyva sorry for the wait. I don't have enough info to look into this yet. Do you still have this issue? If so, can you please try to authorize and sync again, and then open up the dev console (go to View > Toggle Developer Tools or use the hotkey (cmd+ option + i on Mac and ctrl + shift + i for Windows)) and copy paste the logs there? |
Hi! Thanks for your reply. I am using an Ubuntu 20.04. The Developer Tools output is: VM171:31598 Found unexpected stored request token
eval @ VM171:31598
eval @ VM171:28
__awaiter @ VM171:24
getRequestToken @ VM171:31596
eval @ VM171:31707
eval @ VM171:28
__awaiter @ VM171:24
eval @ VM171:31706
(anonymous) @ app.js:1 I have tried clearing local plugin data and syncing again but it still does not work. |
@deleyva when you cleared local plugin data, do you mean that you went to the Pocket settings tab and clicked on the "Clear locally-stored Pocket data" button? That button clears data about Pocket items, not your Pocket authorization tokens. Instead, please click on "Disconnect your Pocket account" and try connecting Pocket again. |
Hi,
Disconnect an connect again with the same result. |
If i check the browser i found the following in response header: |
I just went through some pain, and I'm also on Linux, using AppImage. In my case, I did two things:
This page was useful, and now my
|
@deleyva Maybe you have a similar issue. @nybbles |
When I click on
Authorize
, trying to connect obsidian with pocket, from the browser, it opens the obsidian app (open xdg-open), but then nothing happens.Sysment: Ubuntu 20.04
Obsidian version: v0.13.33
The text was updated successfully, but these errors were encountered: