Unable to authorize app with pocket

[deleyva]

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

[nybbles]

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?

[deleyva]

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.

[nybbles]

@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.

[fscaptain]

Hi, same as @deleyva , After clicking "Authorize" Nothing happens. DevTools output:

VM113:31872 Found unexpected stored request token eval @ VM113:31872 eval @ VM113:28 __awaiter @ VM113:24 getRequestToken @ VM113:31870 eval @ VM113:31981 eval @ VM113:28 __awaiter @ VM113:24 eval @ VM113:31980 (anonymous) @ app.js:1

Disconnect an connect again with the same result.

[fscaptain]

If i check the browser i found the following in response header: x-error Invalid request token.

[abatkin]

I just went through some pain, and I'm also on Linux, using AppImage. In my case, I did two things:

• Got rid of appimaged (it seemed like a good idea a year or two ago, but it's been more pain than it is worth - note that I went through ~/.local/share/applications and renamed (or deleted) most of the appimagekit_* files to proper names, copied away the icons to better locations, and edited the desktop files themselves to be normal)
• For Obsidian, added %u to the Exec line, and added MimeType=x-scheme-handler/obsidian;

This page was useful, and now my Obsidian.desktop file looks like this:

[Desktop Entry]
Comment=Obsidian
Exec=/home/whatever/Applications/Obsidian-0.15.6.AppImage %u
Icon=/home/whatever/Applications/Obsidian.png
MimeType=x-scheme-handler/obsidian;
Name=Obsidian
StartupNotify=true
Terminal=false
Type=Application
Categories=Office;

[cellcoresystems]

@deleyva
I was opening the vault from a google drive folder and there I had the same symptom.
I found out that google drive does not allow files with .__ like the file .__pocket_access_info__ which is the file name of your secrets for pocket in the plugin folder.
I was then opening a copy of the vault in regular folder and the file could be created.

Maybe you have a similar issue.

@nybbles
Do you think we can change the file name ?
Is a PR welcome ?