Hi, Thanks for the info, I’m not sure what is meany by the “App Bundle” ? I have an XCode project with a bunch of source files and resources, not sure if this is the “App Bundle”? All the

Hi Try xattr -cr <path_to_app_bundle> to remove the extended attributes that are triggering those errors. Read more at https://developer.apple.com/library/content/qa/qa1940/_index.html Cheers João

https://developer.apple.com/library/content/qa/qa1940/_index.html I have run into this in the past. As I recall, some of the artwork (app icons, images used in the app, etc.) had extended Finder

Hi Dave, One or more files have extended attributes which codesign doesn’t like. Use ‘xattr -lr’ to find the files with the attributes and ‘xattr -dr <attribute>' to delete them, i.e. xattr

Sorry - I posted with the wrong subject in my last mail! Hi All, I’m try to build my application for Mac. It compels ok, but I get this Code Sign Error. I Code Sign Error Group Command

Hi All, I’m try to build my application for Mac. It compels ok, but I get this Code Sign Error. I Code Sign Error Group Command /usr/bin/codesign failed with exit code 1 CodeSign

That will be possible under the Apple Grand Unified Understandable Design (Apple GUUD). Just kidding…or maybe not! Tangentially speaking, if you need to do this a lot, you could (besides writing a

Based on its placement and indentation in some SDKs, it's probably related to watchOS, and some speculate it's the OS used by the variant of that OS running the touch bar. Maybe a bridge between

Also, the capabilities Dave mentioned *used to be* opt-in — for the App ID on the web site, either instead of or as well as in Xcode. Now they’re effectively always on (and/or managed within

Also natively if you have OS X code grouped under TARGET_OS_OSX. Jonathan

Makes sense. NIBs contain freeze-dried instances of the objects themselves. UIView and NSView have no ancestors in common below NSObject. --- # What identifier? Your mention of an `.identifier`

Amazing isn't it? You'd think that once they'd gotten past their first billion lines of code they'd have learned to straighten things out. Those capabilities don't require permission sealed into the

Ahhhh, well I suppose it *can* run on the Mac, under the simulator? e.g. TARGET_OS_SIMULATOR

Hi, I’m moving some IB Views Across from iOS to Mac. By moving, I mean re-creating as you can’t copy+paste between iOS and Mac Storyboards. In the IOS Storyboard view controller, I have some

If I did that, I be spending 50%+ of my time filling in bug reports! I can’t see this is an “edge” case, you create an AppID and set some capabilities, you create another one and it has the same

Great I’ve made a copy of them - thanks a million.

I answered that yesterday. —Jens

NSData.bytes is a property of type "void*". And NSPointerFunctions even has a property whose type is a C function pointer: @property (nullable) BOOL (*isEqualFunction)(const void *item1, const

TARGET_OS_MAC is incorrect — for some reason that evaluates to true on all Apple platforms. You want TARGET_OS_OSX instead. Here's the full list as documented in <TargetConditionals.h>, which is the

If you want an actual property encapsulating your C-based array, you could keep it within an NSMutableData object since it’s just bytes. I’m not sure if an NSData object would keep the actual