Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

JimmerJabber

macrumors member
Original poster
Jan 3, 2018
66
78
Hi all!

I purchased Delicious Library 3 some time back (https://delicious-monster.com/). I just picked up a new computer and did a clean install of Delicious Library 3 from their website.

To my surprise - I encountered the following permission message:

1676277358929.png


Bit concerning!! Anyone else experienced this?
 
Hi HG

Thanks for taking the time to reply.

The release notes state the issue was fixed in 3.9.1. I downloaded the latest version (3.9.3) and experienced the issue.

Looks like I'll be sticking to Bookpedia for now!
 
The “Keystroke Receiving” window does not show on a fresh 3.9.3 install in Monterey.

Try to reset all permissions for Delicious Library 3 from Terminal with
Code:
tccutil reset All com.delicious-monster.library3
then launch the 3.9.3 version again.

It should ask for Contacts permission, with the reason “You can loan items to friends from your contacts” mentioned in the info.plist file:

<key>NSBluetoothPeripheralUsageDescription</key>
<string>You can scan items with a Bluetooth barcode scanner.</string>
<key>NSCameraUsageDescription</key>
<string>You can scan barcodes with your camera.</string>
<key>NSContactsUsageDescription</key>
<string>You can loan items to friends from your contacts.</string>
 
The app is also in the App Store and there are multiple apps that legitimately require access to keystrokes.
 
The app is also in the App Store and there are multiple apps that legitimately require access to keystrokes.
That might be so, but I have never received a request from any other application to receive keystrokes. In partiular, there is no legitimate reason a simple cataloguing application should require such access.

The version on the website could also be different to the version on the AppStore. Further, being on the AppStore is not a guarantee that the application is safe. Numerous apps have been pulled from the AppStore after Apple found issues with them.
 
If you deny it, then it can’t access it. There are legitimate reasons for asking.

Based on the contents of the info.plist in the 3.9.3 version, my guess is that previous versions had AppleScript functionality enabled. Now, NSAppleScriptEnabled is set to NO. If you have a previous version you can compare the two info.plist files.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.