<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>ITunes Connect on The Dangling Pointer</title><link>https://aaron.blog/tags/itunes-connect/</link><description>Recent content in ITunes Connect on The Dangling Pointer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 26 May 2011 13:11:51 +0000</lastBuildDate><atom:link href="https://aaron.blog/tags/itunes-connect/index.xml" rel="self" type="application/rss+xml"/><item><title>iTunes Connect - Invalid Binary</title><link>https://aaron.blog/itunes-connect-invalid-binary/</link><pubDate>Thu, 26 May 2011 13:11:51 +0000</pubDate><guid>https://aaron.blog/itunes-connect-invalid-binary/</guid><description>&lt;p&gt;I spent the past week pulling out my hair trying to submit an update for Centare's EyeOnWeather application to iTunes Connect.  I kept getting a reject from the system and all I got for an error message was "Invalid Binary."  THANKS, THAT'S SOOPER.&lt;/p&gt;&lt;p&gt;Eventually I ended up attempting to contact iTunes Connect Support for further details.  I thought it might have been missing icons, malformed Info.plist, something.  I haven't changed anything in the project drastically with how it builds, so I was at a loss.  Turns out, I was picking the wrong provisioning profile in my setup.  Man I felt stupid.  Ends up that I'm not crazy - Apple's documentation on how to set up your project for building still only references Xcode 3.  Awesome for the rest of the world using Xcode 4.  Here are some tips I got from Apple iTunes Connect support for pulling in information to submit to their developer team:&lt;/p&gt;</description></item></channel></rss>