48

I am getting an error while uploading my app on device. It does installs it but not able to upload it.

Also I want to run the instrument tool on device but when I run it shows nothing.

Anyone facing the same issues.

Oded Regev
  • 4,065
  • 2
  • 38
  • 50
rkb
  • 10,933
  • 22
  • 76
  • 103

5 Answers5

120

I had this problem after changing around provisioning profiles and app ID's.

What fixed it for me:

  1. Quit XCode
  2. In Terminal.app, navigate to your project directory and execute rm -rf build/
  3. Restart XCode
Don
  • 3,654
  • 1
  • 26
  • 47
Archie
  • 4,959
  • 1
  • 30
  • 36
  • 1
    Another well-deserved upvote from me. Now that I see that, you could probably just go "Build > Clean all Targets" and achieve the same result. – Dan Ray Aug 13 '10 at 18:05
  • 13
    "Clean All Targets" doesn't fix this error. You definitely have to follow the steps detailed here to get rid of the error. – Nik Reiman Aug 19 '10 at 14:32
  • Confirming that, "Clean All Targets" does not fix it. – James Skidmore Aug 24 '10 at 05:45
  • 2
    I would just note that for beginners, step 2 could be expanded to be: 2a. Start Terminal.app 2b. rm -rf build/ It worked for me but since I didn't know what that terminal command meant, I was unsure if that was all there was to it. It was. – Steve Sep 17 '10 at 03:21
  • Archie, that was a painful problem you helped solve. Remind me to never change Bundle Identifiers ever again. Thanks! – John M. P. Knox Sep 24 '10 at 23:28
  • This (rm -rf build/) is definitely required. Clean All does not do what needs to be done. – Jann Nov 27 '10 at 17:17
  • Clean all worked, for me, but just had to be sure to restart xcode. – Ben Holland Dec 29 '10 at 17:11
  • Clean All Targets, then restart XCode fixed it for me. – Benjamin Intal Jan 07 '11 at 09:03
  • Thanks for the answer, but it would be really helpful if you expanded step 2 to make sense for people who are not used to Terminal.app... Most importantly, you need to navigate to your project's directory in Terminal before you can run that command. – jowie Jan 13 '11 at 10:10
  • Clean All/Restart XCode. Whenever something weird happens, that's my regular fix. Works 9 times out of 10 for provisioning/device install weirdness. – Dimitri Mar 21 '11 at 16:21
  • am running iOS beta3 on iPad and Xcode3 (I can’t upgrade to Xcode4 yet), doesn’t work for me. –  Aug 15 '11 at 05:43
6

I also confirm, that I had that issue on Xcode 3.2.5 and iOS 4.2 GM Seed and after adding new provisioning profile.

You do not have to use terminal, you can select *.app from Products Group in 'Groups & Files' pane in Xcode. Then right-click on it, and select 'Reveal in finder'. Then manually delete the build catalogue. And restart Xcode.

Worked for me.

manicaesar
  • 5,024
  • 3
  • 26
  • 29
2

I was getting this issue on an iPhone running 3.0 software, but it was working fine on phones running 3.1. The app used to work on the 3.0 software until we added users to the provisioning for the app - this is the only thing I can think of that might have caused it.

If you're running 3.0 still, try upgrading to 3.1 and see if that fixes it.

1

I had the same error message in iOS 4.1 but from a different cause: when trying to link to a universal (ARM & X86) static library that was over 10MB. If I link directly to the ARM version of the static library (for iPhones), then it works fine.

Shervin Emami
  • 2,695
  • 25
  • 17
1

Sometimes manual delete of Build folder of your application fails to solve the problem "Failed to upload the .app on device"

Try WIndows->organizer->Provisioning profile(in left pane)->refresh it once....

This has solved my problem!

selfReflection
  • 11
  • 1