On 18/10/2011, at 11:16 AM, Graham Cox wrote:
>
> However, checking apps I build with Xcode versus those I have downloaded from
> the App Store shows that indeed, my dev apps do not have a receipt. Why would
> they, I didn't "receive" them, I made them.
>
> Maybe there's a method for obtaining or generating a receipt for testing the
> verification mechanism, or perhaps you just have to trust that by the time an
> app has gone up on the Store, that part will work (you'd have to be very
> brave or foolish to do that I think). Maybe you should ask about that on the
> relevant forum at Mac Dev?
>
> --Graham
>
>
It's built in to the system - from the docs:
In order to test your main application during the development process, you need
a valid receipt so that your application launches. To set this up, do the
following:
• Make sure you have Internet access so you can connect to Apple’s
servers.
• Launch your application by double-clicking on it (or in some way
cause Launch Services to launch it).
After you launch your application, the following occurs:
• Your application fails to validate its receipt because there is no
receipt present, and it exits with a status of 173.
• The system interprets the exit status and attempts to obtain a valid
receipt. Assuming your application signing certificate is valid, the system
installs a valid receipt for the application. The system may prompt you for
your iTunes credentials.
• The system relaunches your application, and your application
successfully validates the receipt.
With this development receipt installed, you can launch your application by any
method—for example, with gdb or the Xcode
debugger._______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
