MacOSCoders » Blog Archive » XCode: Could Not Support Development

»
S
I
D
E
B
A
R
«

Pages

TopPosts

Recent Comments

XCode: Could Not Support Development

June 20th, 2009 by Anish Kumar

Hello there! If you are new here, you might want to subscribe to the RSS feed for updates on this topic.

XCode: Could Not Support Development

Today when I started my work on an iPhone project, my XCode failed to mount my iPhone. The XCode organizer was showing an orange dot next to it instead of the usual green one. Organizer complained “Could Not Support Development”. I tried restarting my XCode, launched iTunes but in vain. iTunes was able to mount my iPhone but XCode simply failed and I was not able to test my app’s on my phone. Finally I restarted my iPhone and tried again. Bingooo..! it started working again. My iPhone was running the latest iPhone OS 3.0 GM developers build. See left for the screenshot of the error message that I got.

About Me: Anish:
Mac OS X software development is my bread winner with over 6 years of experience. Expertise in Color Management, TWAIN Scanner drivers on Mac OS X, Photoshop Filter and Import Plugin development on Mac OS X, iPhone. As an hobby I love to work on PHP, Flex, AIR, Photoshop. Check the 'About' page for more.

Readers who viewed this page, also viewed:

5 Responses

Paul writes:

June 21st, 2009 at 8:36 pm

Hi Anish,

Today I received the same message when I tried to debug an app on the device. Does this mean that we have to upgrade to the non GM 3.0 build? Did you end up solving this?

Thanks,

Paul

Anish Kumar writes:

June 21st, 2009 at 8:41 pm

Hi Paul,
You dont have to degrade to non GM build. Just try restarting your iPhone and/or XCode or your machine or a combination of all of that. This should generally fix it.

Happy Developing for iPhone,
-Anish

Lacy writes:

June 24th, 2009 at 6:55 am

Pretty good post. I just came by your site and wanted to say
that I’ve really liked browsing your posts. In any case
I’ll be subscribing to your blog and I hope you post again soon!

Jan writes:

June 26th, 2009 at 10:20 pm

Thank you very much (and google for finding this blog post). This had the potential to ruin my day … rebooting the iPhone indeed “fixed” this.

indowill writes:

July 3rd, 2009 at 7:07 am

rebooting did the trick indeed. thanks for posting this!