I can no longer run my app from Xcode with code signing for my Mac app. I've configured a debug provisioning profile manually and tried that but it fails, saying the embedded framework is not code signed at all.I tried "Automatic" code signing but it fails with the same error:code object is not signed at allIn subcomponent: PATH_HERECommand /usr/bin/codesign failed with exit code 1The only way I'm able to get the app to run is to turn off code signing alltogether in Debug mode. I've noticed in that case though, testing is pretty useless because my app can't event write a security scoped bookmark to disk.

Where's the link for the "Guides and Sample Code" page (located here: https://developer.apple.com/library/content/navigation/I kow the URL because I know it, but why isn't there a link to it on the main developer page (since release notes and other important tidbits get published there)? Why's it so hard to find?Or is it right in front of my face and I'm not seeing it?

I wrote a little something that uses WKWebView. It seems that print: does not work though (macOS app).I'm kind of regretting using WKWebView over the old school WebView...anyone have a workaround?

Have an app I'm working on that stores an item in the keychain. Everything was was working fine. I have a button in the UI that allows the user to clear out the keychain item:NSDictionary *query = @{(__bridge id)kSecClass: (__bridge id)kSecClassGenericPassword, (__bridge id)kSecAttrService: service, (__bridge id)kSecAttrAccount: accountKey}; OSStatus status = SecItemDelete((__bridge CFDictionaryRef)(query));Status is -25244 which is errSecInvalidOwnerEdit. This app created the keychain item to begin with. What would be the appropriate way to handle this type of error?

Looks like I'm having a bad morning. I'm on 10.11.6 and Xcode 7.3.1.Xcode keeps crashing. When I re-launch Xcode, it restores the window of my open project and crashes again. I rebooted my machine and was able to start working again for about 5 minutes and now it is doing it again.When relaunching I get:Xcode quit unexpectedly while using the dsc_extractor.bundle plug-in.I sent probably 10-15 crash reports to Apple.

I have an NSTableView (view based). The cells (views) have a NSImageView to display a thumbnail.Thumbnails come from the web, and I load the thumbnails lazily. My class that handles the thumbnail loading has a delegate that sends back a message like this:-(void)thumbnailCache:(nonnull MyThumbnailCacheObject*)thumbnailCache loaddedThumbnailsForURLs:(nonnull NSArray<NSURL*>*)imageURLs { //Get the row indexes for the urls...and then call....reloadDataForRowIndexes:columnIndexes //table view doesnt have columns. [self.tableView reloadDataForRowIndexes:indexes columnIndexes:[NSIndexSet indexSetWithIndex:0]]; }However the cells don't update. At first I thought it was a bug in my thumbnail loading, but a call to reloadData does update the cells properly.Wrapping the reloadDataForRowIndexes:columnIndexes: in between beginUpdates and endUpdates calls makes no difference.Does reloadDataForRowIndexes:columnIndexes: not work with view based table views? I'm tempted to just use reloadData and hope everything works out okay.

I got this email from an app update I submitted yesterday....:To process your delivery, the following issues must be corrected:Invalid Signature - This error occurs when you have signed your app's installer incorrectly. There are two certs required for this process: the "3rd Party Mac Developer Application" cert and the "3rd Party Mac Developer Installer" cert. When signing your package, you need to ensure that you are using the Installer cert to sign your package. Ensure that you are specifying this cert when submitting your app via the Xcode Organizer or when running productbuild from the command line.Once these issues have been corrected, you can then redeliver the corrected binary.Regards,________________The App Store teamWhen I validate the app in organizer for MAS distribution, it passes validation. Also, when I manually switch it to "Installer" in Xcode and try to rearchive the project, I get an error about no provisioning profiles matching the identity. For provisioning profiles, I have it "Automatic". I did try to configure provisioning profiles manually for these app Identifiers in the Member Center, which only has it matching the developer application certicate. Why would the Memeber Center have a provisioning profile not match the installer certificate, if that is the one to be used?BTW, code signing just started acting bonkers on me recently, as it seems to do every now and again, though i haven't made any changes to my certificates nor configurations.

Showing a popover from a status bar item. Sometimes results in this being logged out:Error: this application, or a library it uses, has passed an invalid numeric value (NaN, or not-a-number) to CoreGraphics API and this value is being ignored.Please fix this problem.When this happens, the popover appears at 0.0,0.0 (lower left) of the screen for a second... before snapping to the proper position.Code: NSStatusBarButton *statusButton = _statusItem.button; [_popover showRelativeToRect:statusButton.bounds ofView:statusButton preferredEdge:NSMinYEdge];The user can add or remove the status item in this app...the issue I notice usually happens the second time the popover gets presented. Looks like the popover can be trying to present before the status item button's position is set?

I'm looking to release an update to a Mac application. I've updated this app many times and had no issues. I haven't change any code signing related settings in the project.Now when I try to export a dev ID signed app in Organizer, I'm an error presented as a sheet:An error occurred during exportCodesign failedThe sheet has two buttons: Show Logs and & Cancel. I've filed a bug and sent the logs to Apple. If you cancel the sheet out and hit "Previous" Xcode wll crash on you.Anyone experience this and know of a solution? This is preventing me from pushing an update out to the folks.

Started happening kind of out of nowhere. Any ideas?

In NSFileManager there is this method to move files to and from iCloud:- (BOOL)setUbiquitous:(BOOL)flag itemAtURL:(NSURL *)url destinationURL:(NSURL *)destinationURL error:(NSError **)errorOutAll the samples and information I'm able to find seem to be related to using NSDocument, which my app isn't using. I have a little view in my app that allows users to move an image out from the iCloud container and into a local directory. It seems that simply using NSFileManager moveItemAtURL:toURL:error: works fine both to move a file in and out of the iCloud container on OS X without wrapping everything in a file coordinator block. Is it still necessary to use a file coordinator to move files out of iCloud on the Mac. When I put a file in the iCloud container, the system automatically starts uploading it..even though I'm not using a file coordinator...and my related file presenter still is detecting a change.Both methods seem to be working the same, I'm just wondering if I should be using a coordinator because it's a good amount of code I can get rid of if it's not necessary.Thanks.