Notification Center (MAC) Does Not Have Joplin

tessus · 2019-04-13T03:59:07.902Z

gobblepotato:

having waited a day

Hmm, I think that most people in this forum have a day job and reply and/or comment on an issue when they have time to do so. e.g. nobody replied to my post I created 3 days ago. While it easy to reply to a simple and clearly defined question, it might be not so easy for a question that does not even state the version of the release.

gobblepotato:

The section on “Notifications” summarises

I'm not sure what you are reading but it for me it says:

macOS : >= 10.8 or Growl if earlier.

This means that you need Growl for macOS releases earlier than macOS 10.8.

gobblepotato:

“terminal-notifier”, your solution, is presumably for the terminal application, not desktop. I mentioned “Mac”

Yea, I got that. I was talking about the macOS version as well. The test I ran was on macOS.

gobblepotato:

I have looked up everywhere I can find how to add apps to the notification centre,

You do not add applications to the Notification Center. Never have, never will.
As soon as an application uses the macOS API to send a notification, an entry is created in the Notification Center for that application.

Joplin is a react-native application and uses Electron on macOS. Notifications are handled by the module you referenced, so really this module is sending the notifications. This is the reason why the entry you are looking for in the Notification Center is terminal-notifier.

gobblepotato:

I thought I would ask on the support forum

This is ok, but you could have at least mentioned the version of Joplin you are having the problem with or the version of your OS. A problem report that only says it does not work is impossible to work on. You must admit that a bit more information is needed.
As mentioned before, it works for me, so most likely it works also for other people, so your problem might have to do with your setup. Maybe nobody replied, because they don't have that problem.

In any case, more info is needed, since we have to determine what the culprit is.

A debug log always helps, because we can see, if there's an error in Joplin or at least we can narrow down the problem.
So I suggest to set an alarm for time X and we can check what the log says at time X.
Additionally, maybe there's an entry in the macOS system log. You can open the macOS Console application and look for any entries at time X. Other than that, I currently do not have any other ideas.

gobblepotato:

Your attitude, which I provoked, doesn’t encourage donations btw,

Just to be clear, I'm a user of Joplin, like you. I am not the developer.

gobblepotato · 2019-04-13T07:57:17.181Z

Ok, thank you for your help. I will reply with as much useful information as I can.

It is the most recent release of Joplin for Mac Desktop running MacOS Sierra.

Regarding the instructions in the notification section it says:

On the desktop and mobile apps, an alarm can be associated with any to-do. It will be triggered at the given time by displaying a notification. How the notification will be displayed depends on the operating system since each has a different way to handle this. Please see below for the requirements for the desktop applications:

Those instructions are then to either use growl, or follow the instructions I linked to in my first post which said which say to go use the Notification Centre.

I don't know how to run "terminal-notifier" would you mind pointing me to resources that explain it or kindly explaining so you so yourself? (much appreciated). I cant find it from putting into spotlight or searching in finder, siri doesn't have a clue and I dont know how to use terminal. The stuff you said before about reactive-native and Electon is all new to me so I'll have to look that up. I am a keen learner but have a lot to learn.

As mentioned before, it works for me, so most likely it works also for other people, so your problem might have to do with your setup.

This is good news as it means it should be fixable!

Cliking your debug link and having a go there, in the desktop application instructions.

Unfortunately there no file called "flags.txt" so that methed wont work (this is me entering it into spotlight). Putting in the other one (c:\Users\YOUR_NAME.config\joplin-desktop) (obv with my name instead) doesnt do anything, maybe its supposed to be put somewhere else rather than spotlight. So I'm having trouble creating a debug log.

I had a look through the system log as you have advised but dont really know what to look for. In a single minute of activity (when the alarm was set) there are hundreds of things going on and none of them give me a clue as to being to to with Joplin. Any ideas what to look for there?

Also it may be useful to know that in the system preferences for the notification centre I have multiple copies for (for unknown reasons) of the same apps. It might be to do with creating a guest user account that somehow ended up with all the same applications but nothing else creating a possible source for the double copies. I removed the guest user though but maybe that is relevant, possibly, if not let me know and I'll call apple about that for help. I wondered if this was 'clogging it up', but I may be completely on the wrong track here.

Many thanks for your help, it is much appreciated .

laurent · 2019-04-13T10:23:55.276Z

@gobblepotato, if you figure out how to get it working let us know, and we can add the info the readme. Personally, I don’t know as there are many notification systems, which is why we simply link to the documentation of the lib we’re using.

One thing I’ve noticed is that node-notifier had a few new versions recently so perhaps we need to upgrade and it could fix some issues.

gobblepotato · 2019-04-13T13:57:28.220Z

Hi Laurent thanks for the reply. My current plan is to upgrade my OS to the newest one Mohave and see if that fixes it (plus I want to upgrade anyway) but it will take a few days.

In the meantime and tips or ideas would be great. I’ll update after the update, next week sometime .

tessus · 2019-04-13T21:22:27.912Z

gobblepotato:

Those instructions are then to either use growl, or follow the instructions I linked to in my first post which said which say to go use the Notification Centre.

Yes, as I have explained in my previous post:

macOS : >= 10.8 or Growl if earlier.

This means that you need Growl for macOS releases earlier than macOS 10.8. You are using High Sierra, not a macOS version prior to 10.8. So you are not supposed to use Growl.

gobblepotato:

I don’t know how to run “terminal-notifier”

You don't run terminal-notifier. Joplin sends a notification and internally terminal-notifier is used. I only told you about terminal-notifier, because Joplin does nor show up in Notication Center.
So, if you want to change the behavior of Joplin's notifications, you will have to change the settings for terminal-notifier in the Notification Center.

gobblepotato:

Unfortunately there no file called “flags.txt”

This is normal, because you have to create it. The first line of the instructions says:

Add a file named "flags.txt" in the config directory

open a terminal and enter the following comnand (on one line - discourse might have added a line break):

cd ~/.config/joplin-desktop && echo "--open-dev-tools --log-level debug" >flags.txt

Done.

I'm sorry, but I'm starting to wonder, if you read the text as it is written or if you just pick and choose a few words from the text. You asked questions again that I have already explained in my previous post. I'm not sure what else I can do. I think I have expressed myself rather clearly, so I'm at a loss.

varaljop · 2019-04-13T22:26:20.105Z

The ‘terminal-notifier’ entry in System Preferences -> Notifications only shows up after the first notification by Joplin is given, not before, maybe that is the problem gobblepotato is having. Make a todo-entry and set a time on it, and you will get a notification, and the ‘terminal-notifier’ will be there in System Preferences -> Notifications. ‘terminal-notifier’ is a very confusing name though!

gobblepotato · 2019-04-14T07:39:12.038Z

Ok, thanks for telling me what to type in to create the file, that is helpful. The file flags.txt file appears now.

The console tap that appeared in Joplin (as the instructions said it would) didn't do anything, it just stayed blank/empty.

I created a to do, set an alarm, synced, the sync worked as usual, but the alarm didn't go off on desktop and no change in the console inside of Joplin.

The instructions do say "add", my mistake.

Going back to those instructions:

Now repeat the action that was causing problem. The console might output warnings or errors - please add them to the GitHub issue. Also open log.txt in the config folder and if there is any error or warning, please also add them to the issue.

The console did nothing. In the log.txt file I wouldn't know what to look for but nothing says error or warning. The instructions then say to add them to the issue, I don't know which issue, nor how to add them, or if there is anything wrong with them.

So still stuck, but have learned a few things so thank you, it hasn't been or nothing. But I am determined to get this working as well as continue to learn.

gobblepotato · 2019-04-14T07:48:42.005Z

You don’t run terminal-notifier . Joplin sends a notification and internally terminal-notifier is used. I only told you about terminal-notifier , because Joplin does nor show up in Notication Center.
So, if you want to change the behavior of Joplin’s notifications, you will have to change the settings for terminal-notifier in the Notification Center.

I don't know how to do that. How do the notifications appear then? If they are not in the notificatin centre, out of curiosity.

gobblepotato · 2019-04-14T07:52:16.262Z

Hi Varaljop thanks for chipping in,

From what you have said, ‘terminal-notifier’ only shows up after the first notification is given. I have set countless to do’s with alarms, none of them cause any notification on desktop, so it looks like from what you said those alarms I set wont send me a notification until one of them has.

Out of curiosity does terminal-notifier appear like one of the apps in the system-preferences-notifications or completely different?

Thanks

varaljop · 2019-04-14T10:32:33.682Z

Just as one of the apps.

varaljop · 2019-04-14T10:34:09.386Z

Have you tried to uninstall the Joplin app (just move it to the trash and empty), and re-install it?

gobblepotato · 2019-04-14T11:47:03.230Z

I tried doing that early on in my attempts, but haven’t done recently since these alterations. I’ll do it again.

Edit:
Reinstalled, but nope, no luck.

gobblepotato · 2019-04-14T11:56:01.180Z

Ah thanks for the screenshot! This make it much easer for me to visualise how this would even send me a notification.

Is there an app from the app store I could simply download to get terminal-notifier? I dont see any called that but there are some that look similar. Just looking for simple solutions. Though I also want to increase my understanding.

tessus · 2019-04-15T01:56:00.434Z

gobblepotato:

Is there an app from the app store I could simply download to get terminal-notifier?

Ok, let me try this one more time. terminal-notifier is not necessarily an app, it could also be a script.

It is bundled with Joplin, so if you don't get notifications, there must be an error somewhere. Either in the debug log or in the system log of macOS.

There are different implementations of terminal-notifier apps, scripts, tools available. MacPorts has terminal-notifier as well as brew.
The source code is here: GitHub - julienXX/terminal-notifier: Send User Notifications on macOS from the command-line.

Please note that I have no idea, if the module that handles notifications uses the same terminal-notifier. As I mentioned before, there are several implementations out there.

gobblepotato · 2019-04-20T12:30:56.616Z

update: Was backing up my system to upgrade to Macos Mohave just incase that fixed it, but from the changes shown in Mohave it doesn’t look like theres anything very relevant so I don’t know if I really want to do that upgrade, even though there’s still a small chance it can fix this.

Julien from the github link you sent didnt think it would work as they have said (I’m sure they wouldnt mind me quoting) “I don’t know Joplin but I have seen that it uses node-notifier which is a wrapper around my terminal-notifier tool. I think node-notifier bundles my tool so I’m not sure you can change the version yourself easily.”

So, gamble with a Mohave upgrade, which could mess other things up or struggle with getting this fixed? Any more help always welcome.

Edit: Problem solved, at least solved well enough. Turned my phone ringer back one and went through every other app changing its settings. So just joplin can ding my phone and everything else is chilled and relaxed. It still doesn’t give the desktop notification but this will do, so the technical issue isn’t resolved at all, but this workaround will do.

gobblepotato · 2019-04-26T12:40:19.429Z

Just a reminder here that this issue was never fixed, I just had to put my phones ringer on and changed the settings for every other app on the device. And now there is a new problem, posted about in a different thread. I still get no desktop notification, and now due to the new issue I get none on the phone either and it wont even sync, and encryption has to be set up all over again.

ajay · 2020-12-11T22:01:41.780Z

macos, Joplin 1.5.7 : was curious to c whether mac notifications worked for Joplin alerts : yes, it does, but only if Joplin is running in the background. Once you close the app, the banner or alert does not show any longer. Have no clue how difficult this might be to fix ... but this would really be "nice to have".

laurent · 2020-12-11T23:29:46.228Z

You should let it run in the task bar, otherwise notifications won't work.

ajay · 2020-12-12T09:13:17.763Z

simple question, does it - quite in general - have to be this way ? I mean, I see notifications from my calendar, while the calendar isn't running ...

laurent · 2020-12-12T12:01:48.735Z

The calendar service is still running in the background, except they don't display an icon.