I also have this problem and filed FB11710852 with sample test App, copy and pasted from Apple's documentation. Was filed in Oct 2022 and no response. Also tried same Test App in Swift and get the same result. A message showing in the Console is: "[api] Attempt to write notes by an unentitled app" In a semi recent version of iOS, Apple requires a special additional entitlement for App's that want to update the Notes field of a Contact but as far as I know, this is not (yet) required for macOS App's right? Anyone have any updates?

Not working again. No change to macOS version nor Xcode version. Just back to these console messages: error 11:59:51.470396-0700 storeuid <ReceiptRefreshRequest: 0x1581c3ee0>: Error fetching receipt for com.moremobilesoftware.divelogdt - Error Domain=com.apple.commerce.server Code=1008 "(null)" default 11:59:51.471332-0700 storelegacy StoreLegacy: Failed to renew receipt for application at path /Users/jXXXXXXX/Library/Developer/Xcode/DerivedData/<Product>/Build/Products/Debug/DiveLogDT.app : 'The operation couldn’t be completed. (com.apple.commerce.server error 1008.)' Anyone else seeing it go back and forth and back and forth like this?

OK done: FB9126563 Thanks.

Just to clarify, is your app installed on the destination Mac? Yes And if, on the destination Mac, you duplicate a .customxml in the Finder, does it do the right thing? Yes. In the "regular" way so the first duplicate is "... copy.customxml" and then subsequent are "... 2.customxml" And for further clarification, the first time the file is AirDrop'd, it has the correct extension and my App is invoked on the destination Mac. It's just the subsequent transfers of a file of the same name where I can see the file name is ".customxml 2" in the Downloads folder and my App is not invoked. I suspect there is nothing I can do about it, but it does seem weird and "wrong" to have Finder and AirDrop do different things. Thanks for your time.

It has just started working again for me now. No changes on my end so there must have been a problem with the Apple servers.

I'm having the exact same error/problem. In the console I get: ReceiptRefreshRequest: 0x7ff46e9289c0: Error fetching receipt for com.moremobilesoftware.divelogdt - Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorDomainKey=4, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask FC307DCC-81C1-4420-BCF8-D1402FFAB960.3, _NSURLErrorRelatedURLSessionTaskErrorKey=(     "LocalDataTask FC307DCC-81C1-4420-BCF8-D1402FFAB960.3" ), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=https://p100-sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/createAppReceipt, NSErrorFailingURLKey=https://p100-sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/createAppReceipt, _kCFStreamErrorCodeKey=-2102} Has been working for forever of course, nothing new to see here :-) I guess I'll go to DTS as well. Can only help if more people report it right?

Thanks for the suggestion Claude31. I spent some time subclassing NSSegmentedCell and doing my own drawing similar to your example. However it didn't work very well. Unlike you, I just drew a background color and then called 'super' to get the text drawn and to get the same look as the default. After fiddling with modifications to the origin and size, you could still see elements of the horizontal line around the vertical line drawn between the segments. If I made it wider, then the vertical lines were gone. I also needed to draw in the selected segment as you could see the horizontal line when my App was not the "Active" App (the highlighting goes away). And since I used this method in a couple of different places, I found that the "fiddling" needed to be different in each case since the width of the segment and it's associated padding around the text was completely different each instance.But as part of mucking around, I realized a much easier solution. I just put an NSView behind the NSSegmentedControl and in front of the NSBox. Made it the same width and height as the control (and alignment) and set it's colour to the same as the background around the NSBox. Viola! No more NSBox showing through.Hope that helps someone else later.