The assistant only needs the bundle identifier and version to generate the Mac App Store receipt validation code. You can choose to generate code either for receipt validation or for InApp purchase validation. The generated code is ready-to-integrate, documented, debuggable and integrates various protection mechanisms to harden the reverse engineering.
Apple recommends that the validation code should be resilient against circumvention or alteration. Receigen generates code that uses mechanisms like strings obfuscation, constants computation, de-referenced function calls, non-predictible branching, and inlining so the resulting binary code can be hardly reverse-engineered. Moreover, Apple suggest that the validation code should change to not provide a common target. That is why, each time Receigen generates code, it is different.
Ever wanted to know if an application is signed or if what its receipt contains ? Receigen provides a inspector window where you can visualize the signature and receipt status of any application.
The inspector shows whether the application is signed or not and whether the application contains a receipt. If the application is signed, the inspector displays the chain of certification. If the application contains a receipt, the inspector displays the attributes contained in it.
Need to integrate into Xcode ? Using a Continuous Integration build process for your application ? Receigen can also be used on a command line, making easy to integrate into a building process.
Receigen provides a command line interface that makes it suitable to be called inside Xcode build phase. When invoked, Receigen only generates new validation code if the parameters have changed. See the Support page to learn how to integrate Receigen with Xcode.