-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
[BUG] Can't sign out of Amazon #289
Comments
Having the same issue, looks like the method for sign out that this plugin uses needs to be updated as the kindle site may have changed. From what I can tell, it points to
Looks like the last time this plugin was updated was over a year ago, not sure if we will see a fix from the developer any time soon. Honestly, I haven't even been able to get any of the Amazon Cloud sync functionality working, only able to use it via manual file upload for now. I hope this and other issues get fixed since it's a great plugin. |
Has anyone found a workaround, other than deleting the plugin from Obsidian? |
seems it won't then allow you the opportunity to sign in when the plugin has been removed, obsidian closed, and then re-added. |
Hey everyone. I've just been made aware of this thread today. It sounds like as you said the method for parsing logout has changed. Suggested workaround: Open Obsidian dev tools, and clear the app's cookies and sessions. Obsidian is essentially running in a Google Chrome browser. So any instructions online for the latter would work for you. I am going on extended leave from my job in September so will aim to be active on this plugin's development again then. |
Describe the bug
After logging in to my Amazon account and syncing my highlights, I would like to sign out as suggested in the Security section of Git Hub. I click the Sign Out button in the settings but it does not work.
Method of syncing
To Reproduce
Steps to reproduce the behaviour:
Screenshots
Notifications:
Developer Console
Metadata
Thank you in advance for your help !
The text was updated successfully, but these errors were encountered: