Hi, thanks for the update. I've tried to remove every request for the receipt on my app (mine is made on Unity, so I can't guarantee that there are no other embedded calls from Unity's side or a native plugin), but still the same crash on the startup. I am even considering submitting the app without testing to the AppStore, activating manual release and testing using promocodes before the release. At least, in this case, the receipt will come from the AppStore and embedded on the download, so no AppStore sandbox environment. But I am not sure the reviewers would be able to test it anyway. I have a feeling that the error is related to Apple's certificate chain as I see too many errors on the system/console logs that has to do with codesign and other trust processes. I've checked all certificates on the keychain and all of them are valid anyway. But I believe it is related to it. I've learnt way more about codesign than I would like hehe.

Also happens on Catalina 10.15.4 and 10.15.7 =Z

Hi @rowlands, thanks for the info. I really don't know what to do, I may try to remove the refresh receipt but I am not sure if it will affect the error as I see no log from my app requesting the receipt before the crash. It seems it starts automatically from the launch process and the error would be on Apple's server side . As you've posted before, there is this error 500. I've check all possible logs from Mac and got these too: Error fetching receipt for xxxx - Error Domain=com.apple.commerce.client Code=500 “(null)” ‘The operation couldn’t be completed. (com.apple.commerce.client error 500.)’ I've been doing the same process since 2012, even if the AppStore sandbox is bizarre, the login window has always been shown and the app relaunched. I don't know how to escalate the error to Apple support/devs. By far Apple is the company that treats developers worse. Thanks again. If you find out something, please, update here. I will do the same.