Archived Mavericks Bugs
![Archived Mavericks Bugs Archived Mavericks Bugs](https://s.hdnux.com/photos/10/73/05/2339156/7/628x471.jpg)
Share this story. Apple has just issued a patch specifically for Gmail users running Mail.app in. The is said to bring 'improvements to general stability and compatibility with Gmail,' specifically a bug that causes unread message counts to be inaccurate, and another bug that 'prevents deleting, moving, and archiving messages for users with custom Gmail settings.' The for the fix recommends backing up your data via Time Machine or some other mechanism before installing. You can get the update either through Software Update or by grabbing it. The rumor mill says that Apple is also testing some other new features and fixes for Mavericks, most notably in an OS X 10.9.1 update designed to fix minor-but-pressing problems and a larger 10.9.2 update later on. Neither of these has appeared in Apple's standard developer portal as of this writing, but given that Apple has followed this pattern for every single version of OS X to date, it's not exactly a stretch of the imagination.
Apple also released version 1.0.1 of iBooks for OS X today, which includes some non-specific 'bug fixes and improvements to performance and stability.'
Everything was working perfectly under Mountain Lion. Mavericks, not so much. The issue: I'm unable to carry out any receipt verification testing under Mavericks.
I'm using Receigen (Mac App Store/MAS) to generate both startup and in-app purchase receipt verification. I'm using Xcode 5.02 under Mavericks 10.9. Here is the way it worked under Mountain Lion Archive the app and export it to an application.
Archived Mavericks Bugs Bunny
Make sure you are logged out of your personal MAS id. You'll use your iTunes Connect testing ID later. From the Finder, run your exported app. After you launch your application, the following occurs:.
![Archived Mavericks Bugs Archived Mavericks Bugs](https://i2.wp.com/content.invisioncic.com/Mevernote/monthly_2017_09/J.png.f3e99fc1bf4ece488b8989b4e65bfc5e.png?ssl=1)
Your application fails to validate its receipt because there is no receipt present, and it exits with a status of 173. This is expected.
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 should prompt you for your MAS credentials. You will use your testing account here. The system relaunches your application, and your application successfully validates the receipt. This is what happens under Mavericks Same as above - archive/testing MAS ID/Finder run app.
However, now I receive this in the Console: Exited with code: 173 this should be okay just like above storeagent: Unsigned app (path/to/app).??? No MAS credentials. I've triple checked the code signing using both the Organizer/Validate as well as Receigen.
![Bunny Bunny](https://ac3358b8bbb07d0698bc-a5eb9017be3ef075e5ec9be3a0bfe06b.ssl.cf1.rackcdn.com/2013-10-23%2003-12-40%20PM-mavericks-main.jpg)
Both tell me my app is signed properly with no issues. Adata external hard drive hd710a 1tb white for mac. Funny thing, I've submitted the app to the app store and after approval, it works.
So it's signed correctly and receipt validation is working. But, I'm unable to carry out any receipt verification testing. That's the issue.
Archived Mavericks Bug's Bunny Cartoons
Thanks for your time. My problem was that in Xcode I was signing the app with the 'Mac Distribution' code signing identity and not the '3rd Party Mac Developer Application' one.
Archived Mavericks Bugs Bunny
After changing the signing identity, I rebuilt the app, then deleted the app's container folder located in /Library/Containers/. Then, double clicking on the rebuilt app in Finder, I was finally prompted to enter App Store credentials. I then entered the credentials of an iTunes Connect test user that I had setup, and the receipt was generated and the app launched ok.