Com.Apple.Itunes Aedeterminepermissiontoautomatetarget Is Always Return -600

com.apple.iTunes AEDeterminePermissionToAutomateTarget is always return -600

Good call on the NSAppleEventsUsageDescription key — that’s required if you link against the 10.14 SDK — but if your app is sandboxed, you’ll also need an appropriate Apple event entitlement: com.apple.security.scripting-targets if you can, or com.apple.security.temporary-exception.apple-events if you must. See https://developer.apple.com/library/archive/documentation/Miscellaneous/Reference/EntitlementKeyReference/
Chapters/AppSandboxTemporaryExceptionEntitlements.html for more details, including a way to specify both entitlements, but only one applies depending on the current OS version.

Can't run app because of permission in macOS v11 (Big Sur)

The problem in my case it was related to a Big Sur problem where UPX compressed binaries are not recognised properly, so they were not executed with a permission error.

There is some more information here: UPX compressed application fails to start on latest macOS release: Big Sur 11.01 #424

So the solution is to unpack the binary with UPX and run it normally.

Install upx with Homebrew (executable brew):

brew install upx

Now run this command:

sudo upx -d /Applications/my_app.app/Contents/MacOS/my_app

(Please note you have to specify the full binary path.)

You should use the path of your binary instead of "/Applications/my_app.app/Contents/MacOS/my_app"

Then run the application normally.

Looking for a 'cmake clean' command to clear up CMake output

CMake 3.X

CMake 3.X offers a 'clean' target.

cmake --build C:/foo/build/ --target clean

From the CMake docs for 3.0.2:

--clean-first  = Build target 'clean' first, then build.
                 (To clean only, use --target 'clean'.)

CMake 2.X

There is no cmake clean in CMake version 2.X

I usually build the project in a single folder like "build". So if I want to make clean, I can just rm -rf build.

The "build" folder in the same directory as the root "CMakeLists.txt" is usually a good choice. To build your project, you simply give cmake the location of the CMakeLists.txt as an argument. For example: cd <location-of-cmakelists>/build && cmake ... (From @ComicSansMS)

How to get multiple properties from objects in JXA?

I'd probably do it like this:

sys = Application('com.apple.systemevents');
FinderProc = sys.processes['Finder'];
FinderMenuBarItems = FinderProc.menuBars[0].menuBarItems();

Array.from(FinderMenuBarItems,x=>[x.name(),x.enabled()]);

By first converting the object to an array, this allows one to map each element and retrieve the desired properties for all in one go. The code is split over several lines for ease of reading.

EDIT: added on 2019-07-27

Following on from your comment regarding Objective-C implementation, I had a bit of time today to write a JSObjc script. It does the same thing as the vanilla JXA version above, and, yes, it clearly makes multiple function calls, which is necessary. But it's performing these functions at a lower level than System Events (which isn't involved at all here), so hopefully you'll find it more performant.

ObjC.import('ApplicationServices');
ObjC.import('CoreFoundation');
ObjC.import('Foundation');
ObjC.import('AppKit');

var err = {
    '-25211':'APIDisabled',
    '-25206':'ActionUnsupported',
    '-25205':'AttributeUnsupported',
    '-25204':'CannotComplete',
    '-25200':'Failure',
    '-25201':'IllegalArgument',
    '-25202':'InvalidUIElement',
    '-25203':'InvalidUIElementObserver',
    '-25212':'NoValue',
    '-25214':'NotEnoughPrecision',
    '-25208':'NotImplemented',
    '-25209':'NotificationAlreadyRegistered',
    '-25210':'NotificationNotRegistered',
    '-25207':'NotificationUnsupported',
    '-25213':'ParameterizedAttributeUnsupported',
         '0':'Success' 
};

var unwrap = ObjC.deepUnwrap.bind(ObjC);
var bind = ObjC.bindFunction.bind(ObjC);

bind('CFMakeCollectable', [ 'id', [ 'void *' ] ]);
Ref.prototype.nsObject = function() {
    return unwrap($.CFMakeCollectable(this[0]));
}

function getAttrValue(AXUIElement, AXAttrName) {
    var e;
    var _AXAttrValue = Ref();

    e = $.AXUIElementCopyAttributeValue(AXUIElement,
                                        AXAttrName,
                                        _AXAttrValue);
    if (err[e]!='Success') return err[e];

    return _AXAttrValue.nsObject();
}

function getAttrValues(AXUIElement, AXAttrNames){
    var e;
    var _AXAttrValues = Ref();

    e = $.AXUIElementCopyMultipleAttributeValues(AXUIElement,
                                                 AXAttrNames,
                                                 0,
                                                 _AXAttrValues);
    if (err[e]!='Success') return err[e];

    return _AXAttrValues.nsObject();
}

function getAttrNames(AXUIElement) {
    var e;
    var _AXAttrNames = Ref();

    e = $.AXUIElementCopyAttributeNames(AXUIElement, _AXAttrNames);
    if (err[e]!='Success') return err[e];

    return _AXAttrNames.nsObject();
}

(() => {
    const pid_1        = $.NSWorkspace.sharedWorkspace
                                      .frontmostApplication
                                      .processIdentifier;   
    const appElement   = $.AXUIElementCreateApplication(pid_1);
    const menuBar      = getAttrValue(appElement,"AXMenuBar");
    const menuBarItems = getAttrValue(menuBar, "AXChildren");

    return menuBarItems.map(x => {
        return getAttrValues(x, ["AXTitle", "AXEnabled"]);
    });
})();

---

Related Topics