andreas.w

It's hard to tell what might be the reason for this without more context, but you could go to the the Raindrop workflow and check if it says "ra" where I marked that with red in the screenshow below. That is where the code word that by default is set to "ra" is configured, and you could change it to anything by double clicking that box and change the setting for it there. One thing you could do, and which is what I do myself, is to set up keyboard shortcuts for searching a bookmark or adding a bookmark, which you can also see in the screenshow below on the left side. Double click those boxes to set your own shortcuts if that seems like a good solution for you.

No, there isn't (at least not that I'm aware of). What is possible though, and how I have been using this workflow myself, is to bind it to any keyboard shortcut you want, so that you get directly to the Raindrop searching (or adding a bookmark) without having to go through standard Alfred first. I have for example been using it like this: Trigger Alfred: cmd+space Trigger Alfred Raindrop Search: option+space Trigger Alfred Raindrop Add Bookmark: cmd+option+space But you can of course configure it to what you prefer. If you go to this workflow in the Alfred settings, the object that you will need to double click to set the shortcuts are the two green ones with a white field in them, up in the top left corner. (There is a description of this below these objects too). You can also change the "r" and "ra" keywords to anything you like (so that you can use something that you remember more easily) at about the same place in the configuration (you will see the green objects with "r" and "ra" as titles.

Try to open Keychain Access and search for raindrop there, and remove the item that matches this workflow, and then open the workflow again and try to search or add a bookmark. If you do that, you should get to re-authenticate, and hopefully thay will fix the problem.

@heyJoeCampbell Are you getting any error message, or some other hint of what might be going on?

Hi @heyJoeCampbell, @kibbles and @jstncwlcx I think that the workflow should have your issues fixed in the latest version, so check if it works better if you upgrade. https://github.com/westerlind/alfred-raindrop-search/releases

Hi @dyab I answered this on GitHub here: https://github.com/westerlind/alfred-raindrop-search/issues/19 The quick summery is that I think it is possible that it might be possible to solve this issue by forcing a log out and then log in to Raindrop again the next time you use the workflow, which you can do by removing the raindrop-search object from Keychain Access.

The issues with opening links in Alfred 5 is now fixed in version 2.0.7, which you can get here. This version also adds support for the browsers Arc and Sidekick, and fixes some encoding issues when saving bookmarks. Thanks @vitor for the help with fixing the Alfred 5 issue!

Hi @egregious I don't think you left anything blank yourself, but the workflow is trying to read something that is not what it expects it to be. It is hard to tell exactly where this came from by just knowing this error message though, so what you could do to help with some of the context of it is if you could open Alfreds settings, go to the Raindrop workflow, and and click the debug button in the top right corner (the one that looks like some bug). When you have done that, you can just leave it like that and try to use the workflow again, and you will then get more information in the debugging field that you opened, which you could copy and put here or send in a personal message to me. It would also be helpful to know if you got through the login process and accepted that the workflow should get access to your Raindrop account, and it would also be good to know if you where trying to search or add a bookmark when this happened, and if you got to see anything else happen before you got this error message.

Hi @Craigers I'm happy to hear that you like the workflow! There is no way to use Raindrops own search locally, but I have been working on an alternative way to make something like what you ask for possible. The development of that has stalled a bit lately but it should be released eventually (I have a functioning proof of concept for how it would technically work). The idea of what I'm working on is to download and store the title's, tags and URL's (and maybe the description) of all bookmarks locally, and then use Alfreds own search engine to search that list. This will be an alternative way of searching, and you will be able to decide if you want to use the current search mechanism or this alternative one, and if you use the alternative method things will be faster but you will not get full text search like you do now (it will basically only search the titles and tag names and maybe the description, unlike the current search mechanism that is able to search the full content of all bookmarks), so then you can decide what works best for you. I think this will be done within a few months, but I can't say for sure.

Hi @Ravisankar You might already know most of the following, but I'm writing it anyway if someone else might have use for it in the future. From the way you describe this, and the error message, it sounds almost certainly like this problem is a consequence of your corporate firewall sitting in the middle between you and the server and acting as a TLS endpoint (meaning that it decrypts your request to check/filter it), and then makes a new request to the actual server. This can be a good security approach in a corporate environment, but it it requires that the clients have the Firewalls root certificate installed to be technically possible without getting error messages like this for almost everything. Sometimes these firewalls are set to not check known sites, which means that they don't see the content of those, and that you don't need it's root certificate installed to be able to reach those sites, so for that reason you might not see these errors for everything, even though everything goes through the firewall and even if you don't have the certificate installed. It is good to know that if someone who should not be able to is trying to see your web requests, it would also look similar to this, so you should be careful with installing a certificate to solve it when you see an error like this if you are not 100% sure that it is the expected certificate. So, it sounds like you have the correct pem file with the root certificate, so that is good, and than the only thing that remains is really to install it. Chrome uses macOS's system wide certificate store, just like Safari and most other apps (Firefox uses it's own, so certificates that are installed in macOS's store does not apply to it) To install and enable a root certificate in macOS central certificate store you just need to double click it, and then open Keychain Access, search for and find the newly installed certificate and double click it, expand "Trust", change "When using this certificate" to "Always Trust", close the dialog and confirm with your credentials (or TouchID or whatever it asks for). After that it should work in most apps, which means almost anything that is not Firefox or Java based (there are more exceptions, but not on top of my mind right now)

Hi @arpan Sorry that it's not very obvious how to log out. You can do it by opening the Keychain Access app, searching for raindrop, finding the value that comes from this workflow (likely the only result you get when searching for raindrop there), and delete that value. The next time you trigger the workflow it will let you log in again.

@clienttel It is possible that it might start working again if you reauthenticate against Raindrop, which you can do by opening Keychain Access, search for raindrop, and delete the login object there. When you try to use the workflow the next time, it will then let you authenticate again, and with a little luck that might solve your problem.

@clienttel One possibility is that Alfred might not have automation permissions for reading content from Chrome. That would lead to something like this. Go to System Preferences -> Security & Privacy -> Privacy -> Automation, and make sure that Google Chrome is checked under Alfred 4 in the list. Alfred asks for this permission the first time you try to add a bookmark, or something else that requires Alfred to access a specific browser, but if you don't click to allow it at that time, you will have to go to System Preferences like I described above to make it work. Also, if this is not how you did it previously, I think you would get the copied link variant to work by first copying the URL, then selecting something that is not the browser (click on the desktop for example), and then call the workflow for adding a bookmark. If that works like it is supposed to do, it would then read your copied link without you having to paste it, as you don't have a browser windows selected.

Hi @clienttel When trying to add the bookmark, do you either have a browser with the site you want to add open as the front most window, or have copied the link you want to add before you call the workflow? The workflow will add the URL that is open if a browser is the front most window, or otherwise if you have copied a URL, it will add that. If you have none of those it does normally tell you about how to add a bookmark, but it happens that it simply does nothing, like you describe. (I should probably fix that, but it does not brake any functionality, it only makes it a bit less clear how to use the workflow in some cases) Which browser are you trying to add a bookmark from? Could you also, in the view that you sent a screenshot of, click "Script Filter" on the last line and check which box in the workflow that gets selected?

Hi @SteveM I have looked a bit more into this, and I think that the root cause of the issue is some sort of problem to properly connect to the Raindrop servers, or at least it seems like you might get an unexpected response for some reason, so I have made some changes to make the actual response from the server (or at least the "body" of it, for now) show in the Alfred log if there is a problem like the one you are having now. So here is a new pre-release version that you can try, and if you still have the problem with this version you can look in the Alfred log and you should be able to see the server response there, and hopefully that will give a hint about what's wrong. Download here