You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Quitting IBM Notifier, either via CMD+Q or via activity monitor, returns 0 or main button pressed
To Reproduce
Steps to reproduce the behavior:
Run IBM notifier from terminal, hit cmd+Q or quit via activity monitor
Monitor output, it will return 0
Expected behavior
An action like this should return something other than a success. Ideally an error with a unique error code corresponding to that action.
Additionally, it would be good to have the ability to configure settings to allow or block the ability to use cmd+Q. From an admin perspective, this would be helpful and avoid users skirting policies that rely on the notifier prompts
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: macOS 13
Project version: 2.9.1
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
We tried adding custom System Preferences Keyboard app shortcuts for "Quit" and "Quit IBM Notifier" (which can also be done command line) but no success.
Rather than blocking the COMMAND + Q shortcut in IBM Notifier, using non-zero return code that denotes the notification was terminated would suffice.
Today's behavior of exit code 0 for quit events AND main button presses makes it impossible for the calling script to understand what actually occurred!
Yes @porkcharsui the plan for this issue is to return the code "239: User dismissed the popup/banner/onboarding UI" instead of 0 when CMD+Q shortcut is used.
Describe the bug
Quitting IBM Notifier, either via CMD+Q or via activity monitor, returns 0 or main button pressed
To Reproduce
Steps to reproduce the behavior:
Run IBM notifier from terminal, hit cmd+Q or quit via activity monitor
Monitor output, it will return 0
Expected behavior
An action like this should return something other than a success. Ideally an error with a unique error code corresponding to that action.
Additionally, it would be good to have the ability to configure settings to allow or block the ability to use cmd+Q. From an admin perspective, this would be helpful and avoid users skirting policies that rely on the notifier prompts
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: