Thanks Quinn. Within the app, when the customer tries to enable the logging it will alert the customer if the NSStask response isn't 0. This has helped identify if the user can or cannot access the log in the past, but for this particular situation it doesn't fail, just none of the log data is recorded to the file. The customer experimented with the "show" function and was able to access past data, so it seems like "stream" may be broken on this customers Mac.

Superb eskimo... Once again you've saved my bacon. I wasn't trying to find a challenge, I already have enough just trying to learn Swift and SwiftUI. I think I understand, when the object is NOT a UnsafeMutablePointer, I should cast it to be a UnsafeMutablePointer, unless the documentation states otherwise. I have filed a Feedback Request to get your example added to the documentation for CFFileSecurityCopyAccessControlList as I think it would help other developers. Thank you again.

Thank you so much for sharing this workaround. I've spent the last couple of days trying to figure out why scripting Apple Music has suddenly resulted in timeouts (app freezes for two minutes). I realized I wasn't checking to see if app had permission and when I added that code, it never timed out, app just remained frozen.

Hey Quinn, master of Apple framework knowledge... Is there an approved way of obtaining battery information with more precision than 0-100 integers? I personally don't really care too much (ha) about the units, just don't want to report a 17 hour sleep used zero battery (something or rather).

Thanks for the reminder, updating App Wrapper to use notaryTool is on my list of things to do, but there's still some big ticket items above it. Thanks for the video link, I'll watch that soon (I think I've seen it already, but a refresher is always good).

Thanks Quinn, A simple app built-in in Xcode does indeed work. At first glance the Info.plist from Xcode does contain far more keys/values, so I'll start experimenting with those. Thanks for your time and the hint.

I have been able to get it working by following the iOS (yes for developing a Mac application, tested as far back as 10.13.6) guidelines at the bottom of the following document https://developer.apple.com/documentation/appstorereceipts/validating_receipts_on_the_device?language=objc

@Quinn, is there someone I can write to? I believe that this is a perfect example of why Apple should reconsider how they utilize their forums. Many other companies use their forums for support and to triage bugs and issues. These receipt failures, makes it hard (for those that do) to test everything before submitting to the App Store, let alone the poor dev who got rejected and couldn't even debug their receipt validation code (on a different forum). DTS is great for one-to-one (and includes some truly awesome people, present company included), but in situations like these, the problem affects multiple developers and it might actually be more efficient for Apple to say something on a public searchable forum, than answer multiple DTS tickets all of the same (providing developers file DTS tickets and don't just give up). The easier and quicker it is for developers to find solutions, the less resources they'll need and the less frustrated they'll get. Please understand this is not a knock on you or the great people like yourself who assist others here (I do hope that Apple pays you to 'watch' the forums), its about Apple controlling how developers can distribute their apps, but at the same time make it harder to do so, which is incredibly frustrating for those, especially those who were enthusiastic about building great apps for the Mac platform. Thanks for all your help over the years Quinn, I wish you a Merry Christmas and a happy new year. I also hope that one day I can truly express my gratitude. Sam Rowlands.

I am sorry that I am not able to assist with Unity as I've never used it to develop Mac Apps. It may be that there are other issues as well, is your application using a provision profile? If so, you may need to use the "Apple Developer" certificate (and matching profile) to test all the App Store functionality, then re-sign the application using the "Apple Distribution" certificate (and matching profile) to submit. In regards to the error I was getting, instead of using "exit( 173 )", instigating a SKReceiptRefreshRequest object, setting up a delegate to handle the response, was the only way I was able to get a valid receipt and avoid the "Application is damaged" error. It is a pain because I've had to also re-write how the DRM logic works, because SKReceiptRefreshRequest is asynchronous, so it might fail while my app is already running and the user is working. I don't want to make the user wait, because it might take a long time and that too creates user frustration.

Thank for this post, at least I am not alone. You're welcome and thank you joining in. In other forums there's other developers with the same problem. One developer was saying that App Review was rejecting their application because of this issue, and the developer got around it by removing the receipt validation code (which in the past has been a reason for rejection). I was really hoping that someone from Apple would chime in and tell me if I was doing something wrong, to use a different API or that Apple is looking into this. In comparison, FastSpring respond to support requests within 24 hours.

Thanks @Schubert. Several others in other forums have also commented that it hasn't been working in the last few weeks for them, some are even saying that App Store reviewers are rejecting apps because of this problem. I was hoping that I was doing something wrong and I could fix it at my end. Would be nice if Apple could make a statement, at least let us Mac developers know what's going on and when it might be fixed.

Once again, Thank You Quinn. If you have a tip jar, please let me know. Your timely responses and depth of knowledge in these areas really do help make my life easier. Sam Rowlands

Quinn, Thank you for your prompt and informative response. I really appreciate being able to fire questions here and have you answer them so quickly and precisely. Have a great week. Sam Rowlands