Answering own question:
App was built with Automatically Managed Signing. Changing to Manual signing fixed the problem.
Nick Moore
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
I'm having a similar issue. Was this ever resolved for you?
No, SKTerminateForInvalidReceipt does not validate receipts. All it does it terminate the app with error code 173. it is equivalent to calling exit(173).
I have noticed that, on (10.15 and 11.0) if signed with Mac Development ceritficate or official Mac App Store distribution cert, the alert WILL pop up (although with errors in Console). But if signed with Develoepr ID, it will not pop up.
Search "build settings" in Xcode help.
There's also an archived version on the web here: https://developer.apple.com/library/archive/documentation/DeveloperTools/Reference/XcodeBuildSettingRef/1-Build_Setting_Reference/build_setting_ref.html
Remember that the purpose of this initial beta is for third party developers and Apple to catch these faults. It's common for apps to experience problems on the beta version of a new macOS update. I would suggest reporting the fault to Parallels directly and/or Apple (using the Feedback Assistant).
After about 10 hours staring at the motionless progress bar, I bit the bullet and performed a hard reset by holding doen the power button. The Mac then booted and completed installation successfully.
I've been stuck on the "Black background, white apple logo & progress bar" now for about 3 hours with no discernible progress bar movement.