It is apparently impossible to use the sandbox account to test receipt validation on OSX.
No solutions on SO work. Have someone figured this out?
This is a copy of radar http://www.openradar.me/23831039
Summary: Seemingly new to 10.11.2, attempts to authenticate with a sandbox iTunesConnect user account are met with an error message:
"This Apple ID has not yet been used with the App Store."
Steps to Reproduce: 1. Create any submission-ready app for the MAS 2. Launch on 10.11.2 3. Supply Sandbox credentials
Expected Results: The app should be validated with a _MASReceipt and launch as expected.
Actual Results: A dialog is presented:
This Apple ID has not yet been used with the App Store. Please review your information.
Version: 10.11.2
There is also this email from Apple, that we all have received, that probably has a relation to it. BTW, their solution of updating to 10.11.2 and restarting the computer, is useless, as expected:
To help protect customers and developers, we require that all third party apps, passes for Apple Wallet, Safari Extensions, Safari Push Notifications, and App Store purchase receipts are signed by a trusted certificate authority. The Apple Worldwide Developer Relations Certification Authority issues certificates that Apple uses to sign apps on the Mac App Store and receipts that third party developers use to prevent unauthorized copies of their apps from running. On February 14, 2016, the intermediate certificate will expire and receipt signatures will include a renewed intermediate certificate.
Since you may use receipt validation in your apps, we want to make you aware of potential issues your users may encounter due to the renewed certificate. Users running OS X El Capitan (v10.11 or v10.11.1) may receive a notification that your Mac app is damaged if it utilizes receipt validation to request a new receipt from Apple. They can resolve this issue by restarting their Mac or updating to OS X El Capitan (v10.11.2).
Mac App Store customers running OS X Snow Leopard (v10.6.8) will be unable to purchase new apps or run previously purchased apps that utilize receipt validation until they install the OS X Snow Leopard update, which will be available via OS X Software Update this January.
Since different methods can be used for validating receipts, we recommend that you test your receipt validation code in the test environment to ensure no implementation-specific issues exist. Make sure that your code adheres to the Receipt Validation Programming Guide and resolve any receipt validation issues by February 14.
We apologize for any inconvenience. If you have any questions, contact us.
Best regards, Apple Developer Relations
No solutions work like: creating a fresh sandbox user, transferring the project to a new one, cleaning the derived-data folders, cleaning the appstore cache folder of OS X, etc.